fix: lock react components version #439
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
jonaslagoni
requested review from
fmvilas,
derberg,
magicmatatjahu and
asyncapi-bot-eve
as code owners
fmvilas
previously approved these changes
Aug 31, 2023
|
blocked by #440 |
|
@jonaslagoni but this is not going to work. I assume you want to make sure automated bump will not work and upgrade? it do not understand existence of anyway, tests will not let the bump go through -> see #437 so what you're trying to solve here? stop having automated PRs like #437 ? |
|
oh, ok, so not autobump related, thanks for clarification |
derberg
approved these changes
Aug 31, 2023
|
Kudos, SonarCloud Quality Gate passed!
|
|
/rtm |
|
🎉 This PR is included in version 0.28.4 🎉 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.
Description
This PR locks the react components to not use the
1.0.0-next.48version which contains breaking changes for this library.Related issue(s)
Fixes #438