Repository navigation
ci: skip release gates when the version is published; install seo in orb setup - #136
Merged
Merged
Conversation
A push that changes package.json without a new version (scripts, dependencies) ran the full install, package test and audit, so a new upstream advisory failed a run that had nothing to release. Those steps now run only for an unpublished version or a manual run. Amp-Thread-ID: https://ampcode.com/threads/T-01a15a6b-b6b3-75de-9a30-6cec07eb3164 Co-authored-by: Ian Nuttall <6681919+iannuttall@users.noreply.github.com>
Fresh orbs get the latest published seo on PATH for seo login and real runs. Source changes are still tried with node dist/cli.js. Amp-Thread-ID: https://ampcode.com/threads/T-01a15a6b-b6b3-75de-9a30-6cec07eb3164 Co-authored-by: Ian Nuttall <6681919+iannuttall@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
release.ymlruns on anypackage.jsonchange. A change without a new version (chore: deploy the hosted MCP from main through Cloudflare builds #133 added scripts) still ran install, the package test andpnpm audit, so a new upstream advisory failed a run that had nothing to release. Those steps now run only when the version is not on npm yet, or on a manual run. Releases keep the same gates..agents/setupinstalls the latest publishedseoglobally soseo loginworks in fresh orbs (source changes still go throughnode dist/cli.js).Checked: workflow YAML parses; setup runs cold (14s) and warm (4s, no download), and a clean login shell finds
seo0.8.3. Merging this changes release.yml, so the Release workflow runs on main and should end with "already published; nothing to release".