Skip to content

Release: deploy-migrations Node 22 fix (unblocks prod migrations) + roadmap refresh#321

Merged
QSchlegel merged 5 commits into
mainfrom
preprod
Jun 18, 2026
Merged

Release: deploy-migrations Node 22 fix (unblocks prod migrations) + roadmap refresh#321
QSchlegel merged 5 commits into
mainfrom
preprod

Conversation

@QSchlegel

Copy link
Copy Markdown
Collaborator

Promotes the post-#303 work on preprod to main (2 changes).

CI fix — unblocks production migrations

Docs

  • Roadmap June/July refresh (#320): real per-owner June tasks + a dated progress snapshot, fleshed-out July deliverables, and Andre's in-progress email notification service.

⚠️ Deploy checklist for main

  • This merge changes .github/workflows/ and ROADMAP.md only — it does not touch prisma/migrations/**, so merging will not auto-trigger the deploy-migrations workflow.
  • After merge: manually run the Deploy Database Migrations workflow on main (now possible via workflow_dispatch) to apply the still-pending 20260614120000_add_proposal_tally migration. The ProposalTally table is currently missing in prod and the governance tally router errors until it exists.
  • Separately tracked: the Supabase advisory flagging RLS disabled on 7 tables — unrelated to this PR.

🤖 Generated with Claude Code

QSchlegel and others added 5 commits June 17, 2026 14:34
The deploy-migrations workflow pinned Node 18, but the repo now depends on
prisma@7.8.0, which refuses to install on Node <20.19 (preinstall engine
gate). npm ci failed before `prisma migrate deploy` ever ran, so the
20260614120000_add_proposal_tally migration never reached production.

- Bump setup-node to 22, matching pr-checks/unit-tests/trpc/ci-smoke.
- Add workflow_dispatch so a pending migration can be applied without
  pushing a fresh file under prisma/migrations/** (this workflow only
  triggers on that path otherwise).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
ci(migrations): run deploy-migrations on Node 22 + allow manual dispatch
…snapshot

Months 2 (June) and 3 (July) each had a single one-line task per owner, and
June's "Mesh 2.0 + CI" framing no longer matches what actually shipped.

- June (M2): expand into the five workstreams actually delivered (Mesh 2.0
  groundwork, signing/auth reliability, in-app governance voting, IPFS +
  rationale, platform UX) plus CI; add a dated mid-month Progress table that
  cites the merged PRs as evidence (mirrors M1's "Proof of completion"). Mesh
  2.0 is honestly marked In progress — runtime is still on @meshsdk/core@^1.9.
- July (M3): break FROST kickoff and Wallet V2 into concrete deliverables; add
  the Mesh 2.0 runtime cutover (carryover) and a production-hardening item
  (Node-22 migration CI on main, apply ProposalTally, RLS review).
- Sync the per-owner aggregated list; flag #122 as closed ahead of schedule.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Add the email notification service (feature/email-notification-center) to
Andre's June lane — Resend email channel, notification center + outbox/worker,
per-wallet settings, and email verification — marked In progress since the
branch isn't merged to preprod yet. Mirror it into the Progress table and the
per-owner aggregated list.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@vercel

vercel Bot commented Jun 18, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
multisig Ready Ready Preview, Comment Jun 18, 2026 12:58pm

Request Review

@QSchlegel QSchlegel merged commit 9b5feec into main Jun 18, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant