Skip to content

chore: release 5.7.3 - #941

Merged
reggi merged 1 commit into
release/v5from
release-please--branches--release/v5
Nov 2, 2026
Merged

reggi merged 1 commit into
release/v5from
release-please--branches--release/v5

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 2, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

5.7.3 (2026-11-02)

Bug Fixes

Chores


This PR was generated with Release Please. See documentation.

@github-actions
github-actions Bot requested a review from a team as a code owner November 2, 2026 15:52
@github-actions

github-actions Bot commented Nov 2, 2026 •

Copy link
Copy Markdown
Contributor Author

Release Manager

Release workflow run: https://github.com/npm/node-semver/actions/runs/41486707353

Release Checklist for v5.7.3

  • 1. Approve this PR

    gh pr review 941 -R npm/node-semver --approve
  • 2. Merge release PR 🚨 Merging this will auto publish 🚨

    gh pr merge 941 -R npm/node-semver --squash
  • 3. Check For Release Tags

    Release Please will run on the just pushed release commit and create GitHub releases and tags for each package.

    gh run watch -R npm/node-semver $(gh run list -R npm/node-semver --workspace release -b release/v5 -L 1 --json databaseId -q ".[0].databaseId")

@github-actions
github-actions Bot force-pushed the release-please--branches--release/v5 branch from 215e07e to 2c3bcd4 Compare November 2, 2026 15:53
reggi
reggi previously approved these changes Nov 2, 2026
reggi added a commit that referenced this pull request Nov 2, 2026
## Summary

Fix the v5 release configuration before merging #941. It currently uses
backport=6, which would publish semver@5.7.3 to latest-6 and overwrite
the v6 channel.

Set the template backport major to 5 and the default publish tag to
legacy. Extend the upstream release template with an empty backport
argument so the release commands use legacy rather than latest-5, while
keeping v5 branch defaults. Regenerate the release workflow and correct
the manual release CI default to release/v5.

## Validation

- npm test passes on Node 20.19.5 with 100% coverage.
- npm run postlint --ignore-scripts passes.
- Verified both generated release commands select legacy for 5.7.3 and
preserve prerelease-5 for prereleases.
- Verified the actual template-oss 4.30.0 CLI parser accepts an empty
backport argument and its constructor accepts the resulting options,
with GitHub operations stubbed.
- git diff --check passes.

The legacy test runner fails on local Node 26; the complete suite passes
on Node 20, as used by the v5 workflow. No package was published.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: ebd25fa9-cedb-4fc5-9720-36ce0d5fa380
@github-actions
github-actions Bot force-pushed the release-please--branches--release/v5 branch from 2c3bcd4 to e2ab37d Compare November 2, 2026 16:59
@github-actions
github-actions Bot force-pushed the release-please--branches--release/v5 branch from e2ab37d to a263f87 Compare November 2, 2026 17:00
@reggi
reggi merged commit 5365f1f into release/v5 Nov 2, 2026
9 checks passed
@reggi
reggi deleted the release-please--branches--release/v5 branch November 2, 2026 17:07
@github-actions

github-actions Bot commented Nov 2, 2026

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

@github-actions

github-actions Bot commented Nov 2, 2026 •

Copy link
Copy Markdown
Contributor Author

Release Workflow

🚨🚨🚨

@npm/cli-team: The post-release workflow failed for this release. Manual steps may need to be taken after examining the workflow output.

🚨🚨🚨

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant