Repository navigation
0.12.0 reaches more Linux desktops. It builds Flatpak bundles and snaps from the same files as your DEB and RPM, uploads snaps to the Snap Store, and publishes your packages in signed APT, DNF and Flatpak repositories that you serve from any static site, so people install your app with their package manager and get updates with the rest of their system.
New
- Flatpak bundles. Add
flatpakto a Linux target'sformatsand a top-levelflatpaksection (app ID, runtime, command,finish_args, optional metainfo). The package's contents become a single-file.flatpakthroughflatpak build-finish,build-exportandbuild-bundle, with no flatpak-builder, SDK or network. The desktop entry and icon are renamed after the app ID. native-packages never writes or submits Flathub manifests, which Flathub does not accept from AI-assisted tooling. By @crmne. - Snaps, and the Snap Store. Add
snaptoformatsand a top-levelsnapsection (base, confinement, grade, apps with their plugs and desktop entries, icon). native-packages writesmeta/snap.yamland packs the snap assnap packdoes, with no snapcraft or LXD, and the same inputs give the same file.publish --to snapcraftuploads it to the channels insnap.store.channelswithSNAPCRAFT_STORE_CREDENTIALS. By @crmne. - A signed APT repository.
publish --to aptwritesdists/andpool/into a directory you serve, such as a GitHub Pages checkout, signsInReleaseandRelease.gpg, keeps the newestapt.keepversions, and writes the public key and a.sourcesfile for your install instructions. No Debian tools are needed. By @crmne. - A signed DNF repository.
publish --to dnfdoes the same for RPMs withcreaterepo_c: gzip metadata that older dnf and zypper read, a signedrepomd.xml, the public key and a.repofile. By @crmne. - A signed Flatpak repository. With
flatpak.repository,publish --to flatpakimports your bundles into an OSTree repository with signed commits and writes.flatpakrepoand.flatpakreffiles, soflatpak installandflatpak updatework from your own site. By @crmne.
apt:
directory: site/apt
url: https://example.com/apt
signing_key: 0123456789ABCDEF0123456789ABCDEF01234567
keep: 3Signing keys come from NATIVE_PACKAGES_GPG_KEY or your own GnuPG, and every signature is checked against the configured fingerprint before anything is written.
Changed
- Entries under
repositoriescan no longer use the built-in destination names (apt,dnf,flatpak,snapcraft). Rename any such entry.
Known limitations
- Snaps get no snapcraft extensions, so a dynamically linked desktop app must ship the libraries it needs in the package.
- The Flatpak repository serves each app's newest version only.
- Flatpak bundles are not byte-identical between builds, because
flatpak build-bundlestamps the time; the OSTree commit inside them is reproducible. - The repositories are written to a directory. Committing and serving it is your release workflow's job.
Thanks
Thanks to ZapFast, Spotifast, Solco and Chat with Work Desktop, which needed these channels.
Full changelog: v0.11.0...v0.12.0