Skip to content

release: v10.0.0-rc.8#531

Merged
branarakic merged 1 commit into
mainfrom
release/v10.0.0-rc.8
May 15, 2026
Merged

release: v10.0.0-rc.8#531
branarakic merged 1 commit into
mainfrom
release/v10.0.0-rc.8

Conversation

@branarakic
Copy link
Copy Markdown
Contributor

Summary

Lockstep version bump 10.0.0-rc.710.0.0-rc.8 across all 19 workspace package.json files (root + demo + 17 packages) plus the CHANGELOG.md entry summarising the rc.8 contents.

This PR contains no functional code changes — every feature in rc.8 has already merged to main via its own reviewed PR. This is the release-gating commit so a signed v10.0.0-rc.8 tag has matching package.json versions to publish from.

Contents (mirrors CHANGELOG)

libp2p reachability hardening series

CI / release flow

Agent + chat surface

On-chain (already on main)

Other fixes

Release procedure (post-merge)

git checkout main
git pull
git tag -s v10.0.0-rc.8 -m "Release v10.0.0-rc.8"
git push origin v10.0.0-rc.8

Then a reviewer in the npm-publish Environment approves the publish (5-minute wait timer, no self-approval) per the new tag-triggered flow from #522.

Test plan

  • All 19 package.json files bumped in lockstep
  • No 10.0.0-rc.7 references remain in any package.json
  • chainResetMarker intentionally untouched (already moved by chore(deployments): refresh base_sepolia_v10 — redeploy 7 changed contracts #511)
  • CI tests pass on this PR
  • After merge: git tag -s v10.0.0-rc.8 matches package.json versions, points to a main commit
  • After merge: signed-tag push triggers npm-publish workflow successfully
  • After merge: reviewer approval in npm-publish Environment completes the publish

Made with Cursor

Lockstep bumps every workspace package from 10.0.0-rc.7 → 10.0.0-rc.8 so
a `pnpm install dkg-v10@10.0.0-rc.8` resolves to a coherent set.

`network/testnet.json#chainResetMarker` is intentionally NOT bumped here —
it was already moved to `v10-profilestorage-paramstore-redeploy-2026-05-14`
by #511 (Base Sepolia 7-contract redeploy off main@7235e669) and rc.8
ships against that on-chain world.

CHANGELOG entry summarises rc.8 contents:
  - libp2p reachability hardening series:
    * #524 — Core Node relay capacity scaling + 2 h reservation TTL +
      operator `relayServerCapacity` knob.
    * #525 — relay observability via `RelayMetricsAdapter` (HOP/STOP
      stream tracking), `/api/relay/stats`, `relay_*` snapshot
      persistence, and `relay-internal-shapes.ts` compatibility helpers
      that fail visibly instead of silently going stale.
    * #526 — edge multi-reservation tuning: `relayReservationCount`
      (default 3), watchdog enforces per-relay reservation presence
      with a per-tick forced-redial budget capped at missing-slot
      count, canonical `usableRelayCandidates` pass that dedupes by
      peerId / aggregates alternate transports / drops self-references,
      and AutoNAT + `/p2p-circuit` fallback gating off usable count.
    * #530 — `validateRelayServerCapacity` now uses
      `Number.isSafeInteger` and a `MAX_RELAY_SERVER_CAPACITY` ceiling
      so derived caps never overflow.
  - #522 — npm publish switched from continuous (on every merge to main)
    to tag-triggered (signed `v<x>.<y>.<z>` tag on a release branch,
    reviewer-gated `npm-publish` Environment).
  - #510 + #521 — agent-to-agent debug chat: MCP tools, ACL, `MessageOutbox`
    invitee-side retry with per-key inflight guard, `ProtocolRouter.send`
    re-runs `peerResolver` per attempt.
  - #503/#504/#505/#516/#528/#529 — Node UI chat panel revamp end-to-end
    (layout, composer, markdown + syntax highlighting, polish, picker,
    document viewer).
  - #491 — staking-V10 `_convertToNFT` now actually transfers migrated
    TRAC from `StakingStorage` to `ConvictionStakingStorage`.
  - #493 — staking-V10 operator-fee lookup binds to the requesting
    epoch's timestamp, not latest.
  - #517 — close post-approval sync gap that hid freshly-joined curated
    CGs from the invitee until next periodic sync.
  - #508 — `JoinProjectModal` surfaces curator reject reason instead of
    swallowing it.
  - #523 — axiom-4 trust upgrades: hardened endpoint inputs, bounded
    verify-collection timeout, fail-closed on non-quorum verify.
  - #515 — `npm-publish` job uploads the `.publish-artifacts` dir
    correctly (renamed off the leading-dot path).
  - #511 — Base Sepolia: 7 contracts redeployed off main@7235e669
    (Profile / ProfileStorage / ParameterStorage family + staking-V10
    fixes), `chainResetMarker` bumped accordingly.

Co-authored-by: Cursor <cursoragent@cursor.com>
Copy link
Copy Markdown

@github-actions github-actions Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Codex review completed — no issues found.

@branarakic branarakic merged commit 2729848 into main May 15, 2026
41 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