chore: prepare wbot 0.2.0 stable release - #3
Merged
Merged
Conversation
…sions and migration notes
Deniffer001
marked this pull request as ready for review
September 21, 2026 03:31
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.
Publish stable
0.2.0from0.2.0-rc.1, synchronizing the package, lockfile, Codex and Claude plugin manifests, and pinned runtime artifact URLs. Add migration steps from0.1.x; RC consumers have no additional API migration.Remove a hardcoded current-version assertion from the release-impact test. Existing CLI, MCP, plugin, and artifact version-consistency tests remain in place.
Validation:
0.2.0artifact, release preflight, and curated release notes verified.0.2.0and checksum-verified published0.1.2artifacts each successfully read conversations, history, and updates from the current test Platform.The published-client/backend check was performed manually against the current test deployment. Automating that check in backend deployment CI remains a separate follow-up; no backend is deployed by this PR.
Merging this version change into
maintriggers the public stable release. The release workflow reruns its candidate-artifact compatibility gate before creating the immutable tag and assets.