Repository navigation
Prepare 0.6.0rc1 - #666
Merged
Merged
Prepare 0.6.0rc1#666
Conversation
Set the Python version and the container's install pin to 0.6.0rc1 and write the release notes: the inbox, permission levels, conversation history and wolts.nvim, the one-way lodge database change, how to go back with a backup, and the known issues. The TUI stays at 0.5.4.
A release candidate's preparation pins a prerelease in the Dockerfile, and the launcher rightly refuses it for an implicit build or a new lodge. The tests now expect that refusal, and name the release for init, while the pin is a prerelease.
jerpint
approved these changes
Nov 4, 2026
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.
Prepares the first 0.6 release candidate from main.
pyproject.tomland the container'sWOLTSPACE_PYPI_VERSIONpin: 0.6.0rc1.docs/release-notes.md: what's new (inbox, permission levels, conversation history, wolts.nvim, release-line updates), the one-way lodge database change (0.5 refuses the lodge after the first 0.6 start), how to go back with a backup, and known issues.The TUI is unchanged at 0.5.4. Publish with
registry=python: a pre-release TUI version is refused.test/test_native_cli_shadowing.py: the launcher refuses a prerelease pin for an implicit container build or a new lodge, as intended; the tests now expect that while the pin is a prerelease. Until 0.6.0 final,woltspace init/build --latestfrom a main checkout need--version.Users who run a plain
woltspace updatestay on 0.5; the candidate is installed only with--version 0.6.0rc1.Tested: CI green (tests 3.11 and 3.13, package build and verification). A fresh first run of this branch, in a throwaway container with an empty lodge folder and no network path to the host: the default starter installed (onboardie), the lodge reports 0.6.0rc1, schema 1-7, no database or import errors, and
/woltsand/sessionsanswer. With an agent login added, a new onboardie session loaded its start skill and greeted; nothing in Woltspace asked for permission (the only screens before it were Claude Code's own first-launch theme and security notices, from a home folder that had never run it).🦝 read, washed and signed - softie