-
Notifications
You must be signed in to change notification settings - Fork 261
Post release preparation of version and changelog #7534
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
agoscinski
merged 2 commits into
aiidateam:main
from
agoscinski:chore/post-minor-release
Aug 11, 2026
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -27,7 +27,7 @@ | |
| 'For further information please visit http://www.aiida.net/. All rights reserved.' | ||
| ) | ||
| __license__ = 'MIT license, see LICENSE.txt file.' | ||
| __version__ = '2.9.0' | ||
| __version__ = '3.0.0.dev0' | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🚀 |
||
| __authors__ = 'The AiiDA team.' | ||
| __paper__ = ( | ||
| 'S. P. Huber et al., "AiiDA 1.0, a scalable computational infrastructure for automated reproducible workflows and ' | ||
|
|
||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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
Unreleasedsection). We could just keep them commented, until we actually properly include them in the CHANGELOG of each next version:Alternatives considered were:
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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!