Skip to content

build(deps): bump the payload group across 1 directory with 5 updates #129

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mergify merged 3 commits into from
May 18, 2026
Merged

build(deps): bump the payload group across 1 directory with 5 updates #129

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ae0611a
build(deps): bump the payload group across 1 directory with 5 updates
dependabot[bot] May 18, 2026
767383d
fix(deps): regenerate lockfile for patchedDependencies hash
julianken May 18, 2026
367d6e7
Merge remote-tracking branch 'origin/main' into td-129-fix2
julianken May 18, 2026
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
10 changes: 5 additions & 5 deletions package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,10 +28,10 @@
"typecheck": "tsc --noEmit"
},
"dependencies": {
"@payloadcms/db-postgres": "^3.83.0",
"@payloadcms/next": "^3.83.0",
"@payloadcms/richtext-lexical": "^3.83.0",
"@payloadcms/storage-s3": "^3.83.0",
"@payloadcms/db-postgres": "^3.84.1",
Copy link
Copy Markdown
Collaborator

@julianken-bot julianken-bot May 18, 2026

Choose a reason for hiding this comment

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

SUGGESTION — root-cause documentation, not a blocker for this PR.

The fix commit (767383d, "fix(deps): regenerate lockfile for patchedDependencies hash") is correct and minimal, but the why lives only in the commit message and out-of-band context. Future Dependabot PRs that touch a patched dependency will hit the same hash-format mismatch — when Dependabot's older pnpm regenerates the lockfile with the hex SHA-256 form, it diverges from the base32 hash main was committed with under pnpm 9.15.x.

Three options, pick the cheapest that actually persists the runbook:

  1. Add a section to docs/deployment.md (or CLAUDE.md under "Common Tasks") titled something like "Dependabot lockfile hash mismatch (patchedDependencies)" with the one-line fix: re-run pnpm install locally on the Dependabot branch with the project's pinned pnpm version, then push.
  2. Configure .github/dependabot.yml to pin Dependabot's pnpm version to match the project's (if Dependabot supports that — last I checked it doesn't, but worth a 5-minute confirmation).
  3. Add a CI early-fail step that surfaces the hash-format mismatch with a clear message pointing at the runbook, so future hits aren't a 20-minute "why is install failing" investigation.

Doing nothing is also defensible — the next time it happens, fixing it again is 3 minutes — but the cost of documenting now is also 3 minutes.

"@payloadcms/next": "^3.84.1",
"@payloadcms/richtext-lexical": "^3.84.1",
"@payloadcms/storage-s3": "^3.84.1",
"@upstash/ratelimit": "^2.0.8",
"@upstash/redis": "^1.38.0",
"graphql": "^16.14.0",
Expand All @@ -41,7 +41,7 @@
"next-themes": "^0.4.6",
"next-view-transitions": "^0.3.5",
"panzoom": "^9.4.4",
"payload": "^3.83.0",
"payload": "^3.84.1",
"react": "19.2.5",
"react-dom": "19.2.5",
"sharp": "^0.34.5"
Expand Down
Loading
Loading