rancher
/
cluster-api-addon-provider-fleet
mirror of https://github.com/rancher/cluster-api-addon-provider-fleet.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add downstream build step (#326) 

Signed-off-by: Danil-Grigorev <danil.grigorev@suse.com>
This commit is contained in:
Danil Grigorev 2025-06-20 18:16:15 +02:00 committed by GitHub
parent d00f312093
commit 3592c672bd
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 9 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/src/05_developers/01_release.md
View File

@ -48,7 +48,14 @@ git push upstream ${RELEASE_TAG}
This will trigger a [release GitHub action](https://github.com/rancher-sandbox/cluster-api-addon-provider-fleet/actions/workflows/release.yaml) that creates a release with `CAAPF` components.
4. Wait for the [update metadata](https://github.com/rancher/cluster-api-addon-provider-fleet/blob/main/.github/workflows/update-metadata.yaml) workflow to pass successfully.
This workflow will update the `metadata.yaml` file in the root of the repository preparing it for the next release.
This workflow will update the `metadata.yaml` file in the root of the repository preparing it for the next release. It will open a [PR](https://github.com/rancher/cluster-api-addon-provider-fleet/pull/309), which needs to be merged before the next minor version release can be cut.
**WARNING: Out of date published metadata.yaml file will cause upstream install via clusterctl to fail**
5. Perform Downstream Build
Perform the downstream build for the release tag using the CAAPF GitHub action. Specific steps and references for this process can be found by asking in the `#team-rancher-highlander` channel.
## Versioning
@ -97,4 +104,4 @@ The `release-X` branches contain stable, backwards compatible code. On every maj
CAAPF maintains the most recent release/releases for all supported APIs. Support for this section refers to the ability to backport and release patch versions; [backport policy](#backporting) is defined above.
- The API version is determined from the GroupVersion defined in the `#[kube(...)]` derive macro inside `./src/api`.
- For the current stable API version (v1alpha1) we support the two most recent minor releases; older minor releases are immediately unsupported when a new major/minor release is available.
- For the current stable API version (v1alpha1) we support the two most recent minor releases; older minor releases are immediately unsupported when a new major/minor release is available.