Javascript dependency: Bump tar from 6.2.1 to 7.5.15 in /web#9962
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Javascript dependency: Bump tar from 6.2.1 to 7.5.15 in /web#9962dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [tar](https://github.com/isaacs/node-tar) from 6.2.1 to 7.5.15. - [Release notes](https://github.com/isaacs/node-tar/releases) - [Changelog](https://github.com/isaacs/node-tar/blob/main/CHANGELOG.md) - [Commits](isaacs/node-tar@v6.2.1...v7.5.15) --- updated-dependencies: - dependency-name: tar dependency-version: 7.5.15 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
the
Dependencies
9 tasks
asheshv
added a commit
that referenced
this pull request
Jun 8, 2026
) Combined fix for 8 packages flagged by GitHub Dependabot (collapsing 6 of them from open dependabot bump PRs and 4 from transitive vulnerabilities with no existing PR). All eight are transitive — no direct dep changes — so we override via `resolutions` in web/package.json and let yarn collapse duplicate-version entries during install. Resolved (pre → post via resolution): Runtime: ws 8.20.0 -> 8.21.0 (patched 8.20.1) Dev: @xmldom/xmldom 0.7.13 -> 0.8.13 (patched 0.8.13) serialize-javascript 6.0.2, 7.0.5 -> 7.0.5 (patched 7.0.5) ip-address 10.1.0, 10.2.0 -> 10.2.0 (patched 10.1.1) postcss 8.5.8, 8.5.15 -> 8.5.15 (patched 8.5.10) qs 6.15.0 -> 6.15.2 (patched 6.15.2) @tootallnate/once 2.0.0 -> 2.0.1 (patched 2.0.1) tar (7.x lineage) 7.5.13 -> 7.5.16 (patched 7.5.11) The tar 6.2.1 lineage (consumed via ^6.1.2/^6.1.11) is unaffected by these CVEs (alert ranges are 7.x-only), so the resolution is scoped `tar@npm:^7.5.4` to leave it on 6.2.1. Supersedes open dependabot PRs #9956 (ws), #9962 (tar), #9966 (@tootallnate/once), and #9974 (qs) — one CI cycle instead of four. Verification: - yarn install — clean (only pre-existing peer-dep warnings about @mui/system, aspen-core, eve, etc.; no new ones) - yarn run test:js-once — 824 / 824 pass across 140 test suites - yarn run bundle:dev — webpack compiled successfully - All 8 packages confirmed at safe versions via lockfile audit; duplicate entries collapsed (yarn.lock net -64 lines) Out of scope (cannot fix here): - paramiko (#276 #278): no patched version exists; bump-to-5.0.0 PRs #9927/#9930 audited 2026-05-20 and deferred to Q4 2026 over SSH bastion compat risk - elliptic (#176): no patched version, dev-only, low severity - flatted (#224): alert is stale; lockfile already at 3.4.2 (patched); will auto-dismiss on next dependabot rescan * chore(deps): bump Python deps to latest 3.9-compatible Picks up five Python dependency bumps that are 3.9-safe (still resolve under Python 3.9 per PyPI requires_python). Four supersede open dependabot PRs: - certifi 2026.4.22 -> 2026.5.20 (no gate; CA bundle refresh; supersedes dependabot #9977 / #9979) - typer 0.25.* -> 0.26.* (py > 3.9 row only; supersedes dependabot #9995 / #9999) - testscenarios 0.6.1 -> 0.6.2 (py > 3.9 row only; supersedes dependabot #9980) - urllib3 2.6.* -> 2.7.* (py > 3.9 row only) Picks up two HIGH-severity security fixes in urllib3 2.7.0 (2026-05-07): GHSA-mf9v-mfxr-j63j (decompression-bomb safeguards bypassed under drain_conn / Brotli stream patterns) and GHSA-qccp-gfcp-xxvc (ProxyManager.connection_from_url did not strip sensitive headers on cross-host redirects). 2.7.0 requires Python >=3.10, which the existing 'python_version > 3.9' gate already enforces. - Flask-Security-Too 5.4.* -> 5.6.* (py <= 3.9 row only) Closes a roughly 2-year gap between the 3.9 row (last pin from March 2024) and the py > 3.9 row (already on 5.8.*). 5.5/5.6 only touched flows pgAdmin doesn't use (register V2, MFA / WebAuthn templates, username recovery/changing, secret_key rotation) and config pgAdmin overrides (default hash bcrypt->argon2 sidestepped by SECURITY_PASSWORD_HASH = 'pbkdf2_sha512'). The contract changes that mattered (LoginForm.validate -> is_active, UserMixin.is_locked hook, single-kwarg find_user) are all already exercised in production via the existing FST 5.8.* / Python 3.10+ deployments.
Contributor
Author
|
Looks like tar is no longer updatable, so this is no longer needed. |
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.
Bumps tar from 6.2.1 to 7.5.15.
Changelog
Sourced from tar's changelog.
... (truncated)
Commits
87cc3097.5.157aef486fix: regression in pending links detection6244eb37.5.149704d8cstricter protection against hardlinks preempting their targets700734fupdate workflows and depsd6611ae7.5.13119c401fix(extract): prevent raced symlink writes outside cwd2a294d37.5.1201082a4fix: reject top promise on floating addFilesAsync rejectionsdd1c36alintingMaintainer changes
This version was pushed to npm by isaacs, a new releaser for tar since your current version.
Install script changes
This version adds
preparescript that runs during installation. Review the package contents before updating.Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.