Post release preparation of version and changelog

[agoscinski]

No description provided.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 59841ffc-38b3-485f-8160-e645b3c2950c

📥 Commits

Reviewing files that changed from the base of the PR and between 4228604 and a6977ff.

📒 Files selected for processing (1)

• CHANGELOG.md

---

📝 Walkthrough

Walkthrough

The package version changed to 3.0.0.dev0. The changelog now includes an Unreleased section and revised v2.9.0 interface-extension lists.

Changes

Release metadata

Layer / File(s)	Summary
Version and changelog updates src/aiida/__init__.py, CHANGELOG.md	The package version changed to 3.0.0.dev0. The changelog gained placeholder sections and updated interface-extension entries.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

• aiidateam/aiida-core#7458: Both changes update the package version and changelog for adjacent release states.

Suggested reviewers: edan-bainglass, geigerj2

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	No pull request description was provided, so its relevance to the changeset cannot be assessed.	Add a brief description covering the version update to 3.0.0.dev0 and the changelog changes.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the version update and changelog preparation described in the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.69%. Comparing base (299e945) to head (01307cc).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7534      +/-   ##
==========================================
+ Coverage   80.68%   80.69%   +0.01%     
==========================================
  Files         581      581              
  Lines       47068    47068              
==========================================
+ Hits        37972    37975       +3     
+ Misses       9096     9093       -3     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[edan-bainglass]

LGTM! Let's go 💪

[GeigerJ2]

🚀

[GeigerJ2]

Those currently break the anchors for the TOC of v2.9.0. If you click there (TOC entry with the same name under v2.9.0), you currently end up at the anchors here (of the Unreleased section). We could just keep them commented, until we actually properly include them in the CHANGELOG of each next version:

## Unreleased

<!-- Sections below are integrated into the changelog when the release notes are written. -->
<!-- Uncommenting one shadows the anchors of the newest release section. -->

<!-- ### New features -->

<!-- ### Behavior changes -->

<!-- ### Fixes -->

<!-- ### Deprecations -->

Alternatives considered were:

• doing the headings here just as bold statements -> we already use bold headings throughout the changelog
• changing the explicit tags / anchors for the released headings -> seems too complicated, just having them commented out here seems sufficient to me

[agoscinski]

That does not really solve the problem, once you add changes the overshadowing happens again. It's a bit more tricky to solve in a way that is developer friendly and works for the MD view on github as well for the sphinx build on RTD. I made PR #7541 that detects this overshadowing of anchors. There I will elaborate the problem more, once I found a solution.

[GeigerJ2]

Well, that would not be the case, when we keep the headings commented out (it's just for internal categorization anyway, until an actual release). But, I do agree it's best to have an automatic check that captures the unintended behavior. Feel free to request review on #7541 when ready, thanks!

[GeigerJ2]

#7329 ("📚 Document workflow tools entry points") touches only docs/source/howto/plugins_develop.rst and docs/source/topics/plugins.rst. The property came from #6884.

[GeigerJ2]

Same here as in my comment below.