Repository navigation
docs(fork): the 1.11.3 to 1.11.4 upgrade entry, ledger rows without a queue link - #452
Merged
Merged
Conversation
… queue link The atunnel relay change that cuts 1.11.4 needs no migration and no reset; docs/upgrade.md now says so for the patch step. Four ledger files linked a tracking issue outside this repository; their Upstream rows keep the branch and commit and drop the link. Signed-off-by: Timo Derstappen <teemow@gmail.com>
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.
Problem
v1.11.4-rc.1 carries #451 (atunnel ends a CONNECT tunnel when the actor closes its connection, #450), which declared
no-upgrade-entry, sodocs/upgrade.mdhas no "1.11.3 to 1.11.4" entry for the patch it cuts. Four ledger files infork/link a tracking issue outside this repository.Change
docs/upgrade.md: the "1.11.3 to 1.11.4" entry: persisted format and chart unchanged (the diff from v1.11.3 touches onlyinternal/atunnel, test files andfork/), the relay runs in the worker's ateom, no migration, goldens kept, no reset, no conversation lost.fork/ateapi-crashed-actor-refusal-not-resumable.md,fork/ateom-reports-sandbox-exit-of-running-actor.md,fork/glutton-cpu-burn-test-bounded-by-scheduler-share.md,fork/keychain-test-plugins-written-under-fork-lock.md: the Upstream row keeps the upstream-ready branch and commit and drops the external queue link.Documentation only; nothing that ships changes. The step 1.11.3 → 1.11.4-rc.1 is proven on an agentlab with
agentlab substrate-step-test(conversation resumed, goldens kept, under a worker drain).