chore: sync main into testnet-canary after 10.0.12 - #2074
Merged
Conversation
release: promote testnet-canary to main for 10.0.12
Move the root package and all 20 packages/* workspaces to 10.0.12 in lockstep, per RELEASE_PROCESS.md §3, and convert the [Unreleased] section into the 10.0.12 CHANGELOG entry. Version-only bump: pnpm-lock.yaml is untouched, so `pnpm install --frozen-lockfile` stays valid. `pnpm release:verify-versions --version 10.0.12` passes (21/21). The engines.node ranges added in 10.0.10 are preserved unchanged. CHANGELOG: the prior [Unreleased] body documented only #2006, in a single 2.8k-character bullet, under a non-house-style `### Operator knobs` heading. It is replaced by a full section covering all nine PRs (#2067, #2053, #2059, #2051, #2033, #2007, #2010, #2003, #2002) with the #2006 headline cut to house length. Carries an `### Upgrading from 10.0.11` matrix, required by §10. The release removes a public export from a published package — verified: CATCHUP_BACKPRESSURE_RETRY_DELAYS_MS is exported from packages/agent/src/index.ts at v10.0.11 and absent at f9922f2, and `retryDelaysMs` is now typed `never` (sync/catchup-policy.ts:145) and rejected at runtime (:245). Also covered: a new 503 on subscribe, DKGAgent.stop() now rejecting on a drain timeout, the sync-global `operation` dimension becoming `<work class>:<source>`, and the write-preflight tightening. Known issues records a defect that ships knowingly: on sync-global, per-lane `state` cannot reflect a full global queue because priority-admission-queue.ts:177-180 calls updatePressureCapacity without a `lanes` map, while backpressure-observability.ts:361-362 reads lane limits only from capacity.lanes. The scheduler rollup that /api/status publishes is correct; the store scheduler is unaffected. No Solidity source, ABI, or deployment-registry changes since v10.0.11, so no contract deployment. Dashboard SQLite stays at SCHEMA_VERSION 31. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
chore(release): bump version set to 10.0.12
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.
Summary
Re-equalizes
testnet-canarywithmainafter the 10.0.12 release. Fast-forward only —testnet-canaryis fully contained inmain(0 commits ahead, merge-base == canary tip), so there is nothing to resolve.mainis 3 commits ahead: 22 files, +63 / −33.What canary is missing
f9922f262testnet-canary→mainpromotion (the merge commit itself; its content originated on canary)8346598b7chore(release): bump version set to 10.0.12843f5213dThe effective diff is only the version bump and the CHANGELOG entry — verified: filtering the changed-file list for anything that is not a
package.jsonorCHANGELOG.mdreturns nothing.Canary currently declares
10.0.11; this brings it to10.0.12along with the## [10.0.12]CHANGELOG section and its### Upgrading from 10.0.11matrix.Nothing stranded
Every code change in 10.0.12 landed on
testnet-canaryfirst, and #2072 was opened directly from canary rather than a frozen release branch, so there was no branch to strand work on this cycle.Risk
Low. Version-only plus documentation.
pnpm-lock.yamlis untouched, sopnpm install --frozen-lockfilestays valid. Every commit here is already onmainand shipped as 10.0.12 tolatest,mainnetandtestnet.Merge
Prefer a merge commit over squash, so canary keeps the same per-PR history
mainhas — the CHANGELOG convention depends on recovering PR numbers from the merge history.🤖 Generated with Claude Code