Switch Front to PR-gated shared release workflows - #25
Merged
Merged
Conversation
Merged
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.
The last Front release failed because org rulesets now require PRs onto
main. The oldReleaseworkflow still committedCHANGELOG.mdstraight tomain(GH013: Changes must be made through a pull request).This matches Prime: shared
edalzell/github-workflowsv1.4.0.release/vX.Y.Zchangelog PR.dist.tar.gz(Front still ships compiled assets viacomposer-dist-plugin; Prime does not, so this is the one extraupload_assets: trueinput).Satis still rebuilds on
release: published.Before the next release: add a repo secret
RELEASE_TOKEN(fine-grained PAT with Contents + Pull requests write, same one Prime uses). It is not on this repo yet. Release Prepare also uses it to check@transformstudios/maintainers.