build: declare breaking change #32
Merged
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
size-limit report 📦
|
ClaraTschamon
force-pushed
the
ct/trigger-breaking-change
branch
from
0e44af6 to
4c99172
Compare
ClaraTschamon
changed the title
BREAKING CHANGE: update next, boemly and strapi-slices
ClaraTschamon
force-pushed
the
ct/trigger-breaking-change
branch
from
4c99172 to
3cb522a
Compare
ClaraTschamon
changed the title
rschiffer
approved these changes
Jan 15, 2026
|
🎉 This PR is included in version 4.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Adding the BREAKING CHANGE message that i forgot in the previous commit to trigger a release