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.
ios_publish
rule for publishing a built zip to SPM + CocoaPodsspm_publish
rule for dumping + tagging zip into another repothe
ios_publish
rule will put stable releases (versions that dont have any semver metadata) onto one branch, and prerelease/canary versions will update a branch for the semver version its targetting.so
0.7.4--canary.391.13829
would tag commits on branch0.7.4
so
0.7.4-next.0
would tag commits on branch0.7.4
and
0.7.4
would tag commits on branchmain
after a stable release, the corresponding branch with that version would no longer be needed and would be simple to delete as well as any prerelease/canary tags prefixed with the new version for player-ui/player#407