bin/publish-tagged.ts publishes only packages whose tags point at HEAD. Two known gaps:
- GitHub cancels a pending run in the
publish concurrency group when a newer run queues, so a Publish commit that lands between two others can go unpublished with no failure signal.
- A re-run of a failed run re-uses that commit's script, which is why the first release needed its tags moved to the fix commit.
Proposal: an --all-tags mode (exposed as a workflow_dispatch input) that lists every @ethdebug/*@<version> tag, probes the registry for each, and publishes the missing versions from a checkout of each tag's commit. The per-package probe and pack-list check already exist; the new part is iterating tags and checking out per tag in a temporary worktree.
Context: the release process landed in #293, was fixed in #295, and is documented in RELEASING.md (#298).
bin/publish-tagged.tspublishes only packages whose tags point at HEAD. Two known gaps:publishconcurrency group when a newer run queues, so a Publish commit that lands between two others can go unpublished with no failure signal.Proposal: an
--all-tagsmode (exposed as aworkflow_dispatchinput) that lists every@ethdebug/*@<version>tag, probes the registry for each, and publishes the missing versions from a checkout of each tag's commit. The per-package probe and pack-list check already exist; the new part is iterating tags and checking out per tag in a temporary worktree.Context: the release process landed in #293, was fixed in #295, and is documented in RELEASING.md (#298).