Per-version user-facing changelog moved out of the README table into
PREVIOUS_HISTORY.md (newest-first sections, Development Plan §11.1).
On tag push the workflow now harvests the matching section via
scripts/ci/release-notes.py and uses it as the release description,
uploading an Incido-<version>-changes.md beside the APKs; a missing
section falls back to the plain default description. CONTRIBUTING §5
documents the new release-notes maintenance step.
The build step minted a fresh keystore inside the checkout on every
run, so each CI release was signed with a different key. Upgrading
from any previous release then failed with a signature conflict
(INSTALL_FAILED_UPDATE_INCOMPATIBLE) — and with allowBackup=false,
the only workaround was uninstalling, which destroys the user's
notes.
The keystore is now minted once in /tmp/gitea-runner-work (the same
persistent cache that already holds the JDK and Android SDK) and
copied into the checkout before building. Every release from now on
shares one signing key, so in-place upgrades work. Only a runner-host
rebuild would mint a new key (breaking exactly one upgrade).
Note: v0.3.7.0 was signed with an ephemeral key that no longer
exists, so the v0.3.7.0 -> v0.3.7.1 upgrade still requires a one-time
uninstall (export a backup first).
The v0.3.7.1 release run failed in the attach step: the 28.7 MB debug
APK upload took ~126s through the Cloudflare proxy, which returned
"error code: 524" (origin timeout, ~100s limit). The step then crashed
parsing the non-JSON error page as JSON, and the release APK was never
attempted — leaving release 36 with zero assets.
upload_asset() now:
- retries with --retry-all-errors so HTTP error responses (524) are
retried, not just connection failures;
- verifies success server-side by listing the release assets after
each attempt (a 524 often means the origin saved the file before
Cloudflare gave up, so the response body is not trusted);
- only fails after 5 attempts with the asset still missing.
Maintenance release.
UI polish:
- Editor top bar decluttered: camera / attach-file / add-tag moved out of
the title bar into a Keep-style bottom action row, so the title and
remaining buttons (favourite, save, overflow) always fit, even on
narrow screens. Title is now "New note" / "Edit note" with ellipsis.
- Search auto-focuses when opened and shows a clear button while typing.
- Long tag lists in the navigation drawer now scroll within the sheet
instead of overflowing the bottom (weight(1f) on the scroll column).
- Add-tag sheet opens with the keyboard already up.
Bug fix:
- Image viewer no longer flashes a false "couldn't decode" error on
every persisted image open (the old LaunchedEffect checked the bitmap
before the async load finished); genuine failures now show
"Couldn't load image" in place of "Loading…".
New flat app icon:
- incido_flat_icon.png replaces the v0.3.3.8 artwork: adaptive
foregrounds (108-432px) + legacy mipmaps (48-192px) regenerated;
ic_launcher_background re-tinted #010435 -> #352999 to match.
Hygiene:
- Unused persistedBytes param dropped from AttachmentStrip; redundant
repoForViewer alias and dead _ignored val removed; fully-qualified
Spacer/Image/Column/Dispatchers references replaced with imports.
versionCode 31->32, versionName "0.3.7.0"->"0.3.7.1",
SettingsViewModel.APP_VERSION bumped in lockstep.
- Deleting a note now soft-deletes it (trashed flag on NoteEntity,
additive schema, auto-migrated); trashed notes are hidden from Home,
Favorites, Untagged, tag views, and ordinary search.
- New Trash drawer entry lists soft-deleted notes; each Trash card's
overflow menu exposes Restore and Delete permanently.
- NoteFilter gains a Trash case; repository gains moveToTrash /
restoreFromTrash / deletePermanently; backups round-trip the
trashed state.
- Version bump (lockstep): versionCode 30->31, versionName
0.3.6.3->0.3.7.0, SettingsViewModel.APP_VERSION, README intro +
changelog, ReleaseNotes.kt 5-most-recent window.
- Development Plan §10: fix the merged 0.3.4.0/0.3.3.8 table row and
backfill the missing 0.3.6.2/0.3.6.3 rows; add the 0.3.7.0 row.
- README changelog: backfill the missing 0.3.6.2 row; promote the
Unreleased Trash row to 0.3.7.0.
- signingConfigs.release now throws GradleException at config time
when keystore/release.jks is missing, printing the exact keytool
command from keystore/README.md instead of letting packageRelease
die later with the cryptic
"SigningConfig release is missing required property storeFile".
- .gitea/workflows/release.yml now mints the dev keystore on the
runner before assembleRelease (previously the signing config
was empty on a fresh runner, so the release APK was never
produced).
- versionCode 29 → 30, versionName "0.3.6.2" → "0.3.6.3";
APP_VERSION in SettingsViewModel bumped in lockstep; README
"Current release" + intro paragraph + Changelog row updated.
Refs: Incido Development Plan §11.
Two emergency-patch UX fixes on the New/Edit screen:
1. Title left-aligned against the back arrow.
NoteEditorScreen used CenterAlignedTopAppBar, but with six
actions on the right (camera, attach, tag, favourite, save, more)
the visually-centred title landed right next to the action cluster.
Swap for Material 3's standard TopAppBar so 'New' / 'Edit' sits
flush right of the back arrow on the left.
2. Colour chooser is now equally spaced between the title bar
and the top of the note. The picker Row had padding(vertical = 4.dp)
(4dp above + 4dp below), but the OutlinedTextField below has an
intrinsic top inset (~16dp) inside its border, so the perceived
gap from the picker to the first line of the note dwarfed the
gap from the title bar's bottom to the picker's top. Remove the
vertical = 4.dp and bracket the Row with two explicit
Spacer(Modifier.height(12.dp)) siblings so the picker sits 12dp
from the title bar AND 12dp from the field's top border.
versionCode 27 → 28
versionName 0.3.6.0 → 0.3.6.1
APP_VERSION 0.3.6.0 → 0.3.6.1
The user reported the drawer's Recent Tags list eventually rendered,
but only after a couple of minutes. Root cause was inside
NoteRepositoryImpl:
1. hashtagUsageSnapshot() called noteBox.get(x.noteId) once per
cross-ref row. Most notes have multiple hashtags, so each note
was fetched many times — O(M) Box.get calls where M is the xref
count.
2. observeHashtagsByRecentUse() called trySend(snapshot()) BEFORE
setting up the ObjectBox subscription, then also inside the
observer. The first emission doubled the work; if the first
trySend ran before the upstream was warm, the data path itself
was slow.
Two surgical fixes inside NoteRepositoryImpl.kt:
- hashtagUsageSnapshot(): batch-load notes by id (one Box.get per
distinct noteId, not per xref) and tags by id (one Box.get per
distinct tagId). Net reads drop from (M + N) to
(distinct noteIds + distinct tagIds) — typically a 5–20×
reduction.
- observeHashtagsByRecentUse(): rely solely on the ObjectBox
observer's first fire (ObjectBox delivers the current query
state immediately on subscribe). Drop the manual pre-subscribe
trySend.
VERSION
- app/build.gradle.kts: versionCode 7 → 8, versionName '0.3.0.2' →
'0.3.0.3'.
- README.md changelog: new 0.3.0.3 row.
- Incido Development Plan.txt §10: new 0.3.0.3 row.
VERIFIED
- ./gradlew assembleDebug assembleRelease both green.
- versionCode=8, versionName='0.3.0.3'.
- No INTERNET permission.
- Release signed (v2 scheme verified).
The placeholder text in AddTagSheet's OutlinedTextField read
'#tag-name', but the field already has a leading '#' icon to
indicate the format — the extra '#' in the placeholder was
redundant. Changed it to 'hashtag-name'.
No data, viewmodel, or storage changes; this is a pure UI string
fix.
VERSION
- app/build.gradle.kts: versionCode 6 → 7, versionName '0.3.0.1' →
'0.3.0.2'.
- README.md changelog: new 0.3.0.2 row.
- Incido Development Plan.txt §10: new 0.3.0.2 row.
VERIFIED
- ./gradlew assembleDebug assembleRelease both green.
- versionCode=7, versionName='0.3.0.2'.
- No INTERNET permission.
- Release signed (v2 scheme verified).
Urgent UI polish patch on top of v0.3.0.0.
EDITOR (NoteEditorScreen.kt)
- Drop the '+ add' chip from the hashtag row. The '#' icon in the
top bar is now the only way to add tags.
- Move the hashtag chip row to the bottom of the editor. The text
field now uses weight(1f) instead of fillMaxSize() so the row stays
visible below it.
- Hide the chip row entirely when the note has no hashtags (no 'No
tags' placeholder).
- Centre the colour picker horizontally. Switched from a left-aligned
LazyRow to a plain Row with Arrangement.spacedBy(12.dp,
Alignment.CenterHorizontally).
LIST CARDS (NoteListScreen.kt)
- Replace the small 10 dp colour circle chip (next to the star) with
a 'dog-ear' colour accent overlaid on the top-right corner of the
card (a 28 dp right-triangle filled with the note's colour).
- Add a hashtag row to each card. Shows up to three tags as a
FlowRow of label-styled text; an '+N' indicator appears when
there are more than three. Hidden when the note has no tags.
- Wrap the Card in a Box so the dog-ear can be aligned to
Alignment.TopEnd.
VERSION + DOCS
- app/build.gradle.kts: versionCode 5 → 6, versionName '0.3.0.0' →
'0.3.0.1'. The MAJOR.MINOR.MAINTENANCE.EMERGENCY scheme validator
remains in place.
- README.md changelog: new 0.3.0.1 row.
- Incido Development Plan.txt §10: new 0.3.0.1 row.
VERIFIED
- ./gradlew assembleDebug assembleRelease both green.
- Debug 25.7 MB, release 19.8 MB.
- versionCode=6, versionName='0.3.0.1'.
- No INTERNET permission in either APK.
- Release signed (v2 scheme).
v0.3.0.0 bundles four user-facing features, the plan-compliance polish
that was deferred from v0.2, and a permanent change to how we name
releases going forward.
VERSION SCHEME (app/build.gradle.kts)
- versionName = '0.3.0.0' (MAJOR.MINOR.MAINTENANCE.EMERGENCY)
- versionCode = 5
- New gradle taskGraph validator fails the build if versionName
doesn't match ^\d+\.\d+\.\d+\.\d+$ — we can't accidentally
regress the scheme.
- History re-keyed across README, Plan §10, CONTRIBUTING.md.
HASHTAGS
- value class Hashtag (domain/model) with normalise/parseOrNull
helpers; pattern: ^[a-z0-9][a-z0-9._-]{0,30}$
- data class HashtagUsage (name, noteCount, lastUsedAt)
- sealed class NoteFilter { Home, Favorites, Untagged, ByTag(name) }
- Note gains hashtags: List<String> (sorted ascending)
- Repository:
- new entities HashtagEntity (@Index on name) and
NoteHashtagCrossRef (many-to-many junction)
- new methods: observeFavorites / observeUntagged /
observeNotesForHashtag / observeHashtagsByRecentUse /
observeAllHashtags / searchHashtags / addHashtag / removeHashtag
- search() now matches content OR hashtag-name (case-insensitive)
- ObjectBox queries use explicit StringOrder + type annotations
(kapt's stubs are finicky around Property<String> overloads)
UI
- CenterAlignedTopAppBar on both list and editor screens
- List:
- Hamburger top-left opens a ModalNavigationDrawer (Home /
Favorites / Untagged / divider / scrollable Recent tags)
- Drawer selection drives a NoteFilter state held at root
- Search bar visible only when filter == Home
- NoteCard redesign — 14 dp vertical gradient stripe +
tinted surface (12 % colour blend) + 10 dp corner chip
- Empty-state copy is filter-aware
- Editor:
- Persistent hashtag chip row above the text field
- Tag # icon in the top bar + '+ add' chip opens a ModalBottomSheet
- Autocomplete suggestions live from repository.searchHashtags
- '+ Create name' button when the typed value is valid + new
- Snackbar 'Maximum 5 tags reached.' when the cap is hit
- Reconciled on save via addHashtag / removeHashtag diff
DOCS
- README v0.3.0.0 section + re-keyed changelog
- Development Plan §10 history re-keyed (0.1.0.0 / 0.1.1.0 /
0.2.0.0 / 0.2.0.1 / 0.3.0.0)
- CONTRIBUTING.md release-process note updated for the new scheme
VERIFIED
- ./gradlew assembleDebug assembleRelease both green
- Debug 25.7 MB, release 19.8 MB (v2-signed)
- versionCode=5, versionName='0.3.0.0'
- No INTERNET permission
- Validator regression: setting versionName='0.3' causes
assembleDebug to fail with the new scheme error message
In v0.2 the search-active flag lived on a separate StateFlow that
the composable never observed: 'if (state.isSearchActive)' in
NoteListScreen was always false, so tapping the search icon toggled
the internal flag but never updated the UI.
Refactor NoteListViewModel.uiState to use combine() over (notes,
isSearchActive, rawQuery) so the flag and the current query are
folded into the same emitted NoteListUiState. The composable already
reads state.isSearchActive, so no changes are needed there.
Result: tapping the search icon shows the search field; typing filters
the list via the existing ObjectBox 'contains' query; tapping again
closes.