Skip to content

Offset preview run number to stay ahead of pre-merge versions #192

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MikeAlhayek merged 1 commit into from
Sep 14, 2026
Merged

Offset preview run number to stay ahead of pre-merge versions #192

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion .github/workflows/publish_npm.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -144,7 +144,12 @@ jobs:
VERSION="${{ steps.check-publish.outputs.release-version }}"
DIST_TAG="latest"
else
VERSION="$(node -p "require('./package.json').version").${{ github.run_number }}"
# Offset the run number so preview versions stay ahead of the pre-merge
# sequence. The previous per-package workflows reached 2.0.0-preview.180
# before they were merged into this one, which reset GitHub's run_number
# to 1. Adding 180 keeps the .N suffix monotonically increasing and above
# the last published preview.
VERSION="$(node -p "require('./package.json').version").$((180 + ${{ github.run_number }}))"
DIST_TAG="preview"
fi
echo "Publishing ${VERSION} to the '${DIST_TAG}' dist-tag."
Expand Down
Loading