Repository navigation
fix: clear the open security alerts and update dependencies - #288
Merged
Merged
Conversation
@nuxt/content still requires zod 3, which has no patched release, so the docs force zod 4. minimatch moves to 11.0.5 and glob to 14.0.4. The rest of the docs lockfile is updated within its ranges.
The pin check now exempts $/ references, which GitHub treats as pinned.
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.
This clears every open security alert on custom-fields except one, and brings each dependency to its latest compatible version, before v3.16.3 is tagged. Dependabot reports four npm alerts in the docs site (high: zod; medium: minimatch, glob; low: deepmerge). Code scanning reports one zizmor finding in
release.yml. This PR fixes all of them except deepmerge, which has no patched release. There are no repository advisories and no secret-scanning alerts.None of the npm alerts reach the package itself. They sit in
docs/, the Nuxt site that builds the documentation, which Composer users never install.What changed
docs/package.jsonoverrides (Dependabot feat: version the entity registry cache key #295, #335, #337):zodresolves to the site's own^4.6.7($zod).@nuxt/content3.16.2, its latest release, still requires zod 3, and zod 3 has no patched release, so forcing zod 4 is the only fix.minimatchresolves to^11.0.5(all copies were 10.2.6, affected range 7.0.0 to 11.0.0).globresolves to^14.0.4(copy 13.0.7, affected range 9.0.0 to 14.0.1).docs/package-lock.jsonandpackage-lock.json: updated within their ranges. Notable moves: nuxt 4.6.4, @nuxt/image 2.2.1, tailwindcss and @tailwindcss/postcss 4.3.4.resources/dist/custom-fields.css: rebuilt. The committed file dated from 2026-10-05, and 16 commits have touchedsrc/andresources/viewssince. Rebuilding with the old lockfile also gives about 824 KB against 798 KB committed. So the growth comes from source and Filament theme changes, and tailwind 4.3.4 adds only 172 bytes.release.yml(code scanning Add infolists components and factories for custom fields #11): callstests.ymlthrough GitHub's self-repository syntaxuses: $/.github/workflows/tests.yml. That form can't load a workflow cloned at runtime, and GitHub treats it as pinned.tests.yml: the "Actions pinned to SHA" check now exempts$/references as well as./ones. Without this, the check fails onrelease.yml.zizmor.yml:zizmorcore/zizmor-actionv0.8.0 to v0.8.1. Every other pinned action was already at its latest release.Why this way
npm audit fixonly offers semver-major downgrades of docus, nuxt and @nuxt/ui, so overrides on the vulnerable leaves are the smallest fix that keeps the site on current versions.Behavior to know about
composer.json. A freshcomposer updateinstalls Filament 5.11.1 and Laravel 13.40.0, every direct dependency is at its latest, Rector's pin (2.8.4) is its latest release, andcomposer auditfinds nothing.@rollup/plugin-node-resolveinside nitropack, which merges its own options, not user input. The nine low findings left innpm auditfordocs/are all this one package and the packages that depend on it.Checked
On
9c9226f8:vendor/bin/pest --parallelpasses 1123 (3 todo), PHPStan reports no errors, Rector and Pint pass.npm cisucceeds in the root and indocs/. Rootnpm auditfinds 0 vulnerabilities. Docsnpm auditfinds 9 low, all deepmerge, down from 22 (5 high).npm run buildbuilds the stylesheet and script.NUXT_SITE_URL,NUXT_APP_BASE_URL=/custom-fields/):npm run generateprerenders 74 routes. A spot check ofessentials/builder-scoping.htmlshows its markdown rendered, so@nuxt/contentworks on zod 4.$/syntax: proven on a throwaway branch that calledtests.ymlwithuses: $/.... Its matrix jobs started, and its pin check failed on the$/line, which is whytests.ymlchanged. I cancelled the run and deleted the branch.Not checked
release.ymlitself runs only on a tag push, so the first exercise of the changed line is the v3.16.3 tag. The throwaway run proved the same call shape.4.xbranch is not covered here. Dependabot reports against3.x, the default branch.