Skip to content

docs: align distribution guidance - #286

Merged
jeiel85 merged 1 commit into
mainfrom
agent/align-distribution-guidance
Jul 28, 2026
Merged

docs: align distribution guidance#286
jeiel85 merged 1 commit into
mainfrom
agent/align-distribution-guidance

Conversation

@jeiel85

@jeiel85 jeiel85 commented Jul 28, 2026

Copy link
Copy Markdown
Owner

What changed

  • Makes GitHub Releases the unambiguous source for the current signed APK.
  • Clarifies F-Droid as the automatic-update channel after catalog publication and GitLab as a source mirror.
  • Replaces the stale active roadmap with a July–October stability, distribution, and user-evidence gate; keeps older feature phases as deferred backlog.
  • Records the operating decision and documentation history.

Why

Google Play updates are paused, F-Droid can publish after GitHub, and GitLab release assets are not reliable enough to promise as an equal installation path.

Validation

  • pwsh scripts/verify-landing-versions.ps1
  • README distribution-guidance invariant check across all six languages
  • git diff --check
  • ./gradlew test passed on the unchanged v2.32.1 source tree during the repository assessment.

@jeiel85
jeiel85 marked this pull request as ready for review July 28, 2026 01:00

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 450dd11fed

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread README.md
> **Google Play updates are currently on hold.** New versions won't be pushed to the Play Store until a Korean business-registration policy requirement for the solo developer is resolved. For the current release, use **GitHub Releases**. F-Droid remains the recommended update path when its build has caught up. (If you already installed it from the Play Store, it keeps working.)

- **F-Droid** *(recommended)*: [Markleaf on F-Droid](https://f-droid.org/packages/com.markleaf.notes/) — search in the F-Droid client or install via the link above. It uses the same signing key (SHA-256 `0be97352…f91a`), so updates continue seamlessly even if you sideloaded an APK from GitHub or GitLab Releases.
- **F-Droid** *(recommended for automatic updates)*: [Markleaf on F-Droid](https://f-droid.org/packages/com.markleaf.notes/) — search in the F-Droid client or install via the link above. Its catalog may publish after GitHub; if it does not yet show the current version, use GitHub Releases below. It uses the same signing key (SHA-256 `0be97352…f91a`), so updates continue seamlessly even if you first sideload a GitHub APK.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Align the landing pages with the new release hierarchy

Visitors who use GitHub Pages instead of a README still see F-Droid labeled “Recommended · Latest version” in every localized docs/index*.html install card, while this change says that F-Droid may lag and GitHub Releases is the current-version source. When the catalog is behind—the exact scenario addressed here—the public surfaces now give contradictory guidance and can direct users to an older build, so update the six localized landing pages alongside the READMEs.

AGENTS.md reference: AGENTS.md:L238-L238

Useful? React with 👍 / 👎.

@jeiel85
jeiel85 merged commit 72d0256 into main Jul 28, 2026
5 checks passed
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