chore(release): prepare coordinated MAX 0.27.0 candidate - #384
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
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.
Prepares MAX 0.27.0 with canonical permissions across CLI/native/server/MCP and explicit config migration, local message locator reads, and scoped command discovery. Pins latest published core 0.17.0 / messaging 0.140.0, including the SQLite initialization contention fix. Aligns user docs, MCP/bot/security recipes, diagnostics, generated commands and the bundled agent skill. The changelog explains the changed MCP defaults and migration while preserving published 0.26.0 history exactly.
Merged main: a580979. Fresh isolated main verification: all 14 release checks, docs/parity, 1361 tests passed / 2 skipped; main CI 37160454900 success. Tested PR head 47eac83 passed all Linux/Bun/macOS/Windows checks. Isolated leaf/group/invalid discovery checks passed without account/store access.
Telegram's coordinated 0.26.0 release preparation merged as leemour/tg-cli#254 with the same shared pins. Live account verification, changelog review and owner-only MAX report sign-off remain pending before CLI publication; no live operations were performed by this preparation.