Repository navigation
chore(deps): bump addressable from 2.9.0 to 2.9.2 - #3073
Merged
Merged
Conversation
The Security Audit job fails on five medium advisories for 2.9.0, all fixed in 2.9.1: GHSA-8gmh-2hhj-2hv9, GHSA-9crm-g4mf-wc5j, GHSA-9f42-57jx-vpp3, GHSA-j82w-28jv-3pmj, and GHSA-qq38-m9mg-xjj5. Addressable is a transitive dependency of capybara, css_parser, launchy, premailer, and webmock. No Gemfile constraint needed changing.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
bundler-auditfails on the current lockfile:addressable2.9.0 carries five medium advisories, all fixed in 2.9.1. This bumps it to 2.9.2, so the Security Audit job goes green again.Advisories: GHSA-8gmh-2hhj-2hv9, GHSA-9crm-g4mf-wc5j, GHSA-9f42-57jx-vpp3, GHSA-j82w-28jv-3pmj, GHSA-qq38-m9mg-xjj5.
Addressable is transitive via capybara, css_parser, launchy, premailer, and webmock; no direct constraint needed changing. The lockfile checksum moved with the version.
Review notes
Only
Gemfile.lockchanges. Check the resolved version and checksum; no application code or Gemfile constraint changed.One full-suite run reported a single failure that five later runs did not reproduce. I did not capture its name before the output scrolled; it was not in the files this change touches.