Upgrade Candlepin to 4.8.4

Development Releases
1

This procedure was generated from procedures/candlepin/release.md.erb at e719d79e0514cd3dd22ff02a21c0c484d839e67e

Make this post a wiki (help)

Build Package

  • Acquire Candlepin SRPM for 4.8.4
  • Build into Copr: copr build @theforeman/candlepin-4.8-staging candlepin-4.8.4*.src.rpm
  • Sign RPMs
  • Kick off the release pipeline by calling release_pipeline: VERSION=4.8 PROJECT=candlepin ./release_pipeline
  • Announce the release on Discourse using release_announcement: FULLVERSION=4.8.4 VERSION=4.8 PROJECT=candlepin ./release_announcement

Update Container Image

This bumps the Candlepin version pinned in candlepin-oci-images branches that already track Candlepin 4.8. It does not create new branches — that happens automatically as part of a Foreman release’s OCI branching, see theforeman-rel-eng-konflux.

  • Identify branches pinned to Candlepin 4.8 using candlepin_oci_branches: VERSION=4.8 ./candlepin_oci_branches
  • On each affected branch, bump VERSION_XYZ in images/candlepin/Containerfile to 4.8.4 and open a PR: sed -i 's/^ARG VERSION_XYZ=.*/ARG VERSION_XYZ=4.8.4/' images/candlepin/Containerfile
  • Merge the PR(s) — Konflux rebuilds and publishes the image automatically on merge, no manual pipeline trigger needed
  • Verify the new tag is published: quay.io/theforeman/candlepin
2

This is the one that has the PQC stuff in it right?

3

Reading from changelog:

  • CANDLEPIN-1253: Fixed bugs with legacy manifest import under PQC (crog@redhat.com)
  • Revert “CANDLEPIN-1253: Fixed import bug with legacy manifests” (crog@redhat.com)
4

It’s a weird piece of changelog, but that’s the whole changelog that I got for this release.