Skip to content

release: allow same-version npm publish so 26.5 ships #781

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
danieljohnmorris merged 2 commits into from
May 24, 2026
+10 −2
Merged

release: allow same-version npm publish so 26.5 ships #781

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b6c65d0
release: allow same-version npm publish so 26.5 ships
danieljohnmorris May 24, 2026
5a40500
Merge remote-tracking branch 'origin/main' into fix/release-npm-allow…
danieljohnmorris May 24, 2026
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
12 changes: 10 additions & 2 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -200,7 +200,11 @@ jobs:

- name: Set npm version from tag
working-directory: npm
run: npm version ${{ needs.validate-tag.outputs.semver }} --no-git-tag-version
# --allow-same-version: the in-repo package.json is already bumped to the
# release version (e.g. 26.5.0), so a plain `npm version` aborts with
# "Version not changed" and blocks the publish. This makes the step a
# no-op when already at the target version rather than failing.
run: npm version ${{ needs.validate-tag.outputs.semver }} --no-git-tag-version --allow-same-version

- name: Publish to npm
working-directory: npm
Expand Down Expand Up @@ -237,7 +241,11 @@ jobs:

- name: Set npm version from tag
working-directory: pi
run: npm version ${{ needs.validate-tag.outputs.semver }} --no-git-tag-version
# --allow-same-version: the in-repo package.json is already bumped to the
# release version (e.g. 26.5.0), so a plain `npm version` aborts with
# "Version not changed" and blocks the publish. This makes the step a
# no-op when already at the target version rather than failing.
run: npm version ${{ needs.validate-tag.outputs.semver }} --no-git-tag-version --allow-same-version

- name: Publish to npm
working-directory: pi
Expand Down
Loading