makiolaj/agendula
1
0
Fork 0
Code Issues Pull Requests Actions Releases 6 Activity
Files
e639e250b77d9e5b68cde58dc909b987264f12d6
agendula/CHANGELOG.md
Jean-Luc Makiola 217d5d7afd
Some checks failed
Release — F-Droid repo + Gitea/Codeberg release / release (push) Has been skipped
Details
Release — F-Droid repo + Gitea/Codeberg release / detect (push) Successful in 7s
Details
Renovate / renovate (push) Failing after 43s
Details
Move the canonical forge to Codeberg, and add Renovate + Weblate (#2) 
Makes Codeberg canonical for git, issues, PRs, tags and releases. The self-hosted Gitea instance stays build infrastructure: signing key, F-Droid publishing, release pipeline. Ports the setup Calendula already runs on, adapted where Agendula genuinely differs.

**This PR is its own test.** It is the first PR opened on Codeberg, so a green `CI` check proves the new runner works *and* that the submodule resolves from its new home.

### 1 · Workflows split by directory

Forgejo's lookup is first-match-wins across `.forgejo/` → `.gitea/` → `.github/`, and Gitea cannot see `.forgejo/` at all. So each forge sees exactly one set, with no duplicated files and no expression to keep in sync:

| Directory | Runs on | Contains | Secrets |
| --- | --- | --- | --- |
| `.forgejo/workflows/` | Codeberg | `ci.yaml`, `translations.yaml` | **none** |
| `.gitea/workflows/` | Gitea | `release.yaml`, `renovate.yml` | all of them |

The line is drawn at **secrets, not CI-vs-release** — that is what makes fork PRs safe. Renovate deliberately does *not* move despite opening PRs here; it keeps running where its token already lives and merely talks to Codeberg's API.

CI also gains three fixes: an explicit `SKIP_RE` skip-list that names the build-relevant files in the log, base-ref normalisation, and a fully-qualified `android-actions/setup-android` — Codeberg resolves bare `uses:` refs against `data.forgejo.org`, which does not carry that action.

### 2 · Three release-pipeline safety changes

- `detect` and the Renovate job get an explicit `repository_owner` guard. The directory split only holds while `.forgejo/` is non-empty; empty it and Codeberg would fall back to `.gitea/` and start running these on the contributor-facing runner, without secrets.
- `detect` now reads tags from **Codeberg**, not from the Gitea instance it runs on. Push mirroring is `git push --mirror`, so a tag minted on Gitea is deleted by the next sync until the Codeberg tag push propagates back — asking Gitea inside that window reports "no tag" for an already-shipped release and would cut it twice. It also now fails on any status other than 200/404 rather than reading a transient error as "no tag": a failed job is recoverable, a duplicate release is not.
- **The Codeberg publish step pushes the tag itself** instead of waiting for it to arrive by mirror. That wait was correct while Gitea mirrored *to* Codeberg; under Codeberg-canonical the mirror runs the other way and it would never resolve. Attaching the release to an already-pushed ref (no `target_commitish`) is what avoids the empty-bodied 500s, and the create call retries with backoff because Codeberg 500s on a tag it has only just received. The step stays **fail-loud**, not `continue-on-error` — it reported green through 0.2.1–0.3.2 while never once publishing, and that must not be possible again.

### 3 · Renovate

`renovate.json5` plus a Gitea-side job targeting Codeberg's API. `managerFilePatterns` covers **both** workflow directories, so the pinned Renovate image tag and the action versions in either file keep getting bumped.

Needs two new Gitea secrets: `RENOVATE_TOKEN` (Codeberg bot, repo read/write + PR scope) and `GITHUB_COM_TOKEN` (read-only github.com PAT, for changelog lookups).

### 4 · Weblate

A parity check (`scripts/check_translations.py`) runs on every PR without a path filter, so the required `Translations` status is always reported. Partial translations are expected, so `MissingTranslation` and `MissingQuantity` become informational — `ExtraTranslation` stays fatal. Agendula had no `lint` block at all, so the first locale to land would otherwise have failed the build.

**Settings → App language** now opens a picker carrying a "Help translate" header. That is why it drops floret-kit's `LanguagePickerRow` for a local row: the shared recipe has no `header` slot, and the framing is app-specific rather than a family primitive.

### 5 · Links repointed

In-app Source / License / report-issue URLs, F-Droid metadata, README (now with a Codeberg CI badge), and the docs.

`floret-kit` follows suit — `.gitmodules` points at `codeberg.org/jlmakiola/floret-kit`, so a clone no longer needs to reach the personal Gitea instance to resolve it. The Gitea copy is **kept**: every existing tag records the old submodule URL, so rebuilds of past releases still resolve.

### 6 · Housekeeping

Drops `release-notes.md` — a release-pipeline scratch file that got committed — and gitignores the five others the release job writes into the workspace.

### Not in this PR

The Codeberg → Gitea push mirror, the Weblate component, and the Codeberg bot account (all browser-side). Until the mirror is flipped, merging this does **not** reach the Gitea runner.

Co-authored-by: Jean-Luc Makiola <business@jeanlucmakiola.de>
Reviewed-on: https://codeberg.org/jlmakiola/agendula/pulls/2
2026-08-01 16:34:20 +02:00

5.7 KiB
Raw Blame History

Changelog

All notable changes to this project are documented here. The format follows Keep a Changelog; the versionName committed in app/build.gradle.kts is the source of truth for a release (see docs/RELEASING.md), and the vX.Y.Z tag is minted by the pipeline.

[Unreleased]

Added

  • Agendula can now be translated. Pick or request a language on Weblate and translate in the browser — the link sits at the top of the language picker in Settings → App language. Partial translations are fine; anything untranslated falls back to English.

Changed

  • Agendula's home is now Codeberg (jlmakiola/agendula) — that's where the source, issues, pull requests and releases live. The Source and License links in Settings, the issue-reporting link and the F-Droid metadata all point there now. The self-hosted Gitea instance stays as build infrastructure.

[0.3.2] - 2026-07-20

Fixed

  • Releases reach the Codeberg download channel again. 0.3.1 published to F-Droid but never appeared on Codeberg, so if you install from there — or through Obtainium — this is the release that finally carries 0.3.0's launch-crash fix. The app itself is unchanged from 0.3.1.

[0.3.1] - 2026-07-20

Fixed

  • Agendula no longer crashes on launch. Every 0.3.0 install was affected: the release build stripped a constructor that the background-work scheduler needs to open its database, and that happens before the app draws anything.

[0.3.0] - 2026-07-19

Added

  • Reminders: Agendula now delivers your due reminders itself. A one-time setup step explains this and asks for notification access, and a master switch in Settings turns the whole thing off again.
  • A Settings screen, from the gear on the overview: appearance and theme, which fields the task form shows, your default list, and reminder defaults.
  • The overview leads with Today — a progress ring showing how much of today you've finished — followed by a live preview of what's coming up next.
  • Search across every task, open or completed, from the top bar.
  • A proper app icon.

Changed

  • A tidier top bar: no app title, with search and settings pinned to the right.

[0.2.2] - 2026-07-19

Fixed

  • Release automation now reliably mirrors each release to the Codeberg mirror (signed APK + SHA-256 checksum). The 0.2.1 attempt failed when the release tag had already been synced to Codeberg.

[0.2.1] - 2026-07-19

Added

  • Releases are now also published to the Codeberg mirror as a direct download: each release carries the signed APK plus a SHA-256 checksum, for users who don't use F-Droid.

[0.2.0] - 2026-06-27

Added

  • M2 Material 3 Expressive UI — the app is fully navigable now: the provider/permission onboarding gate, the lists overview (smart lists + user lists grouped by account), and the task list (swipe-to-complete / -delete, inline add, smart-list section headers), detail, and create/edit screens, all wired to the M1 ViewModels.
  • M3 detail/edit polish: a "Progress" slider (percent-complete, 5% detents, written to Tasks.PERCENT_COMPLETE) and conflict-safe saves — updateTask re-checks the provider's last_modified against the value captured when the form loaded and surfaces an overwrite-or-cancel prompt instead of clobbering an external change (e.g. a DAVx5 sync).
  • M4 subtasks (UI): reparent — a full-width, searchable "Parent task" sheet on the edit form, with candidates grouped by due-date section, files a task under any active top-level task in its list (or "None" to promote it); switching list clears the now-invalid parent. Tapping a subtask in the detail screen opens its own detail, which shows a "Part of …" parent card. On the task list a parent has a dedicated expand button that reveals its children as a nested grouped run, ending with an inline "add a subtask" row (an opt-out toggle is planned for the M6 settings screen).
  • Priority is coloured by level (green / amber / red pastels) on the list, detail, and edit screens.

Fixed

  • Overview open-counts now count top-level tasks only, so subtasks — and especially open subtasks under a completed parent — no longer inflate a list's "N open" or the smart-list counts.
  • Swipe-to-delete now reveals its red background + icon as you drag (tracking the live direction, not just the settled target), and a floating "Deleted · Undo" chip defers the actual delete so it can be restored.

[0.1.0] - 2026-06-18

Added

  • M1 data layer + logic ("backoffice"): the full non-visual stack over the OpenTasks TaskContract provider (authority resolved at runtime — org.tasks.opentasks for tasks.org, org.dmfs.tasks for OpenTasks).
    • Vendored TaskContract subset, ProviderResolver, ColumnReader, mappers, AndroidTasksDataSource (Instances query + ContentObserver), and TasksRepository exposing live Flows of lists/tasks/detail.
    • Domain models, smart-list filtering (Today/Upcoming/Overdue/No-date/All/ Completed), sorting, form validation, sub-tasks via parent_id.
    • Self-scheduled due-reminder engine (AlarmManager + boot/provider-change re-sync), notifications, DataStore prefs.
    • Render-only ViewModels + UiState for every screen (lists, task list, detail, edit, settings, permission) so the UI is build-only.
    • 24 JVM unit tests (mappers, filtering, sorting, form, value mapping, day windows). RootScreen is a functional scaffold over the real data, to be replaced screen-by-screen with the Material 3 Expressive design.
  • M0 skeleton: project scaffolding copied from Calendula (Gradle, version catalog, Hilt, Material 3 Expressive theme, Gitea CI/release workflows), reseeded to a warm-mauve palette. Builds and shows a themed placeholder.
View Git Blame Copy Permalink