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.
this nix flake is heavily based off of prior work i have done in one of my
repos. it comes with the following features:
- building sable: `nix build .#sable` or just `nix build`. creates a `result/`
dir with the built application.
- devshell: nix users now no longer need to do download and install all the
dependencies for sable by themselves. the devshell comes with all the
dependencies needed to develop sable
- checks: `nix flake check` is configured to perform all checks listed in
`CONTRIBUTING.md` (fmt:check, lint, typecheck, knip, test:run)
- formatting: `nix fmt` runs all the formatters pnpm would also call, but
provides a more familiar interface for nix users.
- pre-commit checks: nix users can benefit from having their changes checked for
before the commit goes through. yay :3
`.vscode/settings.json` was updated to include hints for VS Code users using the
"nix env selector" extension to auto-detect the nix dev environment, if you have
nix installed.
I had to change `oxfmt.config.ts` just a tiny bit to make it work with the nix
stuff, because `node_modules` does not exist inside the nix build sandbox. `pnpm
fmt` successfully runs, so nothing should have broken.
`flake-lock-fix.yml` is a small workflow heavily based on
<https://docs.determinate.systems/guides/fix-hashes/>, which triggers on pushes
to `dev` which change `pnpm-lock.yaml`. The workflow uses `determinate-nixd` to
fix hashes in the `flake.nix`, then pushes the changes to `dev` automatically.