Release v7.5.0: Memba lives on Pearl - #1152
Draft
zxxma wants to merge 3 commits into
Draft
Conversation
✅ Deploy Preview for memba-multisig ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
The latest Buf updates on your PR. Results from workflow CI / proto (pull_request).
|
zxxma
force-pushed
the
chore/release-v7.5.0
branch
from
September 7, 2026 10:04
2c5c903 to
968e905
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

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-10block of ten sections, and bumps the app version.Sections:
BLOCKPARTY_ENABLEDA fresh
[Unreleased]block carries a single### Coming nextsection (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:
main.Version bump:
frontend/package.jsonandfrontend/package-lock.json7.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_VERSIONequalspackage.json)node ./node_modules/.bin/vitest run src/pages/Changelogs.test.tsx— 4 passednpm run build— exit 0npm run lint(--max-warnings=0) — exit 0git diff --check— cleandiffof every block from## [v7.4.0]onward againstorigin/main— identicalImportant
Merging deploys the frontend through Netlify's native build (the
package.jsonbump guarantees a rebuild).backend/is untouched, so the backend auto-deploy does not fire. Thev7.5.0GitHub tag and release are a separate, owner-confirmed step and are not created by this PR.