Skip to content

docs: Update release process for adding release series metadata #861

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 15, 2024
Merged

docs: Update release process for adding release series metadata #861

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion docs/content/contributing/releasing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ Sign the previous commit:
git commit --gpg-sign --amend --no-edit
```

If you are releasing a new minor release, the update the `metadata.yaml`s so that the upcoming release version is used
If you are releasing a new minor release, then update the `metadata.yaml`s so that the upcoming release version is used
for e.g. local development and e2e tests:

1. Add the new release to the root level `metadata.yaml` release series.
Expand All @@ -45,6 +45,12 @@ for e.g. local development and e2e tests:
1. Update the `caren` provider configuration in `test/e2e/config/caren.yaml` with the new release (replacing the last
minor release with the new minor release version) and the next minor release configuration (replacing the `v0.x.99`
configuration).
1. Commit the changed files:

```shell
git add metadata.yaml test/e2e/data/shared/v1beta1-caren/metadata.yaml test/e2e/config/caren.yaml
git commit --gpg-sign -m 'fixup! release: Update metadata for release'
```

And force push:

Expand Down
Loading