Sources → Codeberg. The links.gitea key becomes links.codeberg, with Codeberg's mark and "Source on Codeberg" on the button. The release lookup follows: Forgejo serves Gitea's /api/v1, so the version badge keeps working, and it now falls back to the newest pre-release when releases/latest finds nothing — a pre-1.0 app publishes nothing else. Agendula was showing a stale v0.2.0 from Gitea and now shows v0.4.0; Calendula shows v2.20.1 from Codeberg.
Calendula on Google Play. New links.play, rendered as a tonal button next to the filled F-Droid one (adds .btn--tonal, secondary-container tokens, light and dark). Verified the listing resolves: "Calendula: Calendar".
Descriptions. Checked against each repo rather than edited from memory:
Agendula described the app it stopped being — "pure front-end over the OpenTasks provider… no own database". It now carries its own VTODO store, with an external provider as a choice; the entry covers the store, coexistence with OpenTasks, verbatim round-tripping, .ics export, the two community translations, and its own CalDAV sync as in progress rather than shipped.
Calendula — "German and English UI" was fifteen community translations ago.
floret-kit — modules have grown past core-time to identity, components, core-reminders, core-locale and core-crash.
Both apps now link their published privacy policy from the project body.
Forge roles. Footer link and the /uses infrastructure list now say it plainly: Codeberg for source, issues and releases; self-hosted Gitea for signing, the F-Droid repo, release pipelines and smaller experiments.
No Play button for Agendula — it is on neither Play nor F-Droid yet (both checked, both 404).
**Sources → Codeberg.** The `links.gitea` key becomes `links.codeberg`, with Codeberg's mark and "Source on Codeberg" on the button. The release lookup follows: Forgejo serves Gitea's `/api/v1`, so the version badge keeps working, and it now falls back to the newest pre-release when `releases/latest` finds nothing — a pre-1.0 app publishes nothing else. Agendula was showing a stale **v0.2.0** from Gitea and now shows **v0.4.0**; Calendula shows **v2.20.1** from Codeberg.
**Calendula on Google Play.** New `links.play`, rendered as a tonal button next to the filled F-Droid one (adds `.btn--tonal`, secondary-container tokens, light and dark). Verified the listing resolves: "Calendula: Calendar".
**Descriptions.** Checked against each repo rather than edited from memory:
- *Agendula* described the app it stopped being — "pure front-end over the OpenTasks provider… no own database". It now carries its own `VTODO` store, with an external provider as a choice; the entry covers the store, coexistence with OpenTasks, verbatim round-tripping, `.ics` export, the two community translations, and its own CalDAV sync as in progress rather than shipped.
- *Calendula* — "German and English UI" was fifteen community translations ago.
- *floret-kit* — modules have grown past `core-time` to identity, components, core-reminders, core-locale and core-crash.
- Both apps now link their published privacy policy from the project body.
**Forge roles.** Footer link and the `/uses` infrastructure list now say it plainly: Codeberg for source, issues and releases; self-hosted Gitea for signing, the F-Droid repo, release pipelines and smaller experiments.
No Play button for Agendula — it is on neither Play nor F-Droid yet (both checked, both 404).
Codeberg is where the apps live now, so the source link, its icon and the
release lookup follow. Forgejo serves Gitea's /api/v1, so the version badge
keeps working — with a fallback to the newest pre-release, since a pre-1.0
app publishes nothing else (Agendula showed a stale v0.2.0 before).
Calendula is on Google Play as well as F-Droid; adds a tonal button for it,
and its fifteen community translations replace "German and English".
Agendula's entry described the app it stopped being: it now carries its own
VTODO store, with an external provider as a choice rather than a requirement,
plus export and its own CalDAV sync in progress. floret-kit's modules have
grown past core-time. Footer forge link and the /uses infrastructure list
separate the two roles: Codeberg for source, self-hosted Gitea for builds.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Sources → Codeberg. The
links.giteakey becomeslinks.codeberg, with Codeberg's mark and "Source on Codeberg" on the button. The release lookup follows: Forgejo serves Gitea's/api/v1, so the version badge keeps working, and it now falls back to the newest pre-release whenreleases/latestfinds nothing — a pre-1.0 app publishes nothing else. Agendula was showing a stale v0.2.0 from Gitea and now shows v0.4.0; Calendula shows v2.20.1 from Codeberg.Calendula on Google Play. New
links.play, rendered as a tonal button next to the filled F-Droid one (adds.btn--tonal, secondary-container tokens, light and dark). Verified the listing resolves: "Calendula: Calendar".Descriptions. Checked against each repo rather than edited from memory:
VTODOstore, with an external provider as a choice; the entry covers the store, coexistence with OpenTasks, verbatim round-tripping,.icsexport, the two community translations, and its own CalDAV sync as in progress rather than shipped.core-timeto identity, components, core-reminders, core-locale and core-crash.Forge roles. Footer link and the
/usesinfrastructure list now say it plainly: Codeberg for source, issues and releases; self-hosted Gitea for signing, the F-Droid repo, release pipelines and smaller experiments.No Play button for Agendula — it is on neither Play nor F-Droid yet (both checked, both 404).