Repository navigation
chore: prepare 1.7.0 - #203
Merged
Merged
Conversation
Version 1.7.0 and a curated "## [1.7.0]" section in both changelogs, above the alpha and beta sections (kept, as in 1.6.0), with the item the update notice shows first. PRD D-27 (Legacy in the same release) and the manual checks for the draft and the Legacy files in docs/TESTING.md. The READMEs move to 1.7.0 when the draft is published, so their links don't point at a release nobody can see yet. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes: Reviewed the 1.7.0 release preparation and its release-note and manual-testing updates.
- Release notes: Adds the curated 1.7.0 sections in Portuguese and English, with the user-facing highlights, changes, and fixes.
- Version: Promotes the application package and informational versions to
1.7.0. - Release planning and validation: Records the Legacy-release decision in
docs/PRD.mdand adds draft-release and Legacy checks todocs/TESTING.md.
gpt-6-luna | 𝕏
Closed
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.

What
Prepares 1.7.0, which goes out first as a draft release (see #202) with the Legacy build attached (#200).
ConsoleMode.csproj:1.7.0.## [1.7.0]section (what's new, changes, fixes, with the PR numbers of the alpha and beta items it sums up) above the pre-release sections, which stay as they are, as 1.6.0 did. The first item, the single console-style interface, is the one the in-app update notice shows. The Legacy download is an item of the section; the workflow adds the download names to the release notes.docs/PRD.md: D-27, Legacy in the same release.docs/TESTING.md: the manual checks for the draft and for switching between 1.7.0 and Legacy.Supersedes #179 (the first 1.7.0 prep, from before alpha.3). The READMEs still say 1.6.2 on purpose: they change in a separate PR when the draft is published, so the download link never points at a release the public can't see.
Testing
dotnet test: 677 passing. The release notes are built from the## [1.7.0]sections by the workflow.🤖 Generated with Claude Code