Skip to content

Conversation

@denialhaag
Copy link
Contributor

@denialhaag denialhaag commented Oct 14, 2025

Description

This PR prepares the release of v3.3.0.

Checklist:

  • The pull request only contains commits that are focused and relevant to this change.
  • I have added appropriate tests that cover the new/changed functionality.
  • I have updated the documentation to reflect these changes.
  • I have added entries to the changelog for any noteworthy additions, changes, fixes, or removals.
  • I have added migration instructions to the upgrade guide (if needed).
  • The changes follow the project's style guidelines and introduce no new warnings.
  • The changes are fully tested and pass the CI checks.
  • I have reviewed my own code changes.

Summary by CodeRabbit

  • Changed

    • Bumped minimum supported core component to a newer required version.
    • Ended support for Python 3.9; testing and wheel distributions updated accordingly.
  • Documentation

    • Added release notes and upgrading guidance for v3.3.0.
    • Updated changelog and version comparison links, including new PR reference.
    • Updated “Unreleased” links to point to v3.3.0.

@github-project-automation github-project-automation bot moved this to In Progress in MQT Verification Oct 14, 2025
@denialhaag denialhaag self-assigned this Oct 14, 2025
@denialhaag denialhaag added the documentation Improvements or additions to documentation label Oct 14, 2025
@denialhaag denialhaag requested a review from burgholzer October 14, 2025 13:19
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Oct 14, 2025

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

Adds a 3.3.0 entry to release notes and upgrading guide: bumps minimum mqt-core to 3.3.1, declares Python 3.9 end-of-life, updates Unreleased/version comparison links to reference v3.3.0, and adds PR reference #735.

Changes

Cohort / File(s) Summary
Docs: Changelog
CHANGELOG.md
Add 3.3.0 release entry under Unreleased, bump minimum mqt-core to 3.3.1, add Upgrading note and PR #735, update Unreleased/version comparison links to v3.3.0.
Docs: Upgrading guide
UPGRADING.md
Add 3.3.0 section stating Python 3.9 is no longer supported, update Unreleased link to v3.3.0...HEAD, and add v3.3.0 comparison link v3.2.0...v3.3.0.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

A rabbit tapped the release drum, hop-hop—3.3!
Notes tucked in the burrow, tidy as can be.
Farewell, 3.9—your carrots rotted free.
Core nudged forward, links hopped to see.
I thump and nibble docs—celebrate with me! 🥕🐇

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Title Check ✅ Passed The title concisely and accurately summarizes the primary change by indicating this PR prepares the v3.3.0 release, with no misleading or irrelevant content.
Description Check ✅ Passed The PR description follows the repository’s template by including a ## Description section with a concise summary of the change and a ## Checklist that mirrors the template; the Fixes line is correctly omitted since no issue is being closed and no new dependencies apply.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between abeb308 and e707808.

📒 Files selected for processing (1)
  • UPGRADING.md (2 hunks)

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3f23bfc and abeb308.

📒 Files selected for processing (2)
  • CHANGELOG.md (2 hunks)
  • UPGRADING.md (2 hunks)
🧰 Additional context used
🪛 LanguageTool
UPGRADING.md

[grammar] ~7-~7: Use correct spacing
Context: ...ANGELOG.md). ## [Unreleased] ## [3.3.0] ### End of support for Python 3.9 Starting ...

(QB_NEW_EN_OTHER_ERROR_IDS_5)

CHANGELOG.md

[grammar] ~12-~12: Use correct spacing
Context: ...## [Unreleased] ## [3.3.0] - 2025-10-14 _If you are upgrading: please see [`UPGRA...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~14-~14: Use colons correctly
Context: ...] ## [3.3.0] - 2025-10-14 _If you are upgrading: please see [UPGRADING.md](UPGRADING.m...

(QB_NEW_EN_OTHER_ERROR_IDS_30)


[grammar] ~14-~14: Use correct spacing
Context: ... see UPGRADING.md._ ### Added - 👷 Enable testing on Python 3.1...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~16-~16: Use correct spacing
Context: ...DING.md`](UPGRADING.md#330)._ ### Added - 👷 Enable testing on Python 3.14 ([#730]...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~18-~18: There might be a mistake here.
Context: ...Python 3.14 ([#730]) ([@denialhaag]) ### Changed - ⬆️ Bump minimum required `mqt...

(QB_NEW_EN)


[grammar] ~20-~20: Use correct spacing
Context: ...[#730]) ([@denialhaag]) ### Changed - ⬆️ Bump minimum required mqt-core vers...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~22-~22: Use correct spacing
Context: ... to 3.3.1 ([#735]) ([@denialhaag]) ### Removed - 🔥 Drop support for Python 3....

(QB_NEW_EN_OTHER_ERROR_IDS_5)

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Signed-off-by: Daniel Haag <[email protected]>
Copy link
Member

@burgholzer burgholzer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍🏼 Let's get this release out! 🚀

@denialhaag denialhaag merged commit 8ec24c5 into main Oct 14, 2025
19 of 20 checks passed
@denialhaag denialhaag deleted the prepare-release-3-3-0 branch October 14, 2025 13:37
@github-project-automation github-project-automation bot moved this from In Progress to Done in MQT Verification Oct 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants