chore(release): bump app.py to 0.2.0 - #145
Merged
Merged
Conversation
📝 WalkthroughWalkthroughThe application version changed from ChangesRelease version alignment
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
timon0305
approved these changes
Jul 30, 2026
wpak-ai
approved these changes
Jul 30, 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.
CLoses #142
Release cut for v0.2.0. Stacks on #144, which already landed the [0.2.0] changelog on master.
This PR bumps app.py version from 0.2.0.dev0 to 0.2.0 and updates docs/deprecation-policy.md so it no longer pins the old dev suffix. git grep 0.2.0.dev0 should return nothing after merge.
There is no wheel or npm publish step.
After this merges, tag v0.2.0 on the release commit and create the GitHub Release with notes copied from the [0.2.0] section in CHANGELOG.md.
Summary by CodeRabbit
Release
Documentation