🚨 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!
⚠️ You are using a yanked version of octokit ⚠️
We're getting an error that the version of octokit you're currently using is no longer installable, it most likely has been yanked. That means your deployment, CI build and local development setup are broken until you update octokit to a different version.
We recommend to merge this update 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.
Versions 4.23.0
and 4.24.0 of the octokit gem
were published containing world-writeable files.
Specifically, the gem was packed
with files having their permissions set to -rw-rw-rw- (i.e. 0666) instead of rw-r--r--
(i.e. 0644). This means everyone who is not the owner (Group and Public) with access
to the instance where this release had been installed could modify the world-writable
files from this gem.
Malicious code already present and running on your machine,
separate from this package, could modify the gem’s files and change its behavior
during runtime.
Users can use the previous version of the gem v4.22.0.
Alternatively, users can modify the file permissions manually until they are able
to upgrade to the latest version.
✅ NOTE: This remediates A security advisory was published on versions 4.23.0 and 4.24.0 of this gem. You can read more about this in the published security advisory. ✅
Within the URI template implementation in Addressable, a maliciously crafted template may result in uncontrolled resource consumption,
leading to denial of service when matched against a URI. In typical usage, templates would not normally be read from untrusted user input,
but nonetheless, no previous security advisory for Addressable has cautioned against doing this.
Users of the parsing capabilities in Addressable but not the URI template capabilities are unaffected.
Release Notes
2.8.0 (from changelog)
fixes ReDoS vulnerability in Addressable::Template#match
no longer replaces + with spaces in queries for non-http(s) schemes
fixed encoding ipv6 literals
the :compacted flag for normalized_query now dedupes parameters
fix broken escape_component alias
dropping support for Ruby 2.0 and 2.1
adding Ruby 3.0 compatibility for development tasks
drop support for rack-mount and remove Addressable::Template#generate
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
@depfu rebase
Rebases against your default branch and redoes this update
@depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@depfu close
Closes this PR and deletes the branch
@depfu reopen
Restores the branch and reopens this PR (if it's closed)
@depfu pause
Ignores all future updates for this dependency and closes this PR
@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)
Commit-Lint commands
You can trigger Commit-Lint actions by commenting on this PR:
- `@Commit-Lint merge patch` will merge dependabot PR on "patch" versions (X.X.Y - Y change)
- `@Commit-Lint merge minor` will merge dependabot PR on "minor" versions (X.Y.Y - Y change)
- `@Commit-Lint merge major` will merge dependabot PR on "major" versions (Y.Y.Y - Y change)
- `@Commit-Lint merge disable` will desactivate merge dependabot PR
- `@Commit-Lint review` will approve dependabot PR
- `@Commit-Lint stop review` will stop approve dependabot PR
🚨 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!
⚠️ You are using a yanked version of octokit ⚠️
We're getting an error that the version of octokit you're currently using is no longer installable, it most likely has been yanked. That means your deployment, CI build and local development setup are broken until you update octokit to a different version.
We recommend to merge this update 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?
↗️ octokit (indirect, 4.17.0 → 4.25.1) · Repo · Changelog
Security Advisories 🚨
🚨 Octokit gem published with world-writable files
Release Notes
4.25.1
4.25.0
4.24.0
4.23.0
4.22.0
4.21.0
4.20.0
4.19.0
4.18.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
↗️ addressable (indirect, 2.7.0 → 2.8.0) · Repo · Changelog
Security Advisories 🚨
🚨 Regular Expression Denial of Service in Addressable templates
Release Notes
2.8.0 (from changelog)
Does any of this look wrong? Please let us know.
↗️ faraday (indirect, 1.0.0 → 2.3.0) · Repo · Changelog
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
↗️ sawyer (indirect, 0.8.2 → 0.9.2) · Repo
Release Notes
0.9.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 8 commits:
Release 0.9.2
Version bump to 0.9.2
Add `dig` and `fetch` to `Sawyer::Resource` (#74)
Version bump to 0.9.1
Specify correct minimal Faraday version (#73)
Version bump to 0.9.0
Enhance Faraday Support (#72)
Allow closing underlying connection. (#67)
🆕 faraday-net_http (added, 2.0.3)
🆕 ruby2_keywords (added, 0.0.5)
🗑️ multipart-post (removed)
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