Skip to content

docs: refresh release docs and bump build number#649

Merged
everpcpc merged 2 commits intomainfrom
codex/update-release-docs
Mar 11, 2026
Merged

docs: refresh release docs and bump build number#649
everpcpc merged 2 commits intomainfrom
codex/update-release-docs

Conversation

@everpcpc
Copy link
Copy Markdown
Owner

Problem

The checked-in release copy was partially refreshed, but the App Store changelog had drifted away from the full set of user-visible changes since v4.1. The branch also needed the next project build number before opening a release PR.

Approach

Refresh the release-facing docs as one content pass, then regenerate the App Store changelog from the latest tag range instead of only the recent docs-update window. Keep the build bump isolated as a follow-up commit by running make bump after the docs commit so the generated version change stays reviewable.

Scope

  • update the README, App Store description, and landing page messaging for the latest reader improvements
  • regenerate APP_STORE_CHANGELOG.txt from the v4.1..HEAD user-visible release scope
  • bump CURRENT_PROJECT_VERSION from 359 to 360 via make bump

Validation

  • make bump
  • No build run (docs metadata update plus version bump only)

Update the README, App Store description, landing page, and App Store changelog to reflect the current release messaging. Keep the changelog aligned with the user-visible changes since v4.1 while syncing the docs copy with the latest reader improvements and Live Activity behavior.
@everpcpc everpcpc merged commit 25fd955 into main Mar 11, 2026
3 checks passed
@everpcpc everpcpc deleted the codex/update-release-docs branch March 11, 2026 03:48
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.

1 participant