chore(deps): refresh lockfile to clear all open security advisories - #96
Merged
Conversation
`conventional-changelog-conventionalcommits` used to force every commit note's title to "BREAKING CHANGES" before rendering. Since v10.3 the preset preserves each note's own title and the writer emits one heading per distinct title, so release-please's synthesized `Migration` note (the `# Migration` section lifted out of a breaking change's body) would render as a stray `### MIGRATION` section instead of appearing under `### ⚠ BREAKING CHANGES`. Retitle the note to `BREAKING CHANGE` when handing it to the writer so the rendered changelog stays the same across the preset upgrade. The parsed `ConventionalCommit` still carries the `Migration` title. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
Re-resolves every transitive dependency within the existing `package.json` ranges, so no direct dependency range changes. `pnpm audit` now reports no known vulnerabilities (previously 13 high, 6 moderate, 2 low). Resolves the flagged packages: - `brace-expansion` 1.1.15 -> 1.1.18 and 5.0.6 -> 5.0.9 (GHSA-3jxr-9vmj-r5cp, GHSA-mh99-v99m-4gvg, GHSA-rgw5-rvv9-x895) - `js-yaml` 4.1.1 -> dropped from the tree (GHSA-h67p-54hq-rp68, GHSA-52cp-r559-cp3m, GHSA-5p4m-2wfm-xmqj) - `fast-uri` 3.1.2 -> 3.1.6 (GHSA-4c8g-83qw-93j6, GHSA-v2hh-gcrm-f6hx, GHSA-7p8r-x3mc-p8w7) - `undici` 6.25.0 -> 6.28.0 (GHSA-35p6-xmwp-9g52, GHSA-g8m3-5g58-fq7m, GHSA-p88m-4jfj-68fv, GHSA-m8rv-5g2x-5cg5, GHSA-v3r7-h72x-cjcm, GHSA-8xcm-r25x-g524) - `vite` 8.0.13 -> 8.2.2 (GHSA-fx2h-pf6j-xcff, GHSA-v6wh-96g9-6wx3) Bump the existing `brace-expansion` and `undici` override floors to the newly patched versions, and add a `vite` override: `vitest` accepts `vite@^6 || ^7 || ^8`, so a plain resolve happily stays on a vulnerable 8.0.x. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
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.
Clears all 20 open Dependabot alerts.
pnpm auditgoes from 13 high / 6 moderate / 2 low to no known vulnerabilities.None of the open Dependabot PRs would have fixed these — every alert is on a transitive dependency, so the fix is a lockfile/override change rather than a direct dependency bump.
chore(deps): refresh lockfileRe-resolves every transitive dependency within the existing
package.jsonranges.package.jsonis untouched — no direct dependency range churn.brace-expansionjs-yamlfast-uriundiciviteIn
pnpm-workspace.yaml, the existingbrace-expansionandundicioverride floors move up to the newly patched versions, and aviteoverride is added —vitestacceptsvite@^6 || ^7 || ^8, so a plain resolve happily sits on a vulnerable 8.0.x indefinitely.fix: keep Migration notes under the breaking changes headingThe refresh pulls
conventional-changelog-conventionalcommits10.2.1 → 10.4.0. That preset used to force every commit note's title toBREAKING CHANGESbefore rendering; since v10.3 it preserves each note's own title and the writer emits one heading per distinct title.The practical effect: release-please's synthesized
Migrationnote (the# Migrationsection lifted out of a breaking change's body insrc/commit.ts) would render as a stray### MIGRATIONsection instead of a bullet under### ⚠ BREAKING CHANGES. A snapshot test caught it.src/changelog-notes/default.tsnow retitles the note toBREAKING CHANGEwhen handing it to the writer, so rendered changelogs are unchanged across the preset upgrade. The parsedConventionalCommitstill carries theMigrationtitle.This commit is a no-op against the old dependency versions (verified — the old preset retitled the note anyway), so both commits are green independently and the history stays bisectable.
Verification
On Node 24.15.0, all clean:
pnpm install --frozen-lockfilepnpm audit— no known vulnerabilitiespnpm peers check— no issuespnpm lint,pnpm typecheckpnpm test— 1010 passed, no snapshot updatespnpm build,pnpm build:actionEffect on the open Dependabot PRs
src/commit.tspulls inconventional-commits-filterviarequire. Real work, unrelated to security — not attempted here.@vercel/ncc0.44.1) needs apackage.jsonbump, since^0.38.4won't cross a 0.x minor. Not security-related — not attempted here.🤖 Generated with Claude Code