chore: retarget workflows from v4 to main#106
Merged
Conversation
The v4 branch was promoted to main; the changesets release step in build.yml was still gated on refs/heads/v4, so no Version Packages PR was being opened for pushes to main.
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 v4 branch was promoted to
main(old main preserved asv3), but the CI workflows still referencedv4:build.yml/check.yml/test.ymltrigger onbranches: [main, v4]— harmless but stalebuild.yml's changesets release step is gated onrefs/heads/v4, so pushes tomainnever runchangesets/action— which is why no Version Packages PR was opened for the 13 pending changesetsRetarget everything at
main. Once merged, the next Build run onmainshould open the Version Packages (beta) PR.