docs(roadmap): July status snapshot — Mesh 2.0 cutover blocked upstream#334
Merged
Conversation
…am, hardening progress Mesh core 2.0 still isn't published (npm latest 1.9.1), so the runtime cutover can't start; readiness on our side is documented instead. Records production-hardening state (Node-22 fix on main, ProposalTally still unapplied, RLS fix in #332, gitlink fix in #333) and the systemic dependabot smoke failure as a CI watch item. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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.
Adds an early-July progress snapshot under Month 3, mirroring June's format.
Key call: the Mesh 2.0 runtime cutover is blocked upstream.
@meshsdk/core/core-cst/core-cslhave no 2.0 on npm (latest = 1.9.1, published June 1; MeshJS/mesh's latest GitHub release is 1.9.0). Only@meshsdk/react2.0.0-beta.2 exists and we already run it. Our side is cutover-ready: single-layer bridge (#278) + byte-preserving witness merge with regression tests. The snapshot spells out the delta list for the eventual cutover PR so it stays a one-hook change.Also records:
main;ProposalTallystill unapplied in prod (needs a manual workflow dispatch); RLS advisory → fix(db): enable RLS on tables added since the original RLS migration #332; stray worktree gitlink → fix(repo): remove stray .claude/worktrees gitlink, ignore worktree dirs #333.multisig-v1-smokefails on all dependabot PRs because dependabot-triggered runs get no repo Actions secrets and the job lacks the skip guard — worth fixing in the workflow so dependabot CI is meaningful again.🤖 Generated with Claude Code