Skip to content

docs: CHANGELOG + README refresh for the fork; bump to 3.9.0#82

Merged
AsafMah merged 2 commits into
devfrom
feat/docs-changelog-v3.9.0
Jun 10, 2026
Merged

docs: CHANGELOG + README refresh for the fork; bump to 3.9.0#82
AsafMah merged 2 commits into
devfrom
feat/docs-changelog-v3.9.0

Conversation

@AsafMah

@AsafMah AsafMah commented Jun 10, 2026

Copy link
Copy Markdown
Owner

Summary

Adds a proper changelog, refreshes the README to describe this fork's purpose and features, and sets the next release to 3.9.0 (clean break from the 3.8.x line to avoid confusion).

Changes

  • CHANGELOG.md (new) — Keep-a-Changelog format covering LeanTypeDual's own releases (3.8.1–3.8.6 from the fastlane notes + the 3.9.0 work). Provenance is coarse: a single Upstream baseline marker for the HeliBoard/LeanType base, not per-line attribution. Fork-only features live in the README.
  • README.md — now leads with the fork's identity and purpose:
    • Two-thumb (dual-thumb) typing is documented as the namesake flagship — it was completely absent before despite being the "Dual".
    • Accurate lineage: HeliBoard → LeanType (AI layer) → LeanTypeDual.
    • Current feature set: graduated trust, flag/Add/Block + Blocklist, undo-word key, per-dictionary enable/disable, edge-scroll, etc.
    • Credits attribute LeanTypeDual (AsafMah) on top of LeanType (LeanBitLab); sponsor kept as-is per your call.
  • Version → 3.9.0 (versionCode 3860 → 3900) + fastlane/.../3900.txt user-facing notes.
  • AGENTS.md — changelog/release convention (coarse provenance, versionCode = major*1000+minor*100+patch*10, fastlane note on release) so it stays current.

3.9.0 content (since the 3.8.6 tag)

Graduated trust (#39), undo-word (#35), trace recorder (#20), popup tiling (#36), backspace corpus (#21), badge CI fix (#76), backspace-stack refactor (#31), HeliBoard QoL backports (#74), native engine tests in CI (#78).

Deliberately left (separate branding/distribution decision)

  • README Download buttons still point at LeanBitLab/HeliboardL + the com.leanbitlab.leantype F-Droid package.
  • The banner SVG still reads "LeanType".

Say the word and I'll redirect those to AsafMah/LeanType / regenerate the banner. No code changes here (docs + a version literal), so nothing to build.

AsafMah added 2 commits June 10, 2026 11:41
- CHANGELOG.md: Keep-a-Changelog history of LeanTypeDual's own releases
  (3.8.1-3.8.6 from fastlane + the 3.9.0 work), with a coarse 'Upstream'
  baseline marker instead of per-line provenance.
- README: lead with the fork's identity + purpose (two-thumb / dual-thumb
  typing — the namesake feature, previously undocumented), accurate
  HeliBoard -> LeanType -> LeanTypeDual lineage, and the current feature
  set incl. graduated trust, blocklist, undo-word, per-dictionary control.
  Credits now attribute LeanTypeDual (AsafMah) on top of LeanType
  (LeanBitLab); sponsor kept as-is.
- Bump versionName 3.8.6 -> 3.9.0 (versionCode 3860 -> 3900) so the next
  release is a clean 3.9.0; add fastlane 3900.txt user-facing notes.
- AGENTS.md: changelog/release convention (coarse provenance, versionCode
  scheme, fastlane note on release).

Note: README Download buttons still point at LeanBitLab/HeliboardL and the
banner SVG still reads 'LeanType' — left for a separate distribution/branding
decision.
…peDual

- README Download buttons now point at AsafMah/LeanType (GitHub releases +
  Obtainium); drop the F-Droid button (the fork ships as
  com.asafmah.leantypedual, not the upstream com.leanbitlab.leantype, and is
  not published on F-Droid).
- Banner SVGs (light + dark) now read 'LeanTypeDual' (Lean / Type-purple /
  Dual); alt text updated. Verified rendering (no clipping).
- Lineage/credit links to github.com/LeanBitLab kept (correct attribution).
@AsafMah AsafMah merged commit 6db1551 into dev Jun 10, 2026
1 check passed
@AsafMah AsafMah deleted the feat/docs-changelog-v3.9.0 branch June 10, 2026 09:07
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