docs: correct the 8.0.0 changelog entry

[FBumann]

Problem

8.0.0 shipped with a ⚠ BREAKING CHANGES notice describing a clustering format change that is not in the release.

#739 introduced that change and #746 reverted it before release. Release-please does not pair a revert with its original, so the BREAKING CHANGE: footer both drove the major version bump and rendered into the published notes.

The release is in fact non-breaking. Verified by loading artifacts from released versions against this code:

written by	loads	expands
7.2.3 (plain, multi-period)	yes	yes
6.2.1 (plain, solved, multi-period, period+scenario)	yes	yes
6.1.0 (plain)	yes	yes

Serialized clustering is unchanged from 7.2.1, and 6.x files that stopped loading under 7.0 load again as of #757 — so 8.0.0 is more compatible than its predecessor, not less.

Change

CHANGELOG.md only, for the already-published 8.0.0 section:

• the breaking-change notice becomes a note explaining why the major carries no breaking change
• refactor: drop clustering dim-rename layer via tsam-xarray DimNames #739 moves from Code Refactoring to Reverts, stating it was reverted before release

Uses the !!! note admonition already used elsewhere in this file, so it renders in the docs site.

Typed docs: so it does not itself trigger a release. The v8.0.0 GitHub release notes are being corrected separately, in place.

Follow-up

8.0.1 should pick up #755 (raises the tsam_xarray floor to 0.6.5). Without it, anyone resolving to 0.6.5 gets a cluster_weights deprecation warning — noisy at runtime, and a hard failure under -W error.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@FBumann, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 27 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 4445f8a4-fa12-4ec2-9ae9-d81addb02db9

📥 Commits

Reviewing files that changed from the base of the PR and between 489111c and bb787dc.

📒 Files selected for processing (1)

• CHANGELOG.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/correct-8.0.0-changelog

---

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