Skip to content

chore: enable project-specific tagged releases#1425

Merged
iAmMichaelConnor merged 1 commit intomasterfrom
sp/package-tag-release
Aug 11, 2023
Merged

chore: enable project-specific tagged releases#1425
iAmMichaelConnor merged 1 commit intomasterfrom
sp/package-tag-release

Conversation

@spypsy
Copy link
Member

@spypsy spypsy commented Aug 4, 2023

This change should allow us to create tags for releasing a specific package from yarn-project
e.g. Tagging master with aztec.js/v0.1.1 will create a v0.1.1 release only for aztec.js. Tagging with v0.1.1 will 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.

  • If the pull request requires a cryptography review (e.g. cryptographic algorithm implementations) I have added the 'crypto' tag.
  • I have reviewed my diff in github, line by line and removed unexpected formatting changes, testing logs, or commented-out code.
  • Every change is related to the PR description.
  • I have linked this pull request to relevant issues (if any exist).

@spypsy spypsy changed the title enable repo-specific tagged releases chore: enable project-specific tagged releases Aug 4, 2023
@iAmMichaelConnor iAmMichaelConnor merged commit 28cbe7b into master Aug 11, 2023
@iAmMichaelConnor iAmMichaelConnor deleted the sp/package-tag-release branch August 11, 2023 10:27
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

Labels

None yet

Projects

No open projects
Archived in project

Development

Successfully merging this pull request may close these issues.

3 participants