derive stable release trigger from package version#54
Merged
Conversation
github-actions
Bot
added
vouch:trusted
tarik02
force-pushed
the
fix/drop-release-pr-marker
branch
from
3df2c6e to
f5b51ab
Compare
tarik02
changed the title
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
1 participant
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 Changed
.github/release-pr/stable.jsonmarker from the stable release PR flow.mainnow derive from package manifests: publish when the shared package version is a stable fork version andv<version>does not already exist.Why
The repo does not need a release marker file or commit-message coupling. Package versions are the source of truth, and tags/releases record what has already been published.
Checklist