Repository navigation
chore: update dependencies - #291
Merged
Merged
Conversation
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.
Brings every custom-fields dependency to its latest compatible version before the next 3.x tag, and confirms nothing is left to fix on the security side. GitHub reports one open alert: Dependabot #324, low,
deepmergein the docs site. It has no patched release, so it stays open. There are no code-scanning or secret-scanning alerts.What changed
package-lock.json: updated within its ranges. Tailwind and its toolchain move 4.3.4 to 4.3.5.docs/package-lock.json: updated within its ranges, 54 packages, all patch or minor (for example rollup 4.68.0 and the@ai-sdk/*packages). nuxt 4.6.4, docus 5.15.0, @nuxt/ui 4.12.0 and the zod override (4.6.7) are unchanged.resources/dist/custom-fields.css: rebuilt with tailwind 4.3.5. It is 18 bytes smaller.Behavior to know about
composer.json. A freshcomposer updateleaves no direct dependency outdated, andcomposer auditfinds no advisories.Checked
On
849f27e5:npm auditreports 0 vulnerabilities at the root, and only the 9 low deepmerge findings (the alert and its parents) indocs/.npm ciandnpm run buildsucceed from the new lockfile.Not checked
The PHP suite and the docs build run in CI. No PHP or view changed.