Repository navigation
Prepare 2.0.0 - #102
Merged
Merged
Prepare 2.0.0#102
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Release prep for 2.0.0. Not ready to merge until the TODO bullets are replaced.
Changes
2.0.0rc2→2.0.0inpyproject.toml,modsync/__init__.pyanduv.lock.CHANGELOG.md: Unreleased becomes## [2.0.0] - 2026-10-28, with a new empty Unreleased above it.### Since 1.0.0. With Collapse the detailed changelog lists in release notes #101, that's the only part the release page shows uncollapsed.### Since 1.0.0links the 1.1.0-beta1, beta2, rc1 and rc2 releases. It sits inside the collapsed part, followed by Unreleased's Added entry (the Steam Frame page).type="stable"2.0.0 release with a one-paragraph draft description, which Discover shows. Edit it as you like. It passesappstreamcli validate.If the release goes out on a later day, the date needs changing in both the CHANGELOG heading and the metainfo.
After merging
Tag the merge commit
v2.0.0and push the tag. The release workflow builds and publishes everything.Testing
scripts/changelog_section.py 2.0.0finds the section.🤖 Generated with Claude Code