Repository navigation
chore: release 1.2.5, begin 1.2.6.dev0 development - #5167
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues were identified in the version bump and changelog updates.
No open issues 🎉
What changed in this PR
This automated release PR records the 1.2.5 release and advances the project to the next development version, 1.2.6.dev0.
Changes:
- Updates the package version in
pyproject.tomlto1.2.6.dev0. - Adds the generated 1.2.5 release notes dated 2026-10-28 to
CHANGELOG.md.
| File | Description |
|---|---|
pyproject.toml |
Sets the package to the next development version, 1.2.6.dev0. |
CHANGELOG.md |
Records the 1.2.5 release and its included changes. |
Review effort: Lite (auto)
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 1.2.5.
This PR was created by the Release Trigger workflow. The git tag
v1.2.5has already been pushed and the release artifacts are being built.Merging this PR will set
mainto1.2.6.dev0so that development installs are clearly marked as pre-release.