chore: release 0.6.2, begin 0.6.3.dev0 development#2205
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Automated release PR for 0.6.2, updating the changelog for the release and bumping main to the next development version (0.6.3.dev0) so dev installs are clearly marked.
Changes:
- Bump package version in
pyproject.tomlto0.6.3.dev0. - Add a
0.6.2entry toCHANGELOG.mddated2026-04-13.
Show a summary per file
| File | Description |
|---|---|
pyproject.toml |
Updates the project version to the next dev cycle (0.6.3.dev0). |
CHANGELOG.md |
Records the 0.6.2 release notes. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 0
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.
Automated release of 0.6.2.
This PR was created by the Release Trigger workflow. The git tag
v0.6.2has already been pushed and the release artifacts are being built.Merging this PR will set
mainto0.6.3.dev0so that development installs are clearly marked as pre-release.