Conversation
This was referenced Jan 14, 2025
Merged
Contributor
|
just to be fair, |
aklkv
pushed a commit
to aklkv/addon-blueprint
that referenced
this pull request
Feb 8, 2026
* Remove release-it * Remove execa (now unused)
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
3 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.
Release processes are separate concerns from project generation, and can vary too greatly.
Projects that "work out of the box with no config":
npx create-release-plan-setup@latest --update)Projects that require config / setup
But also, it's totally valid for folks to manually release, if they just want to
pnpm publish -r