Repository navigation
Prepare 0.1.2: the version, and its section of the changelog - #44
Merged
Merged
Conversation
v0.1.1 was drafted but never published, so 0.1.2 is the first release anyone installs. pubspec.yaml goes to 0.1.2+102 (the release workflow's major*10000 + minor*100 + patch), which is also the version the web app reports, and the Release Notes tab shows that version's section of CHANGELOG.md. [Unreleased] becomes [0.1.2] - 2026-10-04, with what merged since v0.1.1 in the user's words: the Pico W (missing until now), mouse pan, ⌘/ comments, release notes, the macOS Window menu, the brand look and type, the simpler welcome screen, the empty editor, no sign-in UI where there is no sign-in, and the fixes (a new project starts clean, sketch colouring, Help ▸ Welcome, ⌘W). Cloud projects are now said to be in the hosted desktop builds, as the web app leaves accounts out. The changelog test now asks for pubspec.yaml's version and requires its own section, so a version bump without one fails, instead of asking for 0.0.0 and falling back to [Unreleased]. Co-Authored-By: Claude Opus 5.5 (1M context) <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.
Merge after #42 (tagline) and #43 (brand fonts): this changelog describes both.
v0.1.1 was drafted but never published, so 0.1.2 is the first release anyone installs.
pubspec.yaml→0.1.2+102(the release workflow's major·10000 + minor·100 + patch). It's also the version the web app reports, and the Release Notes tab shows that version's changelog section.CHANGELOG.md:[Unreleased]becomes[0.1.2] - 2026-10-04, adding what merged since v0.1.1 in the user's words:release_notes_test.dartnow asks forpubspec.yaml's version and requires its own section, so a version bump without one fails. It used to ask for0.0.0and fall back to[Unreleased]. Checked: bumping to 0.1.3 without a section fails with CHANGELOG.md needs a "## [0.1.3] - " section.After this merges: tag
v0.1.2onmainto build and draft the release for all three platforms, then publish the draft. The unpublished v0.1.1 draft can be deleted.🤖 Generated with Claude Code