Skip to content

chore: bump version to v1.2.3 - #55

Closed
github-actions[bot] wants to merge 1 commit into
mainfrom
version-bump/v1.2.3
Closed

github-actions[bot] wants to merge 1 commit into
mainfrom
version-bump/v1.2.3

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

🚀 Automated Version Bump: v1.2.3

This PR automatically bumps the version based on conventional commits since the last release.

📊 Release Summary

  • Version Type: patch
  • New Version: v1.2.3
  • Commits Included: 1
  • Generated: 2026-08-24 22:50:21 UTC

📝 Changelog Preview

🐛 Bug Fixes

🎯 What Happens Next

  1. Review: Maintainers review this automated version bump
  2. Merge: When merged, a git tag v1.2.3 will be created
  3. Release: The tag will trigger the automated release workflow
  4. Publish: Package will be published to PyPI automatically

✅ Pre-Release Checklist

  • Version number looks correct
  • Changelog entries are accurate
  • No breaking changes in patch/minor releases
  • All CI checks pass

This PR was created automatically by the version bump workflow. The release will be fully automated upon merge.

This patch version bump includes:
- 1 commits since last release
- Automated changelog generation
- Version update in pyproject.toml

Release will be triggered automatically when this PR is merged.
@github-actions github-actions Bot added release Release-related pull requests and issues automated Automatically generated content labels Aug 24, 2026
@github-actions
github-actions Bot requested a review from trsdn as a code owner August 24, 2026 22:50
@github-actions github-actions Bot added release Release-related pull requests and issues automated Automatically generated content labels Aug 24, 2026
@trsdn

trsdn commented Aug 25, 2026

Copy link
Copy Markdown
Owner

Geschlossen: Dieser automatische Bump geht von 1.2.2 aus, aber auf PyPI ist bereits 2.0.0 veröffentlicht (getaggt v2.0.0). Ein Release als 1.2.3 wäre eine Rückwärtsversion unterhalb der publizierten 2.0.0.

Ursache: pyproject.toml auf main wurde beim 2.0.0-Release nie nachgezogen, der version-bump-Workflow rechnet daher von einer falschen Basis. Wird stattdessen direkt auf 2.0.0 synchronisiert.

@trsdn trsdn closed this Aug 25, 2026
@trsdn
trsdn deleted the version-bump/v1.2.3 branch August 25, 2026 05:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated Automatically generated content release Release-related pull requests and issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants