Nightlies get their own Flatpak repo, served from GitHub Pages under the
moe.sable.client.Nightly application ID so they install alongside the stable
Flathub build.
Flathub cannot host this: its requirements exclude nightly releases and
software needing daily updates from both the stable and beta repos, duplicate
submissions of the same app are not accepted, and flathub-beta takes no new
submissions.
The payload stays on the nightly release as extra-data, keeping each OSTree
commit small enough for Pages. The repo is rebuilt from scratch every night
because an older commit's extra-data URL points at a release asset that has
since been pruned, so the asset cleanup now keeps the three newest Linux
tarballs.
Publishing needs Pages enabled with the GitHub Actions source, plus
FLATPAK_GPG_KEY and FLATPAK_GPG_KEY_ID; the job skips with a notice until
they exist.
Add nightly iOS build job to tauri-build.yml using tauri ios build --no-sign,
upload the unsigned IPA + altstore-source.json to the release, and document
the install flow in the README.
The project has moved from github.com/7w1/sable to
github.com/SableClient/Sable. Update all non-historical
references throughout the codebase:
- README.md: github.com and ghcr.io links
- CONTRIBUTING.md: issues link
- .github/ISSUE_TEMPLATE/bug_report.yml: existing-issues search link
- knope.toml: owner/repo for release automation
- src/app/features/settings/about/About.tsx: repo + pulls links
- src/app/pages/auth/AuthFooter.tsx: repo link
- src/app/pages/client/WelcomePage.tsx: source + changelog links
Historical PR/issue links in CHANGELOG.md and issue-specific deep-links
(e.g. github.com/7w1/sable/issues/146) are intentionally left pointing
to the old repo where those items live.