-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Upgrade sinatra dependency to 4.2.1 #18305
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: 9.2
Are you sure you want to change the base?
Conversation
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
mustermann (~> 3.0) | ||
rack (>= 3.0.0, < 4) | ||
rack-protection (= 4.1.1) | ||
rack-protection (= 4.2.1) |
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.
It looks like rack-protection
also aligns with sinatra version. I have compared with main Gemlock.file that other sub-dependencies like base64, logger, rack boundaries do not change (make sure we don't get big changes besides our intention).
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.
yep, good catch
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.
i like it. Good if CI is!
💛 Build succeeded, but was flaky
Failed CI StepsHistory |
Somehow one of the PQ CIs (part-2-of-6) hung for more than hour, retried. |
Release notes
[rn:skip]
What does this PR do?
Upgrades sinatra dependency to 4.2.1
Why is it important/What is the impact to the user?
Checklist
Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs