Skip to content

chore: add Flathub verification file - #199

Merged
wavekat-eason merged 1 commit into
mainfrom
chore/flathub-verified-apps
Sep 16, 2026
Merged

wavekat-eason merged 1 commit into
mainfrom
chore/flathub-verified-apps

Conversation

@wavekat-eason

@wavekat-eason wavekat-eason commented Sep 16, 2026 •

Copy link
Copy Markdown
Contributor

Adds an empty public/.well-known/org.flathub.VerifiedApps.txt, served at https://wavekat.com/.well-known/org.flathub.VerifiedApps.txt.

The Flathub reviewer on the com.wavekat.Voice submission asked for this file to confirm we control wavekat.com, the domain behind the app ID. The filename is fixed by Flathub; it isn't named after the app.

  • Now: the file is empty, as the reviewer asked.
  • Later: after the app is published, the Flathub developer portal gives us a verification token. That token goes into this file as one line (one line per app, if we ever ship more than one).

Verified: astro build copies the file (0 bytes) to dist/.well-known/org.flathub.VerifiedApps.txt. Cloudflare Pages serves the build output as-is. After deploy: curl -I https://wavekat.com/.well-known/org.flathub.VerifiedApps.txt should return 200.

Flathub reviewers confirm that the developer controls the domain behind the
app ID (com.wavekat.Voice -> wavekat.com) by fetching
https://wavekat.com/.well-known/org.flathub.VerifiedApps.txt. The filename
is fixed; it stays empty until the Flathub developer portal issues a token
after the app is published, which then goes in as one line.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01A29r3jHUjhaZerP5ahYU8h
@github-actions

Copy link
Copy Markdown
Contributor

@wavekat-eason
wavekat-eason merged commit dcae9d5 into main Sep 16, 2026
2 checks passed
@wavekat-eason
wavekat-eason deleted the chore/flathub-verified-apps branch September 16, 2026 11:33
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