Remove npm dist-tag from release.yml

[tobias-tengler]

No description provided.

[Copilot]

Pull request overview

This PR updates the Nitro npm publishing steps in the release workflow to stop applying additional npm dist-tags after publishing, leaving each publish to use only the single --tag selected by release context.

Changes:

• Removed PKG env vars used only for npm dist-tag add.
• Removed SECONDARY_BAND logic that added an extra dist-tag (e.g., latest-<major>) after publish.
• Simplified publish steps to only run npm publish --tag "$PRIMARY_BAND".

Comments suppressed due to low confidence (1)

.github/workflows/release.yml:540

• Same tagging change here: for the highest stable major, the workflow now publishes only under latest and no longer applies a latest-${MAJOR} dist-tag. Please confirm this is intended; otherwise, reintroduce a second tag step or change the publish tag so major-specific installs keep working.

          # Pick the band this release publishes under, based on release context.
          if [[ "$IS_HIGHEST_STABLE_MAJOR" == "true" ]]; then
            PRIMARY_BAND="latest"
          elif [[ "$IS_STABLE" == "true" ]]; then
            PRIMARY_BAND="latest-${MAJOR}"
          elif [[ "$GIT_TAG" =~ -rc\. ]]; then

---

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