Skip to content

chore(renovate): cap js-yaml below v5 while front-matter is an Analog peer #351

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
BryanFRD merged 4 commits into from
Sep 20, 2026
Merged

chore(renovate): cap js-yaml below v5 while front-matter is an Analog peer #351

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
54f6360
chore(renovate): cap js-yaml below v5 while front-matter is an Analog…
BryanFRD Sep 20, 2026
9959314
chore(renovate): say why the js-yaml cap is org-wide and track its re…
BryanFRD Sep 20, 2026
4597246
chore(renovate): cap js-yaml below v4 on override entries only
BryanFRD Sep 20, 2026
16dfa3e
chore(renovate): cover the package.json pnpm.overrides spelling too
BryanFRD Sep 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions default.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -119,6 +119,22 @@
"automergeStrategy": "squash",
"groupName": "FerrLabs Cargo crates"
},
{
"description": "Sites built on `@analogjs/content` pull `front-matter@4.0.2`, which calls `yaml.safeLoad`. js-yaml removed that in 4, where the stub throws, and deleted the stub in 5 (`TypeError: loader is not a function`), so either major kills the site build at config load. front-matter pins `js-yaml ^3.13.1`, so nothing reaches it except a pnpm override we wrote ourselves to clear GHSA-2883-xcg3-v3hh, and Renovate keeps proposing majors for that override key. Scoped to override entries rather than to js-yaml everywhere: a direct js-yaml dependency in any repo stays free to move, including onto 4.3.2, which carries the same fix. 3.15.2 carries it too, so an override held on 3.x is remediated. Seven sites consume `@analogjs/content` (FerrFlow, FerrVault, FerrTrack, FerrGrowth, FerrFleet, FerrLens and FerrLabs), so this is not scoped per repo. Tracked for removal in FerrLabs/.github#353, to be lifted the day Analog stops requiring front-matter.",
"matchManagers": [
"npm"
],
"matchDepTypes": [
"pnpm-workspace.overrides",
"pnpm.overrides",
"overrides",
"resolutions"
],
Comment thread
ferrfleet[bot] marked this conversation as resolved.
"matchPackageNames": [
"js-yaml"
],
"allowedVersions": "<4"
},
{
"description": "Third-party npm — quarantine for 3 days after release before opening PR, then auto-merge patch/minor. Release age is the only gate: this rule used to carry `matchMergeConfidence`, which is not a real Renovate option (the real one is `matchConfidence`) and therefore matched nothing, so the confidence gate never applied. Rather than adopt `matchConfidence` — which needs a Mend API key and reports `neutral` without one, silently disabling npm automerge everywhere — the quarantine is raised from 1 to 3 days, which is where most malicious publishes are detected and yanked. npm is deliberately stricter than the Cargo rule below: it is the ecosystem where these attacks actually land.",
"matchManagers": [
Expand Down
Loading