Skip to content

take over release notes from score main#237

Open
RolandJentschETAS wants to merge 4 commits into
mainfrom
improvement_update_release_notes
Open

take over release notes from score main#237
RolandJentschETAS wants to merge 4 commits into
mainfrom
improvement_update_release_notes

Conversation

@RolandJentschETAS
Copy link
Copy Markdown
Contributor

@RolandJentschETAS RolandJentschETAS commented May 21, 2026

@github-actions
Copy link
Copy Markdown

The created documentation from the pull request is available at: docu-html

@AlexanderLanin
Copy link
Copy Markdown
Member

Reviewed; LGTM

Comment thread docs/index.rst Outdated
Comment on lines +18 to +21
Newest Release Notes
--------------------

:doc:`score_releases/release_note_score_07`
:doc:`score_releases/release_note_score_v0_7`
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we remove this section if we now list all release notes below?
No need to duplicate and clutter

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would be fine for me. It also reduces some warnings. Not sure, if we should put the release notes section up as first point.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

might be actually a good idea

Comment thread docs/conf.py
Comment on lines +28 to +35
# Exclude external release notes that are now maintained locally in docs/score_releases/
exclude_patterns = [
"_collections/score_platform/docs/score_releases/score_releases/**",
]

# Suppress toc.excluded warnings from external modules referencing excluded docs
suppress_warnings = ["toc.excluded"]

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually lets not introduce this workaround.

Merge score PR first and use new hash, so these needs won't be a problem anymore

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hope, we do not end up in a deadlock

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants