This repository was archived by the owner on Jul 6, 2026. It is now read-only.
chore: auto-release on merge to main#686
Merged
Merged
Conversation
Replace tag-triggered release with automatic production publish on push to main. Lerna versions (patch) and publishes all packages. Remove canary/internal publish from staging workflow since release now handles npm publishing. Upgrade actions/checkout and actions/setup-node to v4. Made-with: Cursor
SamRosignoli
approved these changes
Apr 21, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Summary
@trycourier/*packages to npm on every mergeactions/checkoutandactions/setup-nodefrom v2 to v4 to fix Node 20 deprecation warningsMade with Cursor