Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion client/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@
"@tiptap/extension-superscript": "3.23.5",
"@tiptap/extension-text-align": "3.23.5",
"@tiptap/extension-text-style": "3.23.5",
"@tiptap/extension-underline": "3.23.5",
"@tiptap/extension-underline": "3.23.6",

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dependabot [medium] Bumping the lockfile here makes client/sbom/.lock-hash stale, which is why run-tests / build fails with client/sbom/ is stale (pnpm-lock.yaml or package.json changed). The SBOM hash is derived from pnpm-lock.yaml + package.json, and this PR changed both without regenerating it (computed 93df8d48… vs stored bf47dc04…). Dependabot won't fix this on its own — someone needs to run pnpm run sbom:force in client/ and commit the updated sbom/.

🤖 Prompt for AI agents

The client SBOM is stale after this dependency bump, causing the run-tests / build CI check to fail. In the client/ directory, run pnpm run sbom:force to regenerate client/sbom/bom.json and client/sbom/.lock-hash, then commit the updated files in client/sbom/.

"@tiptap/react": "3.23.5",
"@tiptap/starter-kit": "3.23.5",
"dayjs": "1.11.20",
Expand Down
14 changes: 7 additions & 7 deletions client/pnpm-lock.yaml

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading