fix(release): publish gcode-bgcode + idempotent publish guard - #244
Merged
Conversation
The v0.3.0 publish shipped 12/13 packages: tools/release/publish.mjs had a hardcoded ORDER list that never got gcode-bgcode added when the package was created, so the release skipped it (and reported success for the 12 it knew). - Add gcode-bgcode to ORDER, after gcode-containers / before gcode-parser (parser's batteries worker depends on the bgcode adapter). - Idempotent recovery guard (DD-008 §6): skip any name@version already on the registry, so a rerun publishes only the not-yet-published remainder instead of dying on "cannot publish over existing version". - release-publish.yml: add workflow_dispatch so a partial line can be completed by re-running the idempotent publish against main (no tag surgery); fix the stale "×9" step label. Recovery for the v0.3.0 line: dispatch publishes only gcode-bgcode@0.3.0. 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.
The v0.3.0 publish shipped 12 of 13 packages —
tools/release/publish.mjshad a hardcodedORDERlist that never gotgcode-bgcodeadded when the package was created, so the release silently skipped it (and reported success for the 12 it knew about).gcode-bgcode@0.3.0is not on npm.Changes
publish.mjsORDER — addgcode-bgcode(aftergcode-containers, beforegcode-parser, which depends on the bgcode adapter). Now 13.publish.mjsidempotent guard — skip anyname@versionalready on the registry (DD-008 §6 recovery model), so a rerun publishes only the missing remainder instead of failing on "cannot publish over existing version".release-publish.yml— addworkflow_dispatchso a partial line can be completed by re-running the idempotent publish againstmain(no need to move the immutablev0.3.0tag); fix the stale "×9" step label.Recovery
After this lands on
main, dispatchingrelease-publishpublishes onlygcode-bgcode@0.3.0(the other 12 are skipped), completing the v0.3.0 line. npm allows it — the name is unpublished.Tooling-only; changeset-exempt.