Category
New Feature
Target Platform
Android
Feature Description
Currently, the app can only be built manually and sideloaded. As first step, I want to enable a F-Droid release.
Proposed Solution / Mockup
Necessary steps:
- Re-introduce the versioning concept: I want the application to follow calver.
- Update cd.yml to generate a version number with YY.0W.x format
- This resembles the last 2 digits of the current year, followed by the zero-padded week number, followed by an incrementing component to indicate hotfixes
- F-Droid requires a semver format
- Sync versions in
package.json, Cargo.toml and tauri-conf.json. This can be done as part of the release workflow.
- Update cd.yml to build an unsigned APK and tag the code with the version number. F-Droid handles signing and fetches version info via git tags.
- Add a manual dispatch workflow to verify F-Droid build compatiblity.
- Review dependencies for non-free licenses. Those are considered an anti-feature.
- Create a CHANGELOG.md
- Create a merge request to F-Droid for manual review
Problem Statement (Optional)
No response
Alternatives Considered (Optional)
No response
Additional Context (Optional)
Category
New Feature
Target Platform
Android
Feature Description
Currently, the app can only be built manually and sideloaded. As first step, I want to enable a F-Droid release.
Proposed Solution / Mockup
Necessary steps:
package.json,Cargo.tomlandtauri-conf.json. This can be done as part of the release workflow.Problem Statement (Optional)
No response
Alternatives Considered (Optional)
No response
Additional Context (Optional)