chore: enable project-specific tagged releases #1425
Merged
Conversation
This file contains 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
spypsy
changed the title
ludamad
approved these changes
Aug 10, 2023
4 tasks
ludamad
pushed a commit
that referenced
this pull request
Sep 1, 2023
Addition to #1425 Will allow us to release sandbox dockerhub image by tagging `master` with e.g. `aztec-sandbox/v1.0.0`
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.
This change should allow us to create tags for releasing a specific package from
yarn-projecte.g. Tagging
masterwithaztec.js/v0.1.1will create a v0.1.1 release only for aztec.js. Tagging withv0.1.1will release everything on that version (we still check if current version is below that to avoid mis-versioning)Checklist:
Remove the checklist to signal you've completed it. Enable auto-merge if the PR is ready to merge.