Skip to content

Use a dist-tag for major releases that doesn't parse as semver#9627

Merged
tobias-tengler merged 1 commit intomainfrom
tte/fix-release-pipeline-major-band
May 1, 2026
Merged

Use a dist-tag for major releases that doesn't parse as semver#9627
tobias-tengler merged 1 commit intomainfrom
tte/fix-release-pipeline-major-band

Conversation

@tobias-tengler
Copy link
Copy Markdown
Member

No description provided.

Copilot AI review requested due to automatic review settings May 1, 2026 05:05
@tobias-tengler tobias-tengler merged commit b55a01f into main May 1, 2026
9 checks passed
@tobias-tengler tobias-tengler deleted the tte/fix-release-pipeline-major-band branch May 1, 2026 05:06
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the release workflow’s npm dist-tag strategy so “major line” tags don’t look like semver, avoiding package-manager ambiguity when users install by tag.

Changes:

  • Change major-line dist-tags from ${MAJOR} (e.g., 15) to latest-${MAJOR} (e.g., latest-15) for both the platform packages and the meta package.
  • Keep latest as the primary tag for the highest stable major, while also applying the new latest-${MAJOR} secondary tag.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

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.

2 participants