After we update FBC to promote a build from candidate to stable, we should send a documentation PR similar to https://github.com/openshift/openshift-docs/pull/70984/files to bump the docs accordingly.

/cc ctomasko

Rules

Update the HCO variable when a build is promoted to STABLE channel only.

The HCO version number should always reflect the most-current release number that was promoted to the STABLE channel.

Example

In the following case, the documentation would show 4.18.5 as the HCO version number.

• v4.18.3 is released to the Candidate channel
• v4.18.4 is released to the Candidate channel
• v4.18.5 is released to the Stable channel
• v4.18.6 is released to the Candidate channel
• v4.18.7 is released to the Candidate channel

Later, if v4.18.3 or 4.18.4 is promoted to STABLE, then do not override v4.18.5 as the HCO version number because we don't want to update the version number with an "older" version.

User stories

As a user, when I read the documentation, I want to see the latest release version, that is a stable release, reflected in the yamls and examples in the documentation.

As a writer, I want to update the HCO number for stable releases only, to ensure that only supported builds/content are in the documentation. This ensures that we meet service level agreements and that we do not include unsupported fixes without including disclaimers, such as Tech Preview notices.