chore: sync main into testnet-canary after 10.0.11 - #2001
Merged
Conversation
release: promote testnet-canary to main for 10.0.11
Move the root package and all 20 packages/* workspaces to 10.0.11 in lockstep, per the single-version release set rule in RELEASE_PROCESS.md §3, and add the 10.0.11 CHANGELOG entry. Version-only bump: pnpm-lock.yaml records third-party versions only and is untouched, so `pnpm install --frozen-lockfile` stays valid. `pnpm release:verify-versions --version 10.0.11` passes (21/21). The engines.node ranges added in 10.0.10 on packages/cli and packages/agent are preserved unchanged. CHANGELOG carries an `### Upgrading from 10.0.10` matrix, required by §10 because this release changes the default admission behaviour and error contract of a public HTTP API. Verified in the shipped code: - POST /api/query now defaults to the background store lane (api-query-priority.ts:8,12), reversible via DKG_API_QUERY_PRIORITY (lifecycle.ts:1175, README.md:60). - Under stock tuning that lowers API-read concurrency from 2 to 1: MAX_CONCURRENT=4 less ACK=1 and HEALTH=1 gives totalLimit=2, normalFloor=1, backgroundLimit=max(1, 2-1)=1 (store-priority-scheduler.ts:97-100,177-181). - A shed query now answers 503 + Retry-After: 1 where it previously fell through to a generic 500. No Solidity source, ABI, or deployment-registry changes since v10.0.10, so this release requires no contract deployment. Dashboard SQLite stays at SCHEMA_VERSION 31 — no migration, no rollback question. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
chore(release): bump version set to 10.0.11
otReviewAgent
left a comment
otReviewAgent
left a comment
There was a problem hiding this comment.
Review Agent completed this review and found no issues.
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
2 participants
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.11 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, +59 / −21.What canary is missing
5b149f6d1testnet-canary→mainpromotion (the merge commit itself; its content originated on canary)47be53243chore(release): bump version set to 10.0.112ca1f46ddThe 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.10; this brings it to10.0.11along with the## [10.0.11]CHANGELOG section and its### Upgrading from 10.0.10matrix.Nothing stranded this release
Unlike the 10.0.10 cycle — where two fixes were pushed to the frozen
release/10.0.10branch and had to be recovered by the sync — every code change in 10.0.11 landed ontestnet-canaryfirst (#1991, #1994, #1988).git rev-list --count origin/main..origin/release/10.0.11is 0, so the release branch holds nothing that is not already onmain.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.11 tolatestandmainnet.Note on CI
ci.ymlnow includestestnet-canaryin both thepushandpull_requestbranch filters (#1992), so unlike the 10.0.10 cycle this PR does trigger the full lane.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