🔖 Prepare release of v2.2.0

[denialhaag]

Description

This PR prepares the release of v2.2.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.

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR updates release documentation for version 2.2.0, adding new sections to CHANGELOG.md and UPGRADING.md while updating version comparison links from unreleased to reference the v2.2.0 release tag.

Changes

Cohort / File(s)	Summary
Release documentation CHANGELOG.md, UPGRADING.md	Adds new 2.2.0 release sections with upgrade notes and updates unreleased comparison links to reference v2.2.0...HEAD and v2.1.0...v2.2.0 respectively.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• 🔖 Prepare release of v3.4.0 qcec#823: Makes identical documentation updates—adding a new release section and updating unreleased/compare links in CHANGELOG.md and UPGRADING.md.

Suggested reviewers

• burgholzer

Poem

🐰 Hops through the docs with glee,
Version two-point-two to see,
Links updated, clean and bright,
Release notes organized just right! ✨

🚥 Pre-merge checks | ✅ 3 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	PR description is incomplete with version mismatch (title/commits reference v2.2.0 but description states v3.5.0) and missing required sections like motivation, context, and dependencies.	Clarify the correct release version (v2.2.0 or v3.5.0), add detailed description of changes, motivation, and context. Verify all checklist items accurately reflect the actual work completed.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly indicates this PR prepares a release for v2.2.0, which directly aligns with the changelog and upgrade guide updates shown in the changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch prepare-release-2-2-0

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@UPGRADING.md`:
- Line 7: The release version in UPGRADING is set to "## [2.2.0]" but the PR
description mentions "v3.5.0"; confirm which is correct and make them consistent
by either updating the UPGRADING header "## [2.2.0]" to "## [3.5.0]" if the PR
is for v3.5.0, or editing the PR description to reference v2.2.0 if that is the
intended release; ensure the text in the PR title/description and the UPGRADING
header match exactly.