Dependency updates to remove critical warnings and fix release process #3215
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
…o fixes the critical dependency error
malchata
approved these changes
May 27, 2023
|
Hi Thanks! |
|
if I understand correctly, node 16 was defined as the minimum required version in 6.6.0 in a "soft" way and then the 6.6.1 enforced it in packages.json. This is breaking the build of our application :( IMHO this is a BC break should have happened in a 7.0.0 |
|
I agree, this should not be considered a minor/patch release. @tropicadri could it be possible to move this to 7.0.0 and revert 6.6.1 ? |
This was referenced Apr 24, 2024
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.
Dependency updates to remove critical warnings and fix release process