Repository navigation
Update STATE.md after fork sync with upstream 0.9.0 - #3
Merged
Merged
Conversation
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.
STATE.md only: records the 17-10-2026 fork sync at upstream v0.9.0 and sets the next action to LUKS2/Argon2 real-cryptsetup check.
Tests on synced main: unittest 1422 run, OK (14 skipped); smoke.py all checks passed (25 ok).
Ahead/behind vs upstream not checked: git fetch upstream was not approved in the sandbox.
Queued from the dashboard (item 128). The request:
Opened by the queue runner on LXC 113. The runner squash-merges this once CI checks pass.
🤖 Generated with Claude Code