Skip to content

native-packages 0.12.0

Latest

Choose a tag to compare

@crmne crmne released this 03 Nov 23:27
5150046

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 flatpak to a Linux target's formats and a top-level flatpak section (app ID, runtime, command, finish_args, optional metainfo). The package's contents become a single-file .flatpak through flatpak build-finish, build-export and build-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 snap to formats and a top-level snap section (base, confinement, grade, apps with their plugs and desktop entries, icon). native-packages writes meta/snap.yaml and packs the snap as snap pack does, with no snapcraft or LXD, and the same inputs give the same file. publish --to snapcraft uploads it to the channels in snap.store.channels with SNAPCRAFT_STORE_CREDENTIALS. By @crmne.
  • A signed APT repository. publish --to apt writes dists/ and pool/ into a directory you serve, such as a GitHub Pages checkout, signs InRelease and Release.gpg, keeps the newest apt.keep versions, and writes the public key and a .sources file for your install instructions. No Debian tools are needed. By @crmne.
  • A signed DNF repository. publish --to dnf does the same for RPMs with createrepo_c: gzip metadata that older dnf and zypper read, a signed repomd.xml, the public key and a .repo file. By @crmne.
  • A signed Flatpak repository. With flatpak.repository, publish --to flatpak imports your bundles into an OSTree repository with signed commits and writes .flatpakrepo and .flatpakref files, so flatpak install and flatpak update work from your own site. By @crmne.
apt:
  directory: site/apt
  url: https://example.com/apt
  signing_key: 0123456789ABCDEF0123456789ABCDEF01234567
  keep: 3

Signing 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 repositories can 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-bundle stamps 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