Skip to content

release: promote publish-order fix to main (complete v0.3.0) - #245

Merged
sobechestnut-dev merged 1 commit into
mainfrom
dev
Jul 28, 2026
Merged

release: promote publish-order fix to main (complete v0.3.0)#245
sobechestnut-dev merged 1 commit into
mainfrom
dev

Conversation

@sobechestnut-dev

Copy link
Copy Markdown

Promotes the publish.mjs fix (#244) to main so the idempotent publish can be dispatched to complete the v0.3.0 line by publishing the skipped gcode-bgcode@0.3.0.

Merge with a merge commit (promotion pattern). No version change — dev and main are both at 0.3.0; this only carries the release-tooling fix. After merge, I'll dispatch release-publish on main.

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: Nathaniel Chestnut <sobechestnut-dev@users.noreply.github.com>
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
@sobechestnut-dev
sobechestnut-dev merged commit 95bbe2e into main Jul 28, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant