NanoLedger

be.chvp.nanoledger
by Zapstore _@zapstore.dev

Republished from GitHub / F-Droid by the Zapstore main account.

NanoLedger is a [Plain Text Accounting](https://plaintextaccounting.org/) data entry app for Android.

First release: Nov 15, 2025, 7 total releases.

Most recent release: Apr 5, 2026.

Repo

Appears in 0 app stacks.

0 sats / 0 zaps received in the past year.

Sats Received

Underlying data available via MCP: app_zaps, app_releases.

Zap Count

Underlying data available via MCP: app_zaps, app_releases.

Releases

  • Apr 5, 2026 1.4.1
    ## ๐Ÿ› Bug Fixes * Trim trailing whitespace when formatting a posting (#426) @chvp
  • Mar 7, 2026 1.4.0
    ## ๐Ÿš€ Features * Add advanced edit functionality (#392) @chvp ## ๐Ÿ› Bug Fixes * Search in combined payees and notes when only one is enabled (#409) @chvp * Fix saving transactions when there is only a payee/note (#406) @chvp * Fix formatting of empty payee and note when writing transaction (#400) @chvp * Don't require payee for validity (#399) @chvp
    Moreโ€ฆ
    ## ๐Ÿงฐ Maintenance * Update readme now that costs and assertions can be edited (#403) @chvp * Fix string syntax in release workflow (#402) @chvp * Publish betas as prereleases on GitHub (#401) @chvp
  • Feb 21, 2026 1.4.0-beta.3
    Note that v1.4.0-beta.2 was skipped due to an issue with the release workflow. ## ๐Ÿš€ Features * Add advanced edit functionality (#392) @chvp ## ๐Ÿ› Bug Fixes * Fix formatting of empty payee and note when writing transaction (#400) @chvp * Don't require payee for validity (#399) @chvp
    Moreโ€ฆ
    ## ๐Ÿงฐ Maintenance * Fix string syntax in release workflow (#402) @chvp * Publish betas as prereleases on GitHub (#401) @chvp
  • Feb 21, 2026 1.4.0-beta.1
    ## ๐Ÿš€ Features * Add advanced edit functionality (#392) @chvp
  • Feb 21, 2026 1.3.1
    ## ๐Ÿงฐ Maintenance * Update Java to 21 (#398) @chvp
  • Feb 14, 2026 1.3.0
    ## ๐Ÿš€ Features * Allow searching by the amount in a posting (#391) @chvp
  • Nov 15, 2025 1.2.2 Release page โ†’
    ## ๐Ÿ› Bug Fixes * Use KeyboardType.Number instead of Decimal (#358) @agarciamontoro