Skip to content

ci(stable): dedicated FIYORA signing + artifact-only Stable candidate - #17

Merged
Noirero merged 2 commits into
mainfrom
ci/fiyora-stable-signing-candidate-20261113
Nov 13, 2026
Merged

Noirero merged 2 commits into
mainfrom
ci/fiyora-stable-signing-candidate-20261113

Conversation

@Noirero

@Noirero Noirero commented Nov 13, 2026

Copy link
Copy Markdown
Owner

Owner goal

Prepare independent Android signing for FIYORA Stable (com.noirero.fiyora) while keeping apk-build / NFile Original untouched. Add a signed validation APK workflow with no GitHub Release. Owner will manually enter the four secrets later.

Change scope (no app code)

  • .github/workflows/main.yml: change Stable public release signing secrets from shared NFile KEYSTORE_* names to FIYORA_STABLE_* names and check the expected FIYORA public signing certificate SHA-256 after signing.
  • .github/workflows/stable-candidate.yml (new): manually dispatched from main, checked out at github.sha, runs flutter test, builds signed split-ABI Stable APKs with obfuscation symbols, verifies package com.noirero.fiyora, signature/fingerprint, and uploads Actions Artifacts only. contents:read; absolutely no release action.
  • docs/FIYORA_STABLE_SIGNING.md and docs/RELEASE_WORKFLOWS.md: names, manual UI setup, recovery, explicit boundary between public release and candidate.
  • The expected public cert SHA-256 is dfcb5468d7e280befbe5ffdb0b4fe04cc0ced10810abb5c5fdc7a4dd48d02935. This fingerprint is not a secret; it binds the workflow to the private signing identity that the owner will back up separately.

Required GitHub repository secrets (owner enters privately)

FIYORA_STABLE_KEYSTORE_BASE64
FIYORA_STABLE_KEY_ALIAS
FIYORA_STABLE_KEY_PASSWORD
FIYORA_STABLE_STORE_PASSWORD

Do NOT populate old NFile KEYSTORE_* secrets with FIYORA key. FIYORA Beta stays on MRARE_*; NFile Original stays on KEYSTORE_*.

Safety and validation

  • No keystore, passwords, base64, or private key committed; code and docs contain only public fingerprint.
  • No application source, Gradle applicationId or Beta/Original workflow modifications.
  • The PR CI validates YAML integration and normal Flutter test/Android build without production secrets. Successful signed candidate build is not possible until owner sets secrets and manually runs it on main.
  • Do not dispatch public Fiyora Stable (manual) until explicit owner approval.
  • Production APK signing certificate updates are destructive for upgrade continuity: preserve this key and its password securely.

DRAFT; no merge, manual run or public release yet.

@Noirero
Noirero marked this pull request as ready for review November 13, 2026 02:43
@Noirero
Noirero merged commit 73c5e67 into main Nov 13, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant