chore: auto-publish in "v*" branches #304
Merged
Conversation
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
roncohen
changed the title
main branches`
roncohen
changed the title
Contributor
|
Should we consider using tags for realses? |
laander
approved these changes
Feb 4, 2025
Contributor
Author
definitely! And I now realize this branching strategy isn't going to work because each package is independently versioned. |
Contributor
|
hmm, come to think of it, we can't really talk about the whole repo being at a specific version since it's separate packages e.g. react-sdk is at branch names could start with a version, like this branch for example is too generic / unspecific EDIT: just saw your comment above @roncohen after submitting |
roncohen
added a commit
that referenced
this pull request
Feb 26, 2025
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.
Since
mainhas gone to 1.6-alpha, we need to start a separate branch for 1.5 series releases. This'll let us run the publish script from any branch that starts withvas inv1.5.