Carmine Paolino
16a9dde2ca
Packages no longer install a fastpotify command or declare that they replace, provide or conflict with the old packages. Releases no longer carry the 0.9.1 bridge files, the release script only checks and sums Spotifast downloads, and the Flatpak, Homebrew, macOS and Windows recipes lose their old-identity branches and clean-ups. Packaging CI tests the v0.11.2 release instead of installing the 0.8.0 package first. The Rename page and the notes pointing to it are gone. Updates begun by 0.10.2 or earlier on Windows relaunch fastpotify.exe, which the installer no longer provides; such an install updates, but needs starting by hand once.
8.6 KiB
Packaging
native-packages.yaml is the packaging configuration:
it pins the shared CLI and nFPM versions and declares Linux amd64/arm64 inputs,
DEB/RPM/AppImage contents, dependencies, recipe templates and downstream repositories.
Application assets and native recipes stay in packaging/.
Public AUR, Homebrew, DEB/RPM and release download names use Spotifast, and
Linux packages install spotifast as the only executable.
Linux builds provide spotifast.desktop and spotifast.svg, matching the
native window and MPRIS desktop-entry ID. Flatpak installs those assets under
its full application ID and sets the window class to match.
python3 packaging/test-launchers.py exercises the actual AUR and Flatpak
installation commands with a release payload, using Ruby to read YAML.
Linux packages also install the optional Omarchy template and hook under
share/spotifast/omarchy in their installation prefix. The normal application
launch registers missing per-user files and prepares the current palette on an
Omarchy desktop, without changing existing files or the selected theme. Setup
runs in the background; package-manager scripts do not write into user homes.
DEB/RPM packages take these small assets from the checked-out configuration,
so package validation can still use the pinned older binary fixture. AUR and
portable Linux release archives carry the assets with their source/binary
payloads. Source and binary AUR recipes also accept older releases that predate
the integration; the git recipe requires the current files. Nix installs the
Linux desktop assets beside its binaries and packages the signed macOS
Spotifast.app bundle in the same derivation. Flatpak does not install host
desktop hooks.
gem install native-packages --version 0.8.1
native-packages validate
native-packages doctor --target linux-amd64 --target linux-arm64
native-packages build --release v1.2.3 --target linux-amd64 --target linux-arm64
Replace v1.2.3 with an existing stable application release. Local use also
requires nFPM 2.47.0, bsdtar, readelf and, for the AppImage,
mksquashfs (squashfs-tools); AUR generation needs makepkg
or Docker. CI installs its tooling. To package local release archives, put
the selected target inputs and recipe assets under dist/, then run
native-packages build --version 1.2.3 --target linux-amd64 --target linux-arm64.
Outputs go to dist/packages/1.2.3; use --output for a fresh destination when rebuilding.
Before tagging, commit written notes at packaging/release-notes/vVERSION.md.
CI requires notes for the current Cargo version, and the release workflow
publishes that file immediately instead of a generated PR-only summary.
Verify the notes and their download links after the artifacts are published.
Stable tags run the existing native build jobs first. After binaries and
checksums.txt are published, the shared workflow verifies their hashes,
builds the configured packages, and attaches them to the GitHub release.
Configured recipes are attached as an archive. Package checksums are separate
from the original binary checksums. PR validation never publishes.
The Linux release runners are pinned to Ubuntu 24.04 (glibc 2.39). The native
packages target Ubuntu 24.04 / Debian 13 and newer, and Fedora 41 and newer.
Runtime-loaded GUI libraries must be declared explicitly in the YAML; ELF
inspection only discovers linked dependencies. The ALSA library mapping also
uses the Debian/Ubuntu libasound2t64 name for this baseline.
Packaging CI builds both architectures using a pinned published release
(v0.11.2) for pushes and PRs, or the requested version for manual and release
runs. It then installs and removes each package in clean Ubuntu 24.04, Debian
13, Fedora 41 and current Fedora containers on native amd64 and arm64 runners.
Each case verifies that a settings fixture survives installation and removal,
runs spotifast --version, loads the GUI libraries with dlopen, and
verifies the desktop entry and icon. They cover installation and library
resolution, not a running desktop or Spotify playback. On release runs these
checks follow artifact attachment; a failure marks the workflow as failed.
The generated Homebrew cask is also installed, launched with --version,
signature-checked, and uninstalled on a native macOS runner. Wait for this
check before publishing the staged cask to the tap.
To repeat a check locally on the matching architecture, with Docker and a C compiler available:
bash packaging/test-install.sh ubuntu:24.04 dist/packages/1.2.3
bash packaging/test-install.sh fedora:latest dist/packages/1.2.3
Review or publish an existing build with the same installed CLI:
native-packages publish --from dist/packages/1.2.3 --to github --target linux-amd64 --target linux-arm64
native-packages repositories
native-packages status --offline
For applications with configured AUR or Homebrew destinations, stage the
recipes with native-packages stage TARGET dist/packages/1.2.3/recipes,
inspect native-packages diff TARGET, run native package validation, and
publish with native-packages publish TARGET. These destinations use ignored
managed Git clones, recorded in this application's YAML configuration.
AUR automation needs PUBLISH_AUR=true, AUR_SSH_KEY and AUR_KNOWN_HOSTS;
Homebrew automation needs PUBLISH_HOMEBREW=true and
HOMEBREW_TAP_GITHUB_TOKEN. Enable only configured destinations.
The macOS target, Windows and Flatpak build steps remain responsible for their native artifacts. Additional nFPM formats require suitable platform inputs and dependencies; adding a format does not port the application. See the shared CLI documentation for commands and supported formats.
The manual Flatpak from release workflow can rebuild a missing Flatpak from
an existing tag. It verifies the published Linux archive against checksums.txt
and uses that tag's version and description with the current Flatpak app ID,
rocks.spotifast.Spotifast, without compiling or replacing binaries.
It uploads a workflow artifact only. After checking the bundle, attach it to the
existing release and add its hash to checksums.txt, preserving every existing
asset and checksum. Release tags stay immutable.
Check AUR source-directory compatibility against a downloaded source archive
with bash packaging/test-arch-source.sh SOURCE_ARCHIVE VERSION. It runs the
recipe's prepare/build/check directory handling with Cargo calls stubbed out;
it does not replace compilation or native package installation checks.
To upgrade the tool, change tool.version in native-packages.yaml, the matching
immutable workflow reference, and any release-job gem installation pin together.
Applications need no packaging Gemfile, lockfile or Ruby wrapper.
Automatic macOS notarization
The macOS release job builds the app first, then selects
macos-universal from native-packages.yaml and uses packaging/macos/dmg.rb
to package it. Native Mac builds pass --defer-recipes, so they do not require
Linux inputs, AUR tooling or the not-yet-published DMG for Homebrew. The Linux
packaging job selects linux-amd64,linux-arm64 from the same configuration
after the release assets exist and generates downstream recipes then.
The shared gem signs its owned input copy, notarizes the DMG, staples and validates
Apple's ticket, and only then records final checksums. Configure these repository
secrets, which the job exposes as environment variables:
APPLE_CERTIFICATE_P12: base64 PKCS#12 Developer ID Application certificate and private key.APPLE_CERTIFICATE_PASSWORD: the export password.APPLE_SIGNING_IDENTITY: exactDeveloper ID Application: Name (TEAMID)identity.APPLE_ID,APPLE_TEAM_ID,APPLE_APP_PASSWORD: Apple email, Team ID and app-specific password.
A complete set enables notarization automatically. An incomplete set fails; no values retain local builds without Developer ID signing. Application inputs and the user's normal keychains remain unchanged. See the shared Apple setup and phase contract.
After preparing dist/macos-input on a Mac, test packaging without publishing:
native-packages build \
--version 1.2.3 --target macos-universal --defer-recipes --output dist/macos-packages-test
Secret configuration applies to future builds. Existing published DMGs retain their original signatures; this setup does not replace release assets.
packaging/release-names.py DIST TAG checks the release's spotifast-
downloads and writes their checksums. Run python3 packaging/test-release-names.py
when changing this step. Published historical downloads are never rewritten.