chore: bump to 1.0.20, and require a version bump per material change - #83
Merged
Merged
Conversation
The raw-HTML <table> fix (#82) landed on main without a version bump, so the running build stayed 1.0.19 — identical to the latest release — and the in-app updater correctly reported "no update found". The fix was on main and unreachable by every installed user. Bump to 1.0.20+21, and write the rule into CLAUDE.md as standing rule 9 plus a line in the definition of done, so the bump rides in the feature PR rather than being remembered at release time. The site's JSON-LD softwareVersion/datePublished stay at 1.0.19 — per RELEASING.md step 4 those follow the published release, and advertising a version with no downloadable assets would be worse than lagging. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LKDdZmyggGAvaakLhAaNEM
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
1 participant
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.
The raw-HTML
<table>fix (#82) landed onmainwithout a version bump, so the running build stayed1.0.19+20— byte-for-byte the same version string as the latest release. The in-app updater compares those, found no difference, and correctly reported "no update found". The fix was onmainand unreachable by every installed user.Changes
pubspec.yaml:1.0.19+20→1.0.20+21.CLAUDE.md: new standing rule 9 — any change to app behaviour carries itsversion:bump in the same PR, unasked. Docs-only / CI-only / website-only changes are exempt. Also added to the definition of done, since that's the checklist actually consulted per change.Deliberately not changed:
softwareVersion/datePublishedin thedocs/index.htmlJSON-LD. PerRELEASING.mdstep 4 those track the published release, and pointing them at a version with no downloadable assets would be worse than lagging. They move when the tag is pushed.This PR doesn't release anything — it only makes a release possible. Tagging
v1.0.20is a separate step.flutter analyzeclean,flutter testgreen (160).🤖 Generated with Claude Code
https://claude.ai/code/session_01LKDdZmyggGAvaakLhAaNEM