Skip to content

chore: publish v5 releases to the legacy dist-tag - #942

Merged
reggi merged 1 commit into
release/v5from
fix/v5-publish-legacy
Nov 2, 2026
Merged

reggi merged 1 commit into
release/v5from
fix/v5-publish-legacy

Conversation

@reggi

@reggi reggi commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

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.

Correct the v5 backport configuration and preserve the existing legacy channel through a release template override. Regenerate workflows so publishing cannot overwrite latest-6.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: ebd25fa9-cedb-4fc5-9720-36ce0d5fa380
@reggi
reggi requested a review from a team as a code owner November 2, 2026 16:12
@reggi reggi changed the title fix: publish v5 releases to the legacy dist-tag chore: publish v5 releases to the legacy dist-tag Nov 2, 2026
@reggi
reggi merged commit 566e22f into release/v5 Nov 2, 2026
7 checks passed
@reggi
reggi deleted the fix/v5-publish-legacy branch November 2, 2026 16:58
@github-actions github-actions Bot mentioned this pull request Nov 2, 2026
reggi pushed a commit that referenced this pull request Nov 2, 2026
🤖 I have created a release *beep* *boop*
---


## [5.7.3](v5.7.2...v5.7.3)
(2026-11-02)
### Bug Fixes
*
[`7227001`](7227001)
[#927](#927) backport v7 range
parsing performance improvement to v5 (#927) (@reggi, @Copilot)
### Chores
*
[`566e22f`](566e22f)
[#942](#942) publish v5 releases
to the legacy dist-tag (#942) (@reggi, @Copilot)
*
[`b827b90`](b827b90)
[#926](#926) backport v7 range
parsing coverage to v5 (#926) (@reggi, @Copilot)
*
[`9246ad5`](9246ad5)
[#708](#708) deps:
`@npmcli/template-oss@4.22.0` (#708) (@lukekarrys)
*
[`d7654e3`](d7654e3)
[#623](#623) auto publish
(@lukekarrys)
*
[`2783af2`](2783af2)
[#851](#851) bump
@npmcli/template-oss from 4.29.0 to 4.30.0 (#851) (@dependabot[bot],
Michael Smith)
*
[`1ed65a5`](1ed65a5)
[#734](#734) postinstall for
dependabot template-oss PR (@hashtagchris)

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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.

2 participants