feat(presets): add react-spring monorepo#36177
Merged
rarkins merged 1 commit intorenovatebot:mainfrom May 27, 2025
Merged
Conversation
|
|
react-spring monoreporeact-spring monorepo
rarkins
approved these changes
May 27, 2025
Contributor
Author
|
Thanks for looking into this @rarkins 🥇 I noticed that the build docs workflow is failing, but I doubt it's the changes I've introduced that's causing it. Do let me know if there's something I need to change tho 👍 |
|
🎉 This PR is included in version 40.33.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 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.
Changes
This PR groups the
react-springpackages into a single monorepo.Context
I discovered
@react-spring/*packages are being listed to be upgraded individually and therefore missing from the monorepo settings. This was after I have to configure pnpm overrides due to a vendor bug, which triggered the following entries in the renovate bot dashboard:As these packages are all published with the same version, it is justified that they are considered a monorepo group.
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: