Repository navigation
ci: publish automatically when the release PR is merged - #144
Merged
Merged
Conversation
… the docs changelog
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Oct 7, 2026
This branch was successfully deployed
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.
Before: merging the release PR only prepared the release. Publish to NPM had to be run by hand, so 0.8.0 (#143) was never published. Running it would also have failed, because the docs changelog had no
## 0.8.0section.After: Publish to NPM runs on every push to
main. A smallcheckjob looks for the GitHub release of the current package version; when there is none (right after the release PR is merged) the publish job runs and publishes onlatest. Other pushes skip it. Running it by hand still works for a dry run or anothernpm_tag.Merging this PR publishes 0.8.0, since
v0.8.0has no release yet.How:
publish.ymlgets apushtrigger, acheckjob and a concurrency group; inputs are read throughDRY_RUN/NPM_TAGenv with defaults for pushes. The docs changelog gets the 0.8.0 section (en/tr, translation check passes) and CONTRIBUTING (en/tr) describes the new flow.