Closed depfu[bot] closed 6 months ago
Well Done! Your tests are still passing. https://ci.suse.de/job/scc-RMT-integration-tests/352445/console If the given link has expired,you can force a Prophet rerun by just deleting this comment. (Merged cc0da53bf944e42f37d330fb8d43e408a25c0831 into 4926fb902d3e9c4583c4251415585c8cad14c22f)
🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ puma (5.6.7 → 5.6.8) · Repo · Changelog
Security Advisories 🚨
🚨 Puma HTTP Request/Response Smuggling vulnerability
Release Notes
5.6.8 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 2 commits:
5.6.8
Merge pull request from GHSA-c2f4-cvqm-65w2
↗️ nio4r (indirect, 2.5.9 → 2.7.0) · Repo · Changelog
Release Notes
2.7.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 19 commits:
Bump minor version.
For some reason, I had to add `bake` as a direct dependency.
Update changes.
Convert NIO objects to TypedData API (#310)
Fix license (#309)
Fix changelog_uri in gemspec metadata (#303)
Disable `bake-modernize` as it's not supported on Ruby v2.4.
Bump patch version.
Update copyrights/license & funding URI.
Add bake-gem and bake-modernize for maintenance tasks.
Don't update `io` which is subsequently stored. Retain the original. (#306)
Resolve issue loading both nio and nio4r gems (#302)
Avoid direct access to IO internals. (#301)
Update changes.
Remove codeql as it seems tricky to use without extra research.
Prefer lower case.
Create codeql.yml
Fix conversion loses int precision using SIZET2NUM. (#297)
Add more notes for building jruby package.
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands