chore(deps): lock file maintenance

[ferrlabs-renovate]

This PR contains the following updates:

Update	Change
lockFileMaintenance	All locks refreshed

---

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

🔧 This Pull Request updates lock files to use the latest dependency versions.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "before 6am on monday"
• Automerge
  • At any time (no schedule defined)

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

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

This PR has been generated by Mend Renovate CLI.

[github-actions]

SonarQube — aucune nouvelle issue

_{Comparaison entre le projet bac à sable de cette PR et la branche par défaut : SonarQube Community n'analyse pas les PR, ce delta est calculé côté CI. Détail}

[ferrfleet]

Lockfile maintenance only: cc 1.4.2→1.4.3 and find-msvc-tools 0.1.10→0.1.11 (transitive build-deps of cc, used at compile time for native builds), both patch bumps. No API changes relevant to this repo's usage. All 22 checks green. Uneventful — approving.

[ferrfleet]

Follow-up on a re-pushed lockfile-maintenance commit (528c3bc, previously reviewed 3604863). New content since last review: zerovec-derive 0.11.4→0.11.5, a patch bump of an ICU4X derive-macro crate pulled in transitively (not a direct dependency) — no relevant API changes. The previously-reviewed cc 1.4.2→1.4.3 and find-msvc-tools 0.1.10→0.1.11 bumps are unchanged. All completed checks are green; remaining jobs are the standard test/coverage matrix, unrelated to a lockfile-only diff. Uneventful — approving.

[ferrfleet]

Follow-up on a re-pushed lockfile commit (f1ee4dd, previously reviewed 528c3bc). New since last review: @ferrlabs/ui-ng 1.21.0→1.23.0 in pnpm-lock.yaml (semver-minor, within site/package.json's ^1.10.0 range). This is a private GitHub Packages registry — I can't reach its repo/changelog (FerrLabs/ui-ng isn't visible to this token) to check for breaking changes. Usage is confined to site/ (docs/marketing site: SiteShellComponent, provideSiteChrome, DocsLayoutComponent, resolveLocale, SiteChromeConfig) — the Check Site CI job, which builds that subproject, passed on this commit, so the new version at least builds and renders. The previously-reviewed cc/find-msvc-tools/zerovec-derive Cargo bumps are unchanged. All 22 checks green. Nothing blocking — approving.

[ferrfleet]

Follow-up on a re-pushed lockfile commit (cdf2426, previously reviewed d00ec9b). New since last review: @ferrlabs/ui-foundation 5.2.0→5.3.0 and a further @ferrlabs/ui-ng bump 1.23.0→1.24.0 (both semver-minor, within site/package.json's ^5.1.0/^1.23.0 ranges). Same as before, FerrLabs/ui-foundation and FerrLabs/ui-ng are private repos this token can't reach (404) to check changelogs. Usage is still confined to site/ — ui-foundation only via CSS import in site/src/styles.css, ui-ng via the previously-noted components — and the Check Site job, which builds that subproject, passed on this commit. Previously-reviewed cc/find-msvc-tools/zerovec-derive Cargo bumps are unchanged. Only pending status is renovate/stability-days (expected, not a CI failure); all completed checks are green. Nothing blocking — approving.

[ferrfleet]

Follow-up on a re-pushed lockfile commit (566b308, previously reviewed 76fd369). New since last review: baseline-browser-mapping 2.11.14→2.11.15 in pnpm-lock.yaml, pulled in transitively via browserslist — this is just a Baseline browser-support data refresh (dev-time build tooling), no API surface, no relevant change. The previously-flagged @ferrlabs/ui-ng 1.23.0→1.24.0 and @ferrlabs/ui-foundation 5.2.0→5.3.0 bumps are no longer part of this diff (likely landed on main separately) — nothing to review there now. The Cargo bumps (cc, find-msvc-tools, zerovec-derive) are unchanged from prior reviews. All completed checks are green; remaining jobs are the standard test/build matrix still running, no failures. Uneventful — approving.

[ferrfleet]

Follow-up on a re-pushed lockfile commit (05eae95, previously reviewed 566b308). New since last review: wrap-ansi 10.0.0→10.0.1 in pnpm-lock.yaml (patch, transitive under log-update/site build tooling) — its own dependency list dropped strip-ansi (now presumably inlined), no relevant API surface for this repo. The Coverage check is failing, but the log shows a SonarQube-side error ("The server is busy" / report upload failure), not a test or build failure — an unrelated infra flake, not caused by this diff. Previously-reviewed Cargo bumps (cc, find-msvc-tools, zerovec-derive) and baseline-browser-mapping are unchanged. Only pending status is renovate/stability-days (expected). Nothing blocking — approving.

[ferrfleet]

Follow-up on a re-pushed lockfile commit (13e3213, previously reviewed 05eae95). New since last review:

• marked 18.0.9→18.0.10 (+ marked-gfm-heading-id/marked-highlight/marked-mangle synced, @analogjs/content/@analogjs/router hash bumps as a side effect): patch, 3 bug fixes only (EOF backtick-fence parsing, em/strong mask length for astral chars, task-checkbox placement) — confirmed via upstream changelog, no breaking changes or API changes.
• @ferrlabs/ui-foundation 5.3.0→5.3.1: patch, within site/package.json's ^5.1.0 range. Same as prior rounds, FerrLabs/ui-foundation is a private repo this token can't reach (404) to check the changelog; usage is still confined to a CSS import in site/src/styles.css, and Check Site passed on this commit.
• electron-to-chromium 1.5.408→1.5.409: transitive under browserslist, pure browser-support data, no API surface.

Previously-reviewed Cargo bumps (cc, find-msvc-tools, zerovec-derive) and baseline-browser-mapping/wrap-ansi are unchanged. All completed checks are green; only renovate/stability-days is pending (expected) and a couple of matrix jobs still running with no failures. Uneventful — approving.

[ferrfleet]

Follow-up on a re-pushed lockfile commit (1265aa5, previously reviewed 13e3213). New since last review: @ferrlabs/ui-ng 1.24.0→1.24.1 in pnpm-lock.yaml, patch, within site/package.json's ^1.23.0 range. Same as prior rounds, FerrLabs/ui-ng is a private repo this token can't reach to check the changelog; usage is still confined to site/ (SiteShellComponent, provideSiteChrome, DocsLayoutComponent, resolveLocale, SiteChromeConfig), and Check Site passed on this commit. The previously-flagged @ferrlabs/ui-foundation 5.3.0→5.3.1 bump is no longer part of this diff (landed on main separately) — nothing to review there now.

Previously-reviewed Cargo bumps (cc, find-msvc-tools, zerovec-derive) and JS-side patches (marked, baseline-browser-mapping, electron-to-chromium, wrap-ansi) are unchanged.

scan / SonarQube analysis is failing (scanner exit code 1, no further detail in the log) — this diff touches only Cargo.lock/pnpm-lock.yaml, no source, so it can't be caused by this change; consistent with the Sonar infra flakiness seen on earlier commits of this PR. All other checks green or still running (standard matrix). Uneventful — approving.

[ferrfleet]

Follow-up on a re-pushed lockfile commit (d94cc3d, previously reviewed 1265aa5). New since last review: @vercel/nft 1.10.2→1.11.0 in pnpm-lock.yaml, transitive under nitropack (build-time file tracer used by the site/ build) — checked upstream release notes: one feature addition ("resolve package import wildcard trailers"), no breaking changes or removed APIs. The previously-flagged @ferrlabs/ui-ng 1.24.0→1.24.1 bump is no longer part of this diff (landed on main separately) — nothing to review there now.

Previously-reviewed Cargo bumps (cc, find-msvc-tools, zerovec-derive) and JS-side patches (marked, baseline-browser-mapping, electron-to-chromium, wrap-ansi) are unchanged. All completed checks are green; only renovate/stability-days is pending (expected) and the rest of the matrix is still running with no failures so far. Uneventful — approving.

[ferrfleet]

Follow-up on a re-pushed lockfile commit (f8cb6f1, previously reviewed d94cc3d). New since last review:

• zerovec 0.11.7→0.11.8 in Cargo.lock: patch, transitive ICU4X crate (not a direct dependency — confirmed zerovec isn't in Cargo.toml, pulled in via unicode/idna handling). No API surface for this repo.
• electron-to-chromium 1.5.408→1.5.411 (previously reviewed up to .409, now further to .411): pure browser-support data under browserslist, no API surface.
• magic-string 1.2.0→1.2.1 in pnpm-lock.yaml: patch, transitive under site/ build tooling (nitropack/vite chain), no relevant change.

All previously-reviewed bumps (cc, find-msvc-tools, zerovec-derive, marked, @vercel/nft, baseline-browser-mapping, wrap-ansi) are unchanged. No failing checks currently; remaining jobs are the standard test/build matrix still in progress. Uneventful — approving.

[ferrfleet]

Follow-up on a re-pushed lockfile commit (0f310a8, previously reviewed 865567c). Diffed file contents directly between the two commits: Cargo.lock is byte-identical. Only changes in pnpm-lock.yaml:

• @ferrlabs/ui-ng 1.25.2→1.26.0: semver-minor, within site/package.json's ^1.23.0 range. Same as prior rounds, FerrLabs/ui-ng is a private repo this token can't reach to check the changelog; usage is still confined to site/ (SiteShellComponent, provideSiteChrome, DocsLayoutComponent, resolveLocale, SiteChromeConfig).
• electron-to-chromium 1.5.413→1.5.414: transitive under browserslist (site build tooling), pure browser-support data, no API surface — same pattern as the many prior bumps of this package.

This is a fresh push (07:06 UTC); only a few fast checks have completed so far, all green, with the rest of the matrix still in progress and no failures reported. Uneventful — approving.