chore(cms,web): update payload dependencies to 3.82.0

[jhb-dev]

Summary

This pull request upgrades all Payload CMS related dependencies to version 3.82.0, ensuring consistency across the project's CMS infrastructure.

Changes

• Updated @payloadcms/db-mongodb from 3.81.0 to 3.82.0
• Updated @payloadcms/email-resend from 3.81.0 to 3.82.0
• Updated @payloadcms/next from 3.81.0 to 3.82.0
• Updated @payloadcms/plugin-cloud-storage from 3.81.0 to 3.82.0
• Updated @payloadcms/plugin-mcp from 3.81.0 to 3.82.0
• Updated @payloadcms/plugin-search from 3.81.0 to 3.82.0
• Updated @payloadcms/plugin-seo from 3.81.0 to 3.82.0
• Updated @payloadcms/richtext-lexical from 3.81.0 to 3.82.0
• Updated @payloadcms/storage-s3 from 3.81.0 to 3.82.0
• Updated @payloadcms/translations from 3.81.0 to 3.82.0
• Updated @payloadcms/ui from 3.81.0 to 3.82.0
• Updated payload from 3.81.0 to 3.82.0

Notes

All Payload CMS packages have been updated to the same minor version (3.82.0) to maintain compatibility and consistency across the CMS ecosystem.

https://claude.ai/code/session_01PndWwDekDFJ1Jj9PAfekAo

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
website	Ignored		Apr 9, 2026 8:32am
website-cms	Ignored		Apr 9, 2026 8:32am

[claude]

PR Review: Payload CMS 3.81.0 → 3.82.0 upgrade

Overall this is a clean, well-structured dependency bump. All direct Payload packages are updated consistently. A few observations:

Potential Issues

• @payloadcms/live-preview stays at 3.81.0 — This transitive dependency was not upgraded alongside the rest. It appears in pnpm-lock.yaml still at 3.81.0 (line ~169 in the diff). While pnpm may resolve this correctly given peer dep ranges, it's worth verifying this doesn't cause a version mismatch at runtime, especially if any plugin uses live-preview internals that changed between 3.81 and 3.82.

Notable Change Worth Reviewing

• @payloadcms/next peer dep range narrowed — The accepted next range changed from >=16.2.0-canary.10 <17.0.0 to >=16.2.2 <17.0.0. The project pins next@16.2.2 exactly, which satisfies the new range — no action needed, but worth being aware of if Next.js is ever downgraded.

Performance & Security

• No source code changes; all changes are in package.json and pnpm-lock.yaml.
• Minor version bumps within the Payload ecosystem typically contain bugfixes, not breaking changes or security regressions.
• No security concerns for this scope of change.

Suggestion

Consider verifying @payloadcms/live-preview compatibility with payload@3.82.0 before merging, or upgrading it to 3.82.0 if a release is available.

[claude]

PR Review: Payload CMS 3.81.0 → 3.82.0

Summary

This is a clean, straightforward dependency upgrade. All 12 Payload CMS packages are updated atomically to 3.82.0, and the lockfile is correctly regenerated to match.

Potential Bugs / Issues

• None found. All @payloadcms/* packages are updated consistently to the same version, which is the correct approach since Payload's monorepo packages must stay in sync. Third-party plugins (@jhb.software/*) are also correctly re-resolved against the new peer dependency in the lockfile.
• Worth a quick check of the Payload 3.82.0 changelog to confirm there are no breaking changes or migration steps required before merging.

Performance Considerations

• No application code was changed, so no runtime performance impact. Any performance changes would be internal to Payload itself.

Security Concerns

• No security concerns. This is a minor version bump; no new dependencies were introduced and none were removed or downgraded.

Verdict

LGTM. The upgrade is mechanically correct and consistent. Recommend verifying the 3.82.0 release notes and doing a smoke test of the CMS admin panel after merging.

[github-actions]

Preview Deployment

Project	URL
CMS	https://website-kf1ytgs79-jhb-software.vercel.app
Web	https://website-p9vtywegy-jhb-software.vercel.app

The Web preview uses the CMS preview URL for content fetching.