fix(deps): bump astro to 7.1.3 + re-resolve brace-expansion to clear osv-scanner (#636)#637
Merged
Conversation
…osv-scanner (#636) The osv-scanner required check (`Secrets, deps, and workflow scan`) fails on main's yarn.lock, ejecting every PR from the merge queue (observed on #623). Advisories were published after PR-open scans, so PR-level checks are green while the merge_group re-scan is red. - astro 7.0.5 -> 7.1.3 (docs/package.json). Fixes GHSA-4g3v-8h47-v7g6 (XSS), GHSA-8mv7-9c27-98vc, GHSA-f48w-9m4c-m7f5. NOTE: intentionally 7.1.3, NOT 7.1.0 — 7.1.0 (the version Dependabot #631/#630 target, and the "fixed" version GHSA-4g3v cites) is flagged malicious by MAL-2026-10726. 7.1.3 is the current `latest` and is past the single poisoned release. - brace-expansion re-resolved within existing ^1.1.7/^2.0.2 ranges: 1.1.15 -> 1.1.16 and 2.1.1 -> 2.1.2 (GHSA-3jxr-9vmj-r5cp). Transitive-only; no resolutions pin needed. Lockfile-only (+ one version string). Verified: `mise run security:deps` exits 0, `mise //docs:build` builds 68 pages clean, `mise run security:retire` clean. Supersedes Dependabot #631/#630 (which bump to the malicious 7.1.0). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
isadeks
approved these changes
Jul 21, 2026
isadeks
left a comment
Contributor
There was a problem hiding this comment.
Approving — verified independently.
Correct fix, correctly scoped. Diff is lockfile-only + one version string (docs/package.json + yarn.lock), no code touched:
astro 7.0.5 → 7.1.3— clears the three XSS advisories (GHSA-4g3v-8h47-v7g6/-8mv7-9c27-98vc/-f48w-9m4c-m7f5), and deliberately 7.1.3, not the7.1.0Dependabot #631/#630 targeted —7.1.0is flagged malicious byMAL-2026-10726(confirmed:7.1.0returns that advisory in OSV,7.1.3is clean).brace-expansion 1.1.15 → 1.1.16+2.1.1 → 2.1.2(GHSA-3jxr-9vmj-r5cp) — re-resolved within the existing caret ranges, noresolutionspin needed. Both patched versions confirmed clean in OSV.
All 8 checks green, incl. the previously-failing Secrets, deps, and workflow scan — osv-scanner logs "No issues found" (exit 0). This clears the merge_group re-scan that was ejecting approved PRs from the queue, and the same red check on #616 and other open PRs.
Superseding #631/#630 is the right call — both bump into the poisoned 7.1.0.
This was referenced Jul 21, 2026
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.
What & why
The
osv-scannerrequired check (Secrets, deps, and workflow scan→Dependency scan (osv-scanner))fails on
main'syarn.lock, which ejects every PR from the merge queue — themerge_groupre-scan runs against the latest main and fails any queued PR. Observed on #623, which is otherwise
approved + CLEAN but kept getting removed from the queue by
github-merge-queue[bot].These advisories were published after the affected PRs' PR-open scans, so PR-level checks are
green while the
merge_groupre-scan is red.Closes #636.
Changes (lockfile-only + one version string)
7.0.5→7.1.3(docs/package.json). FixesGHSA-4g3v-8h47-v7g6(reflected XSS),GHSA-8mv7-9c27-98vc,GHSA-f48w-9m4c-m7f5.GHSA-4g3vlists its fix as7.1.0, and Dependabotchore(deps): npm: bump astro from 7.0.5 to 7.1.0 #631 / chore(deps): npm: bump astro from 7.0.5 to 7.1.0 in /docs #630 bump to exactly that — but
7.1.0is flagged malicious byMAL-2026-10726(published 2026-07-16, affectsonly 7.1.0).
7.1.3is the currentlatestand is past the single poisoned release.^1.1.7/^2.0.2ranges:1.1.15 → 1.1.16and2.1.1 → 2.1.2(GHSA-3jxr-9vmj-r5cp, CVSS 7.7). Transitive-only, so noresolutionspin was needed — the caret ranges already permit the patched versions.Verification
mise run security:deps(osv-scanner, exact CI command) → No issues found (exit 0).mise //docs:build→ 68 pages built clean under astro 7.1.3.mise run security:retire→ clean.origin/main..HEAD) → no leaks (the pre-push full-history hit ispre-existing history on other branches, unrelated to this diff).
Supersedes
Dependabot #631 and #630 (both bump astro to the malicious
7.1.0) — close as supersededonce this lands.