Skip to content

Release v7.5.0: Memba lives on Pearl - #1152

Draft
zxxma wants to merge 3 commits into
mainfrom
chore/release-v7.5.0
Draft

Release v7.5.0: Memba lives on Pearl#1152
zxxma wants to merge 3 commits into
mainfrom
chore/release-v7.5.0

Conversation

@zxxma

@zxxma zxxma commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

Summary

Memba lives on Pearl. v7.5.0 is the release that moves Memba's home network from Sapphire to Pearl (pearl-1): the 2026-08-31 combined ceremony deployed every Memba realm (32 artifacts), Sapphire is retired (nodes dead 09-02, formal sunset 09-09), and every backend/tooling default now says Pearl.

This PR rolls the thirteen [Unreleased] sections accumulated since v7.4.0 (2026-08-16) into one ## [v7.5.0] — 2026-09-10 block of ten sections, and bumps the app version.

Sections:

  1. Memba lives on Pearl (Pre-register Pearl as a hidden, fail-closed network so the cutover is a flag flip #1091, Pearl becomes the default network; Sapphire and Betanet stay selectable #1117, Pearl §6 completion: pins move, realms live, allowlist filled (ceremony-gated) #1119) — network
  2. Sapphire sunset (Retire sapphire to hidden for the 2026-09-09 sunset #1126, Backend RPC defaults follow the app to pearl (the live failover list named only dead sapphire hosts) #1138, Sapphire sunset: drop sapphire-1 from MEMBA_ACCEPTED_CHAIN_IDS and retire its config #1139) — network
  3. DAO pages read the daokit realm (DAO pages: parse the gnodaokit basedao render contract (memba_dao on sapphire) #1113, Memoize each DAO realm's render dialect (once-per-session discovery) #1114, New-proposal notifications reach daokit DAOs (read counts from the sub-page headers) #1115, Memberstore rosters read every pager page (back-link truncation fix) #1116)
  4. Block Party, dark and kill-switched (Block Party: pearl seed default, chain-identity verification, total kill switch #1128, Block Party: play the board the server issued #1130, Block Party: the public verification story moves to pearl #1131, Block Party v1: reliability, fairness, and accessible polish #1143) — still paused by BLOCKPARTY_ENABLED
  5. Space Invaders v1 (Space Invaders: input-contract tests, e2e happy-path, and the design-spec record #1132, Space Invaders daily certify: pause/quantization determinism, O(T+D) replay cursor, daily mode + submit wiring (M3) #1134, Certify runbook: pearl ceremony, multi-game flags #1135, Space Invaders v1: polished arcade experience, deterministic full runs, mobile guardrails #1145) — route flag on, certify flag off
  6. Security (Close the codegen path-injection class, at the generator and the choke point #1098, Raise browserslist past today's two high advisories #1137, fix(security): require patched JavaScript dependency floors #1140, fix(security): bump grpc to v1.83.1 — OOM via HTTP/2 DATA frame fragmentation #1141, fix(security): make outbound destination checks authoritative #1142, Keep CodeQL out of test fixtures and fix two escape-order nits #1146)
  7. Wallet activation's one-click button works now (Activate wallets with a MsgCall — Adena rejects bank/MsgSend from apps #1079)
  8. Pearl-true defaults and docs (Default the MCP servers and gno-rpc to Pearl instead of a dead test13 host #1147, Public docs: Pearl is home, Sapphire is retired, release state is v7.4.0 + unreleased #1148, Start fresh backends at Pearl heights and retire the legacy agent-registry alias #1149, Docs: stamp historical runbooks and ADRs as executed or superseded #1150, E2E and comment truth: the default network is Pearl #1151)
  9. Under the hood and accessibility (Make grc20 guard tests hermetic under any VITE_GNO_CHAIN_ID pin #1080, Make the runbook's alert thresholds executable #1096, Adjust LaneToolbar's search sync during render, and ratchet to 54 #1097, Give the money-path modal real dialog semantics and a mobile layout #1100react-query wave 3: ChannelsPage and ProfilePage #1106, react-query wave 4: eight more pages off fetch-in-effect #1108set-state-in-effect endgame: every warning resolved, ratchet locked at ZERO #1112, fourteen Dependabot bumps)
  10. Temporarily dark, on purpose — Block Party, Space Invaders certify, arcade multi-game realm (undeployed, Arcade certify: multi-game backend fan-out (BARRICADE + Space Invaders), dark by default #1133), commerce/marketplace + NFT indexer, Marketplace v2 flag, reactions; mainnet not authorized

A fresh [Unreleased] block carries a single ### Coming next section (commerce lanes after the two-wallet live-money check, NFT indexer after observability wiring, Block Party / Space Invaders certify after their owner ceremonies).

Consolidation notes:

  • Bullets superseded by later facts were dropped: "earlier sapphire posts stay readable by switching networks until its September 9 sunset", "Sapphire stays fully available from the network selector", "features arrive with their deployment ceremony and show a not-deployed-yet notice", and "connecting a wallet on Pearl or Betanet shows a not-accepted-yet message" (both chains are on the accepted list).
  • Close the codegen path-injection class, at the generator and the choke point #1098 had no changelog entry; one line was written from the merged PR description.
  • Every release block from v7.4.0 down is byte-identical to main.

Version bump: frontend/package.json and frontend/package-lock.json 7.4.0 → 7.5.0 (npm version 7.5.0 --no-git-tag-version).

Test plan

  • node ./node_modules/.bin/vitest run src/lib/changelog.test.ts — 14 passed (parser runs against the real file; exactly one unreleased entry; ≤ 16 sections per block)
  • node ./node_modules/.bin/vitest run src/lib/config.test.ts — 96 passed (APP_VERSION equals package.json)
  • node ./node_modules/.bin/vitest run src/pages/Changelogs.test.tsx — 4 passed
  • npm run build — exit 0
  • npm run lint (--max-warnings=0) — exit 0
  • git diff --check — clean
  • diff of every block from ## [v7.4.0] onward against origin/main — identical
  • Grepped the v7.5.0 block: every "Sapphire" mention is in the retired/sunset sense; no dark feature is described as live or enabled

Important

Merging deploys the frontend through Netlify's native build (the package.json bump guarantees a rebuild). backend/ is untouched, so the backend auto-deploy does not fire. The v7.5.0 GitHub tag and release are a separate, owner-confirmed step and are not created by this PR.

@netlify

netlify Bot commented Sep 7, 2026

Copy link
Copy Markdown

Deploy Preview for memba-multisig ready!

Name Link
🔨 Latest commit 968e905
🔍 Latest deploy log https://app.netlify.com/projects/memba-multisig/deploys/6a9e8c396583a60008e06dfd
😎 Deploy Preview https://deploy-preview-1152--memba-multisig.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 69 (🔴 down 5 from production)
Accessibility: 97 (no change from production)
Best Practices: 83 (no change from production)
SEO: 90 (no change from production)
PWA: 100 (no change from production)
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@github-actions

github-actions Bot commented Sep 7, 2026

Copy link
Copy Markdown

The latest Buf updates on your PR. Results from workflow CI / proto (pull_request).

BuildFormatLintBreakingUpdated (UTC)
✅ passed✅ passed✅ passed✅ passedSep 7, 2026, 10:04 AM

@zxxma
zxxma force-pushed the chore/release-v7.5.0 branch from 2c5c903 to 968e905 Compare September 7, 2026 10:04
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