Update release-it setup to each package vs monorepo #55
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
scalvert
requested review from
eddynaka,
GabeDeBacker,
jeffersonking,
michaelcfanning and
rwjblue
as code owners
eddynaka
approved these changes
Apr 28, 2022
|
Closing and re-opening to see if cla task works. |
|
|
|
The commits I pushed were from a different email than my MSFT one. Just amending commits now! |
scalvert
force-pushed
the
pre-pkg-release-it
branch
from
e7495b5
to
e6ddaee
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.
Since this monorepo now houses the
eslint-formatter-sarifin addition tojest-sarifandsarif-builder, it doesn't make as much sense to use therelease-it-yarn-workspacesplugin, which requires each sub-package to be versioned the same.This change pushes the release-it configuration down to the package level, and changes the tag format to follow the
<package-name>@1.2.3convention, which allows for independent versioning while still benefiting from housing these packages together.