chore: use embroider/release-plan #73
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
bantic
force-pushed
the
bantic/release-plan
branch
from
67ad8cc to
add61c5
Compare
bantic
changed the title
mixonic
approved these changes
Jan 14, 2025
Merged
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.
Updates the repo to use https://github.com/embroider-build/release-plan.
I used the setup script from https://github.com/embroider-build/create-release-plan-setup.
To prepare to use the changes, I've also added an NPM_TOKEN secret, following the guidance at https://github.com/embroider-build/create-release-plan-setup#create-a-npm_token
I'm not sure how fully it is possible to test this before merging. This is what I've done:
npx release-plan explain-plannpx release-plan gather-changesBoth of these look good to me.