Repository navigation
chore: dual-license create-release-branch - #40
Merged
Merged
Conversation
cryptodev-2s
approved these changes
Oct 9, 2026
cryptodev-2s
left a comment
cryptodev-2s
left a comment
Contributor
There was a problem hiding this comment.
LGTM, I have checked we have no external contributor
This branch was successfully deployed
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Explanation
Apply the same MIT / Apache-2.0 dual-license setup to
create-release-branchthat the package template andchangeset-utilsuse: aLICENSEpointer file plusLICENSE.MITandLICENSE.APACHE2, with thelicensefield inpackage.jsonset to(MIT OR Apache-2.0).This prepares the package for the move into
packages/(#35), where the Yarn constraints require the dual license.Checklist