Prepare for new dev-cycle

[spoorcc]

See release procedure in contributing.rst

Summary by CodeRabbit

• Documentation
  • Updated changelog to reflect upcoming version 0.12.0 release.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

A new unreleased release section for version 0.12.0 has been added to the changelog at the top, marked with an "Under development..." bullet point. Existing release sections remain unchanged.

Changes

Cohort / File(s)	Summary
Changelog Update CHANGELOG.rst	Added unreleased 0.12.0 section header with "Under development..." placeholder at the top of the changelog; all existing release sections remain intact

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Pre-merge checks

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Prepare for new dev-cycle' directly relates to the main change: adding a new unreleased release header for version 0.12.0 to CHANGELOG.rst, which is the standard first step in preparing for a new development cycle.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d553575 and 7e92b7f.

📒 Files selected for processing (1)

• CHANGELOG.rst

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (20)

• GitHub Check: Publish Python distribution 📦 to TestPyPI
• GitHub Check: build / build (ubuntu-latest)
• GitHub Check: build / build (windows-latest)
• GitHub Check: build / Build wheel 📦
• GitHub Check: Codacy Static Code Analysis
• GitHub Check: run / run (windows-latest, 3.12)
• GitHub Check: run / run (macos-latest, 3.14)
• GitHub Check: run / run (windows-latest, 3.14)
• GitHub Check: run / run (windows-latest, 3.13)
• GitHub Check: run / run (ubuntu-latest, 3.12)
• GitHub Check: run / run (windows-latest, 3.9)
• GitHub Check: run / run (windows-latest, 3.11)
• GitHub Check: run / run (ubuntu-latest, 3.13)
• GitHub Check: run / run (macos-latest, 3.10)
• GitHub Check: run / run (ubuntu-latest, 3.9)
• GitHub Check: run / run (windows-latest, 3.10)
• GitHub Check: run / run (ubuntu-latest, 3.10)
• GitHub Check: test / test
• GitHub Check: run / test-cygwin
• GitHub Check: DevContainer Build & Test

🔇 Additional comments (1)

CHANGELOG.rst (1)

1-5: ✓ Proper release cycle setup.

The new unreleased section for version 0.12.0 follows the correct format and structure used for all other releases in the changelog. The version bump from 0.11.0 to 0.12.0 is logical, the "(unreleased)" marker is appropriate, and the "Under development..." placeholder will be replaced with actual release notes as features are added during the development cycle.

---

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.}