Start here

Packager.io Documentation

Build native DEB and RPM packages in GitHub Actions, publish them to signed repositories, and install them with standard Linux tools.

Packager.io turns an application repository into native Linux packages. Builds run in your own GitHub Actions workflow; Packager.io hosts the results as fast, signed package repositories.

DEB and RPM together

Publish Debian, Ubuntu, Enterprise Linux, and SUSE packages from one workflow.

GitHub-native builds

Build on every tag, release branch, schedule, or manual dispatch with pkgr/action.

Channels for every release line

Keep develop, stable/16, and feature builds isolated without duplicating repositories.

Signed repositories

Packager.io creates APT, DNF/YUM, and Zypper metadata and signs it with your organization key.

Granular access

Use organization administration tokens, narrow publish tokens, and pull tokens for private repositories.

A practical CLI

Manage repositories, channels, packages, and installer instructions with packagehall-ctl.

How the pieces fit together

  1. pkgr/action/package@v1 builds a .deb or .rpm inside GitHub Actions.
  2. pkgr/action/publish@v1 uploads that package to go.packager.io.
  3. Packager.io indexes and signs the package under your organization, repository, channel, and target.
  4. Your users install it with apt, dnf, yum, or zypper.
GitHub repository → GitHub Actions → DEB / RPM → Packager.io → Linux servers

Supported targets

The current build-image matrix covers these 64-bit targets:

Family Targets Package
Debian 11, 12, 13 DEB / amd64
Ubuntu 20.04, 22.04, 24.04, 26.04 DEB / amd64
Enterprise Linux 8, 9, 10 RPM / x86_64
SUSE Linux Enterprise Server 12, 15, 16 RPM / x86_64

Write targets as dist/version, for example ubuntu/24.04 or el/9.

Start publishing

Ask [email protected] for an organization administrator token. Then follow Getting started to configure the CLI, create your repository, and add a publish token to GitHub.

Moving from the old Packager.io? Builds now run through GitHub Actions. We can also copy existing repositories and published package history for you. See the migration guide or email [email protected].