-
Notifications
You must be signed in to change notification settings - Fork 247
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.
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
Release v0.13.1 #1172
Comments
/lgtm |
1 similar comment
/lgtm |
+1 |
/lgtm |
+1 |
Plus I'm not aware of anything else in the pipeline |
Does the PR that introduced this situation was part of V0.13? if older than that, maybe this can be just a nice fix for V0.14 |
Reactive updates was part of v0.13: |
ok then this qualifies for v0.13.1 IMO |
/lgtm |
Final changelog for v0.13.1 CHANGELOG
If there are no further objections I'll start the release process tomorrow. |
Release cut is paused for today, image promotion is broken |
eduardo@fedora:~$ polluntiltrue "skopeo list-tags docker://registry.k8s.io/nfd/node-feature-discovery |grep v0.13.1" 3
"v0.13.1",
"v0.13.1-full",
"v0.13.1-minimal", |
/close |
@ArangoGutierrez: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Release Checklist
hack/prepare-release.sh $VERSION
to turn references to point to the upcoming release(README, deployment templates, docs configuration, test/e2e flags), submit a PR against the release branch
prepare-release.sh
script above to the draft releasegit tag -s $VERSION
and inserts the changelog into the tag description.
git push $VERSION
gcr.io/k8s-staging-nfd/node-feature-discovery:$VERSION
https://kubernetes-sigs.github.io/node-feature-discovery/0.$MAJ/
registry.k8s.io/images/k8s-staging-nfd/images.yaml
to promote the container images (both "full" and "minimal" variants) to productionregistry.k8s.io/nfd/node-feature-discovery:$VERSION
) is available.which will also trigger a Helm repo index update to add the latest release
dev@kubernetes.io
with the subject[ANNOUNCE] node-feature-discovery $VERSION is released
hack/prepare-release.sh $VERSION
but only committing README.md, and,submit a PR
Changelog
The text was updated successfully, but these errors were encountered: