Repository navigation
Conversation
- Publish the client packages under the latest dist-tag when a release tag is pushed, after checking that it is a final release tag matching the package version, signed and verified by GitHub, and that CI passed on the tagged commit - Exclude javax tags, which have no npm release - Skip next publishes of release versions in the change detection step Part of: eclipse-glsp/glsp#1823
5 of 7 tasks
Contributor
Author
|
Superseded by #150, which now includes the |
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.
What it does
Publishes a release under the
latestdist-tag when its signed tagv<version>is pushed, replacing the dispatch from the umbrella release workflow.glsp releng release(eclipse-glsp/glsp-core#41) pushes this tag once the release PR is merged and CI passed on the release commit. Publishing stays inpublish.ymlbecause npm trusted publishing is bound to the workflow file.v<version>tags and publish underlatestafter checking that the tag is a final release (v<major>.<minor>.<patch>) matching the package version, that it is signed and verified by GitHub, and that CI passed on the tagged commitnextpublishes of release versions in the change detection stepPart of: eclipse-glsp/glsp#1823
How to test
The tag-triggered publish runs for the first time with the next real release.
nextpublish still runs and publishes as beforeFollow-ups
v*tagsprepare-release.ymlandpublish-release.ymlafter the first release with the new flowv<version>.javax)Changelog