Lock to rack-cors 2.0.0
to avoid problem with rack-cors 2.0.1
#10173
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.
🛠 Summary of changes
Right now all lint tasks are failing in
main
because there's a newly reported file permission vulnerability inrack-cors
(link) version 2.0.1 (latest). This PR addresses that by locking our version to 2.0.0, the latest version ofrack-cors
without this vulnerability (link).Presumably we'll be able to use 2.0.1 again once they've patched the problem.
The error:
📜 Testing Plan
make lint
inmain
notice the failure.make lint
in this branch, the failure is gone.