Commit Graph
5 Commits
Author SHA1 Message Date
ayushyaandClaude Sonnet 5 722b66f7b1 Fix release signing and unify "+" upload with the share-intent path
Build APK / build (push) Successful in 5m21s
- Release builds now sign with a dedicated keystore (local
  android/key.properties or CI secrets, both gitignored) instead of each
  machine's own debug key, so a downloaded release APK can actually
  update a previous install instead of failing with "App not installed"
  (mismatched signature).
- The Files tab's "+" -> "Upload File" now goes through the same
  ShareUploadView destination picker and background foreground-service
  upload as receiving a file via Android's "Share to..." sheet, instead
  of a separate blocking in-app-only upload path. Removed the
  now-unused ServerProvider/NextcloudService.uploadFileFromPath.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-18 17:17:46 -04:00
ayushyaandClaude Sonnet 5 da22030d43 CI: build on RC* tags only, name the APK, and publish to a Gitea release
Build APK / build (push) Successful in 5m22s
- Trigger on pushing a tag matching RC* instead of every push to main
  - tag the commit you want built: git tag RC1 && git push origin RC1
- Rename the built APK to Noo-<version>.apk (from pubspec.yaml's version)
- Replace the plain artifact upload with akkuman/gitea-release-action,
  which creates/updates a Gitea release named after the triggering tag
  and attaches the versioned APK to it - the GitHub-flavored
  actions/upload-artifact and release actions don't reliably work
  against Gitea's own API, this one talks to Gitea natively

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-16 15:17:49 -04:00
ayushyaandClaude Sonnet 5 ab427c0b9f Fix CI: downgrade upload-artifact to v3 for Gitea Actions compatibility
Build APK / build (push) Successful in 5m42s
actions/upload-artifact@v4 speaks a newer artifact backend protocol
that Gitea Actions doesn't implement yet, failing with
GHESNotSupportedError even though this isn't GHES. v3 uses the older
protocol Gitea does support. The build itself (flutter analyze +
flutter build apk --release) already succeeded before this step.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-16 15:06:53 -04:00
ayushyaandClaude Sonnet 5 dca0daf41f Fix CI: pin setup-android packages to skip removed 'tools' package
Build APK / build (push) Failing after 5m22s
Google removed the legacy standalone "tools" package from the Android
SDK repository (~Sep 2026); android-actions/setup-android@v3's default
packages list ("tools platform-tools") now fails its own sdkmanager
call for everyone. Pin packages: platform-tools instead - that's all
this step needs, flutter build fetches whatever platform/build-tools
versions it actually needs on its own.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-16 14:57:38 -04:00
ayushyaandClaude Sonnet 5 b5df0ee77a Add Gitea Actions workflow to build a release APK on push to main
Build APK / build (push) Failing after 3m28s
Checks out, sets up JDK 17 + Flutter (stable) + Android SDK, runs
flutter analyze, then builds and uploads a release APK artifact.
Requires a registered Gitea Actions runner - see the setup notes
given alongside this commit.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-16 14:39:07 -04:00