nzbget is absent from the artifactapi rpm-vendor-el9/rpm-vendor-el8
repodata, so `dnf install nzbget` fails on the media host. Its build.sh
requested the download asset using PACKAGE_RELEASE, which carries the
dist tag (e.g. 1.el9); upstream only publishes nzbget-<version>-1.x86_64.rpm,
so the fetch 404s and a 22-byte junk file gets published that createrepo
cannot index. The existing junk nzbget-26.1-1.el9 also makes the deploy
dedup probe return 200, blocking re-upload of a corrected 26.1.
- Point the build.sh source URL at the upstream release-1 asset name,
keeping the dist-tagged local output filename (mirrors code-server).
- Bump nzbget el8/el9 to 26.2 (current upstream stable) so the corrected
build produces a fresh filename that the deploy step will actually PUT.
Claude-Session: https://claude.ai/code/session_015ur3i7D2azsMAWTSVABApv
- Add github_release_pattern field to support multi-product repositories
- Implement get_github_releases_by_pattern() for filtered release matching
- Add parse_github_version_release() to extract version-release components
- Update openbao plugin packages with release patterns and correct versions
- Configure openbao-plugins meta package for manual versioning
- Fix HashiCorp package GitHub repository references
- Support complex tag formats like "secrets-consul-v0.1.0" and "v7.1.3-1"
This enables automatic updates for packages sharing GitHub repos while
maintaining proper RPM version/release semantics and backward compatibility.
- Migrate from legacy shell-based build system to modern Python tooling
- Update all metadata.yaml files to new schema with per-distro builds
- Standardise build scripts with curl -L, envsubst, and error handling
- Convert nfpm.yaml templates to use environment variable substitution
- Update Dockerfile to accept all package metadata as build arguments
- Modernise Makefile to use new Python build tool commands
- Update CI workflow to use tools/build instead of make
Add simplified metadata structure for all 41 packages containing:
- Package name, version, and release number
- GitHub repository for packages with GitHub releases
- Build configuration for el/8 and el/9 distributions
This metadata enables future automation for version checking and package building across different distributions.