-
Notifications
You must be signed in to change notification settings - Fork 81
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
Update rotp β 6.3.0 (unknown) #118
Conversation
Can this be merged? There is a CVE-2024-28862 in rotp 6.2 dependency. Thanks |
pretty please someone do a |
please merge this soon, thank you! maybe @robertomiranda @pedrofurtado ? |
Adding to this, this needs to be updated ASAP @robertomiranda @guilleiguaran @bithavoc |
Thanks a lot @guilleiguaran |
Is there going to be a new release of |
@guilleiguaran any timeline on a release for this? |
@guilleiguaran rubygems |
Why not make the dependency less strict '~> 6.3' probably works as well (assuming rotp follows semver correctly) and gives users of this gem easier upgrade paths |
@guilleiguaran @robertomiranda @bithavoc sorry to be a bother but could somebody please push a rubygems release for this? π CVE-2024-28862 was published a month ago. |
yay thank you so much! |
thank you! |
Welcome to Depfu π
This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.
After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.
Let us know if you have any questions. Thanks so much for giving Depfu a try!
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
β³οΈ rotp (~> 6.2.0 β ~> 6.3.0) Β· Repo Β· Changelog
Release Notes
6.3.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 11 commits:
chore(main): release 6.3.0 (#132)
feat: Allow for non-standard provisioning URI params, eg. image/icon (#91)
chore: bootstrap releases for path: . (#131)
Chore: run CI on all pull requests (#130)
chore: docker-compose.yml: Use ruby-3.0 (#128)
Chore: CI Update for please release and Devcontainer addition of `act` (#127)
Merge pull request #126 from mdp/mdp/pr_rollup
Merge branch 'main' into mdp/pr_rollup
Add Ruby 3.2 to CI.
Merge pull request #116 from gogainda/patch-1
Merge pull request #115 from simi/patch-1
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