Repository navigation
chore: ignore nestjs-crud and next in changesets - #54
Merged
Merged
Conversation
Workaround for changesets/changesets#1228 — when core or drizzle gets a minor bump, changesets jumps these dependent packages straight to 1.0.0 because of how it treats peer dep changes. They will be versioned and published manually for now. See .internal/changesets-peer-dep-bug.md.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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.
Workaround for changesets/changesets#1228 — when
coreordrizzleget a minor bump, changesets jumps these dependent packages straight to1.0.0because of how it treats peer dep changes.For now they are added to
ignoreand will be versioned and published manually after each upstream release.