Skip to content

chore(deps): update dependency prettier to v3.9.6 - #121

Merged
yumike merged 1 commit into
mainfrom
renovate/prettier-3.x-lockfile
Aug 7, 2026
Merged

chore(deps): update dependency prettier to v3.9.6#121
yumike merged 1 commit into
mainfrom
renovate/prettier-3.x-lockfile

Conversation

@renovate

@renovaterenovateBot commented Jul 25, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

PackageChangeAgeConfidence
prettier (source)3.9.53.9.6ageconfidence

Release Notes

prettier/prettier (prettier)

v3.9.6

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovateBotforce-pushed the renovate/prettier-3.x-lockfile branch from 5d8f02c to eeb7e0fCompareJuly 30, 2026 18:42
@yumike
yumike merged commit 99c0bda into mainAug 7, 2026
1 check passed
@yumike
yumike deleted the renovate/prettier-3.x-lockfile branch August 7, 2026 08:40
yumike added a commit that referenced this pull request Aug 9, 2026
…161)
Alerts #121 (high, GHSA-mwp4-54f8-5fhr / CVE-2026-69192 — Address4 decodes
leading-zero octets as decimal while resolvers decode them as octal, allowing
SSRF and trust-boundary bypass) and #41 (medium) were both unreachable:
express-rate-limit 8.3.1 pins ip-address to exactly "10.1.0", and an exact pin
admits no upgrade.
express-rate-limit 8.5.1 relaxed that to "^10.2.0", and @backstage/backend-
defaults already declares "^8.2.2", which accepts 8.6.2. Re-resolving it therefore
lifts ip-address, and a second pass collapses the remaining socks copy
("^10.0.1", left at 10.1.0 by the first step) onto the same version:
express-rate-limit 8.3.1 -> 8.6.2
ip-address 10.1.0 -> 10.4.0 (single copy, was two mid-way)
express-rate-limit uses ip-address to parse client IPs for rate limiting, which
is itself a trust boundary — an octal/decimal parsing discrepancy there is a
rate-limit evasion primitive. It reaches us only through backend-defaults, a
devDependency of rw-backend and a dependency of the private demo backend, so it
is not in any published plugin's graph.
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@yumike