chore: v0.58.0 - #274
Merged
Merged
chore: v0.58.0#274
Conversation
Release for #251, #252, #263, #265, #268 and #272, with the pre-release fixes in #273. - Bump the workspace version to 0.58.0 - release-notes/0.58.0.md The control-plane protocol (34) and the request store schema (25) are already at their release values on main and do not change here. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.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
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.
Release for #251, #252, #263, #265, #268 and #272, with the pre-release fixes in #273.
Cargo.toml, and the 19 workspace crates inCargo.lock).release-notes/0.58.0.md: an opening paragraph, the upgrade notes, and one section per feature.CONTROL_API_VERSION(34) and the request storeSCHEMA(25) are already at their release values onmain. This PR does not change them.Upgrade notes in brief
Protocol 31 → 34. Lite 2026.10.0 (core 0.57.1, protocol 31) does not connect to 0.58.0.
sudo twcore upgrade --version 0.57.1 --restartswitches a server back.Schema 23 → 25: the request history is cleared on first start.
security.hidden_textandsecurity.output_limitare removed, and a config that still has either does not load. Only changed settings are written, so the affected users are those who set:The fix is to reset those settings, or to delete the two keys under
security:.Checked against v0.57.1:
securitysection (init.rs);max_chars, and removing the last key also removes the emptied parent sections;security: {hidden_text: …}fails withunknown field hidden_text, and an emptysecurity:loads.Protocol and message-code changes are listed against v0.57.1. The code lists come from diffing
msg-codes.txtbetween the tag andmain: 67 added (two of them test-only), 14 removed, 3 of those pairs renames.Building from source needs a WebAssembly-capable clang.
Behavior notes:
The release notes contain no CJK characters, which
scripts/release_notes_test.pyenforces, so the settings are named by their English labels in Lite.Checks
python3 scripts/release_notes_test.pycargo fmt --all -- --checkcargo clippy --workspace --all-targets -- -D warningsenv -u HTTP_PROXY -u HTTPS_PROXY cargo test --workspace: 2601 passed, 0 failed, 7 ignoredAll runs used
RUSTFLAGS="-D warnings".Cargo.tomlchanges, so theenterprisejob runs against ThinkWatchdev. It is expected to be red until ThinkWatch#72 lands after the tag, as onmainsince #268.🤖 Generated with Claude Code