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 @@ -58,7 +58,7 @@
"@tiptap/extension-subscript": "3.23.5",
"@tiptap/extension-superscript": "3.23.5",
"@tiptap/extension-text-align": "3.23.5",
"@tiptap/extension-text-style": "3.23.5",
"@tiptap/extension-text-style": "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 [high] The client SBOM wasn't regenerated for this bump, so run-tests / build fails on the stale-hash gate — client/sbom/.lock-hash still hashes the old pnpm-lock.yaml/package.json. A maintainer needs to run pnpm run sbom:force in client/ and commit the updated sbom/bom.json + sbom/.lock-hash (Dependabot won't do this on its own). The separate refresh workflow failure is the known-broken auto-SBOM job, so ignore that one.

🤖 Prompt for AI agents

In the client/ directory, the committed SBOM is stale after bumping @tiptap/extension-text-style to 3.23.6: client/sbom/.lock-hash no longer equals sha256(pnpm-lock.yaml + package.json), which fails the "Verify client SBOM is up-to-date" step in .github/workflows/run_tests.yml. Run pnpm install then pnpm run sbom:force in client/, and commit the regenerated client/sbom/bom.json and client/sbom/.lock-hash.

"@tiptap/extension-underline": "3.23.5",
"@tiptap/react": "3.23.5",
"@tiptap/starter-kit": "3.23.5",
Expand Down
12 changes: 6 additions & 6 deletions client/pnpm-lock.yaml

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

Loading