Story (Required)

As a release engineer, releasing OpenShift GitOps 1.16.0, I want the latest versions of binaries (argocd cli, argo rollouts CLI) to be available for download for customers.

Background (Required)

The binaries in RPMs gets published to the content gateway site of Red Hat for all OS and processor architecture combination. This is done automatically by the release process. However it is important to verify that the latest binaries are updated in the site post the release.

Out of scope

NA

Approach (Required)

1. Go to https://developers.redhat.com/content-gateway/rest/browse/pub/openshift-v4/clients/openshift-gitops/latest/
Download the binaries and run the following command to check the version.

<binary_name> version --client
eg: argocd-linux-amd64 version --client

The version should have an Extra Build Info field something like below

 ExtraBuildInfo: openshift-gitops-version: 1.15.0, release: 68

2. Check if the sha/md5 checksum matches the downloaded binary.

 shasum -a 256 <downloaded-binary>

3. Check if the binaries are signed.
For macOS, run the following command

codesign -dv --verbose=4  <downloaded-binary>

and check if the signature information are valid and signed by Red Hat certificates.

Signature size=8976
Authority=Developer ID Application: Red Hat, Inc. (HYSCB8KRL2)
Authority=Developer ID Certification Authority
Authority=Apple Root CA
Timestamp=31 Mar 2025 at 7:44:46 PM
Info.plist=not bound
TeamIdentifier=HYSCB8KRL2

Dependencies

The release should have been completed and the errata should be in SHIPPED_LIVE state.

Acceptance Criteria (Mandatory)

The latest version of all binaries are available in this link.
https://developers.redhat.com/content-gateway/rest/browse/pub/openshift-v4/clients/openshift-gitops/
and the latest version is pointing to the right set of binaries built for 1.15.0
https://developers.redhat.com/content-gateway/rest/browse/pub/openshift-v4/clients/openshift-gitops/latest/

<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met