ci(publish): rebase-safe lockstep version-bump commit-back#424
Merged
Conversation
Same fragility as run402-private's publish-functions (fixed there): the 'Commit version bump' step did a bare 'git push origin main', which loses a push race with any concurrent merge — leaving run402-mcp/run402/@run402/sdk published on npm but main un-bumped with no tag/release. Now it rebuilds the (already-published) lockstep bump on the LATEST main each attempt — fetch + reset --hard origin/main + re-set the exact published version across all three package.json (root via npm version, cli/sdk via node -e, mirroring the bump step) + npm install --package-lock-only — which is conflict-free, then retries the push up to 5x with backoff. Idempotent. dry_run path unchanged. YAML validated. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.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
1 participant
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.
Sibling of run402-private's publish-functions hardening. The
Commit version bumpstep did a baregit push origin main, which loses a push race with a concurrent merge — npm ships all three packages but main stays un-bumped with no tag/release (the failure mode that bit @run402/functions 3.5.0).Now it rebuilds the (already-published) lockstep bump on the LATEST main each attempt —
fetch+reset --hard origin/main+ re-set the exact version across root + cli + sdkpackage.json(mirroring the bump step) +npm install --package-lock-only— conflict-free, retried 5x with backoff. Idempotent;dry_rununchanged. YAML validated; exercised on the next real publish.