Repository navigation
v6.1.1
Changes
- fix(release): 🐛 Publish only pending source snapshots
Release details
- npm: https://www.npmjs.com/package/@haskou/value-objects/v/6.1.1
- Pull request: #60
- Source branch:
fix/release-queue - Version bump:
patch
Pull request notes
Problem
The release queue replays historical merged PRs with no modern release marker. The latest master run attempted to republish #7 as 4.2.0 and failed while pushing a synthetic release commit containing an old workflow. This blocks publication of the current package changes.
Change
- Only process merges after the last legacy release commit on the triggering first-parent history and contained in the triggering commit.
- Tag the existing merge commit and record version/PR metadata in the annotated tag, avoiding synthetic commits with historical workflow changes.
- Recognize both new annotation metadata and legacy release-commit metadata when resuming.
- Reapply the recorded npm version on retries and restore package.json after publication so subsequent queued checkouts stay clean.
- Add release-workflow regression tests to CI.
This is separate from #59 and is required to unblock its npm publication. Existing published versions and tags are preserved.
Validation
Three regression tests pass using temporary Git repositories: queue boundaries, tag identity/metadata, and legacy retry compatibility. Workflow YAML parses and every shell step passes bash -n.