Repository navigation
Publish from GitHub releases, with next pre-releases - #5
Merged
Merged
Conversation
korkje
force-pushed
the
release/github-releases
branch
4 times, most recently
from
September 1, 2026 23:33
37ef9dc to
f84e511
Compare
korkje
force-pushed
the
release/github-releases
branch
from
September 1, 2026 23:35
f84e511 to
1856b4b
Compare
The Publish workflow now runs on release:published instead of tag pushes and takes the version from the release tag, so cutting a release is a GitHub UI action rather than a local npm version + push. A tag with a pre-release suffix must be marked pre-release and lands on the next dist-tag; the workflow refuses mismatches in either direction. package.json therefore carries 0.0.0-dev in git. Dev builds skip the update check (there is nothing to compare against), and isNewer learns that a release outranks its own pre-releases so users on next get the notice once the release ships. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
korkje
force-pushed
the
release/github-releases
branch
from
September 1, 2026 23:43
1856b4b to
1f177c9
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stack 2/6 — depends on #4
Releases are now cut from the GitHub UI instead of a local
npm version+ tag push.release: published. The version comes from the release tag; the workflow stamps it withnpm version --no-git-tag-versionbeforenpm publish.v1.2.3→latest.v1.3.0-next.0→nextdist-tag, and must be marked pre-release. Mismatches in either direction fail the job.package.jsonstays at0.0.0-devin git. Dev builds skip the update check (nothing to compare against).isNewerlearns that a release outranks its own pre-releases, so users on@nextget the notice once the release ships.The workflow file keeps its name (
publish.yml) because npm trusted publishing is bound to it. The trigger change needs no config change on npm.🤖 Generated with Claude Code