Publish packages as release downloads #41

New issue

Closed

opened 2026-10-17 11:41:10 +00:00 by littlefox · 1 comment

littlefox commented

2026-10-17 11:41:10 +00:00

Owner

User (D-027): "Are there published packages available for download in a release? If not make that happen"

As of 2026-10-17 there are no releases or tags. The packages exist only as workflow artifacts, which expire.

Plan:

On a v* tag, packaging.yml builds and checks all four distros, as it already does.
A release job then creates a Forgejo release for the tag with the Arch .pkg.tar.zst, the Debian .deb, the Fedora .rpm and .src.rpm, and SHA256SUMS. The notes give install commands per distro, including NixOS through the tagged flake (nix run git+https://forge.lysator.liu.se/littlefox/neokom?ref=vX.Y.Z).
First release: v0.1.0 from main.

User (D-027): "Are there published packages available for download in a release? If not make that happen" As of 2026-10-17 there are no releases or tags. The packages exist only as workflow artifacts, which expire. Plan: - On a `v*` tag, packaging.yml builds and checks all four distros, as it already does. - A `release` job then creates a Forgejo release for the tag with the Arch .pkg.tar.zst, the Debian .deb, the Fedora .rpm and .src.rpm, and SHA256SUMS. The notes give install commands per distro, including NixOS through the tagged flake (`nix run git+https://forge.lysator.liu.se/littlefox/neokom?ref=vX.Y.Z`). - First release: v0.1.0 from main.

littlefox added the

area/packaging

kind/feature

labels

2026-10-17 11:41:10 +00:00

littlefox referenced this issue from a pull request that will close it,

2026-10-17 11:42:01 +00:00

Publish packages as a Forgejo release on v* tags #42

littlefox referenced this issue from a commit

2026-10-17 11:42:02 +00:00

Publish packages as a Forgejo release on v* tags (D-027)

littlefox closed this issue

2026-10-17 12:12:15 +00:00

littlefox commented

2026-10-17 12:42:55 +00:00

Author

Owner

Done: https://forge.lysator.liu.se/littlefox/neokom/releases/tag/v0.1.0

Tag v0.1.0 ran packaging run #65. It built and install-tested all four distros, then the release job published the Arch, Debian and Fedora packages, SHA256SUMS and the install notes. The built-in workflow token was enough to create the release.

Checked afterwards: an anonymous download of the .deb, .pkg.tar.zst and .rpm all pass sha256sum -c.

To make the next release, push a tag (e.g. v0.2.0) after bumping the version in Cargo.toml, PKGBUILD and neokom.spec. The release job fails if the tag and the package version don't match.

Done: https://forge.lysator.liu.se/littlefox/neokom/releases/tag/v0.1.0 Tag v0.1.0 ran packaging run #65. It built and install-tested all four distros, then the release job published the Arch, Debian and Fedora packages, SHA256SUMS and the install notes. The built-in workflow token was enough to create the release. Checked afterwards: an anonymous download of the .deb, .pkg.tar.zst and .rpm all pass sha256sum -c. To make the next release, push a tag (e.g. v0.2.0) after bumping the version in Cargo.toml, PKGBUILD and neokom.spec. The release job fails if the tag and the package version don't match.