feat: setup release-it
#658
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
vscav
force-pushed
the
move-release-it
branch
from
2d4623e
to
80a2dc8
Compare
michelegera
reviewed
Nov 16, 2023
vscav
force-pushed
the
move-release-it
branch
from
80a2dc8
to
7917abe
Compare
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.
In this MR, we set up everything needed to use
release-itto release the addon.We also get rid of the
release.ymlscript. As a reference, the releases ofember-lottieare successfully published to the npm registry even without this script, asrelease-itis supposed to do it automatically.Also, we can't use the last version of
release-it, as there is a peer dependency incompatibility.