You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Consolidate every currently open Dependabot pull request into one reviewable, tested dependency update on main, then close the superseded Dependabot PRs with links to the landed rollup.
Required workflow
Inventory all open Dependabot PRs, including package, lockfile, GitHub Action, Docker, and indirect dependency changes.
Record current versions, proposed versions, release notes, security advisories, breaking changes, runtime/toolchain constraints, and whether PRs overlap.
Create one dedicated rollup branch from current main.
Apply upgrades deliberately to manifests and regenerate the pnpm lockfile once. Do not merge Dependabot branches blindly or combine unrelated user work.
Resolve peer/runtime constraints using supported versions for Node 24/current LTS, Next.js 16, React 19, Drizzle, Better Auth, BullMQ, Playwright, and the rest of the declared stack.
Update code/config/migrations where a dependency requires it.
Run the complete verification suite locally and in GitHub Actions.
Review the final diff for unexpected install scripts, new transitive packages, licence changes, supply-chain risk, action pin drift, and accidental lockfile churn.
Merge the single rollup to main only after required checks pass.
Close every superseded Dependabot PR with a comment linking the rollup commit/PR; leave none silently abandoned.
Confirm the public amd64 GHCR image is rebuilt successfully from the merged commit.
Guardrails
Do not bypass branch protection, required reviews, failed checks, or security policy.
Do not use force-push on main.
Keep GitHub Actions pinned by full commit SHA.
Preserve reproducible pnpm installs and the repository package-manager version.
Do not combine feature work beyond compatibility fixes required by these upgrades.
If one upgrade is unsafe or blocked, document and exclude it from the rollup instead of weakening tests.
Security-sensitive major updates require explicit migration notes and targeted tests.
Acceptance criteria
Issue/PR contains a complete table of all Dependabot PRs and their disposition.
One clean rollup branch/PR contains the approved dependency changes.
pnpm install with frozen lockfile succeeds.
Lint, typecheck, unit, integration, Playwright, build, migration verification, dependency audit, CodeQL, SBOM, licence, and container scan checks pass.
Docker Compose clean-install smoke test passes on linux/amd64.
Public GHCR image builds and has the expected amd64 manifest.
Rollup is merged to main through normal protections.
All superseded Dependabot PRs are closed with traceable comments; intentionally deferred upgrades have a follow-up issue.
README/operations notes change only if prerequisites or commands actually changed.
Verification evidence
Attach exact test commands, CI run links, image digest, docker buildx imagetools inspect output, and the closed-PR mapping.
Dependency/order
Do this from a stable main after the current overnight implementation lands, to avoid mixing its feature diff with dependency churn.
Goal
Consolidate every currently open Dependabot pull request into one reviewable, tested dependency update on main, then close the superseded Dependabot PRs with links to the landed rollup.
Required workflow
Guardrails
Acceptance criteria
Verification evidence
Attach exact test commands, CI run links, image digest,
docker buildx imagetools inspectoutput, and the closed-PR mapping.Dependency/order
Do this from a stable main after the current overnight implementation lands, to avoid mixing its feature diff with dependency churn.