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 @@ -62,7 +62,7 @@
"@tiptap/extension-underline": "3.23.5",
"@tiptap/react": "3.23.5",
"@tiptap/starter-kit": "3.23.5",
"dayjs": "1.11.20",
"dayjs": "1.11.21",

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.

@app/renovate [medium] This bump needs the generated client SBOM files too. Right now client/sbom/bom.json still lists dayjs@1.11.20, client/sbom/.lock-hash does not match the new package/lock hash, and CI is already failing at install because dayjs@1.11.21 has not cleared pnpm's minimumReleaseAge policy yet. Once the release-age gate passes, regenerate the SBOM and commit client/sbom/bom.json plus client/sbom/.lock-hash with this bump.\n\n

🤖 Prompt for AI agents\n\nIn client/package.json, dayjs was bumped to 1.11.21 but the committed client SBOM still references dayjs@1.11.20 and the lock hash is stale. After dayjs@1.11.21 clears the pnpm minimumReleaseAge policy, run the client SBOM generation (pnpm sbom:force from client) and commit client/sbom/bom.json and client/sbom/.lock-hash. Do not change CI or the pnpm policy.\n\n

"dompurify": "3.4.5",
"embla-carousel": "8.6.0",
"embla-carousel-react": "8.6.0",
Expand Down
16 changes: 8 additions & 8 deletions client/pnpm-lock.yaml

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

Loading