-
Notifications
You must be signed in to change notification settings - Fork 75
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
Bump referenced Velero tag. #151
Conversation
Signed-off-by: Xun Jiang <[email protected]>
e1538ae
to
c7e9fb1
Compare
k8s.io/api v0.22.2 | ||
k8s.io/apimachinery v0.22.2 | ||
github.com/stretchr/testify v1.8.2 | ||
github.com/vmware-tanzu/velero v0.0.0-20230727074327-a6d79fc272a2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why not a specific tagged release? like v1.11.1
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would be easier to read and match with tagged commits in the future.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kaovilai this is for the main branch, not release-1.11 -- ongoing dev work for a release that will come out with 1.12. Not sure about this plugin, but certainly the CSI pluign needs post-1.11 stuff. On the release branch, we can peg this to a specific release tag, but for ongoing dev work, that's not always possible. This is just the lastest main commit as of when this PR was submitted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ahh yes.
I imagine this is something CI (github actions) could do on a regular basis to check for breakage? |
No description provided.