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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[P1] Update yarn.lock to keep dependency upgrade effective
Changing
@openapitools/openapi-generator-clito 2.23.2 indevDependencieswithout regeneratingyarn.lockleaves the lock file still pinning 2.17.0. On Yarn 4 installs run with--immutable(commonly used in CI) this mismatch will error out, and if installs proceed locally the dependency remains at the vulnerable 2.17.0 so the security fix never applies. Re-runyarn up @openapitools/openapi-generator-cliand commit the updated lockfile/cache.Useful? React with 👍 / 👎.