-
Notifications
You must be signed in to change notification settings - Fork 32
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 go to 1.22.6 #610
base: eng
Are you sure you want to change the base?
bump go to 1.22.6 #610
Conversation
@BergCyrill, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding
|
All commits are signed & signoff was made according to the dco. I don't unterstand why the vmwclabot doesn't recognize this, I think it is a false behaviour. |
d226ff0
to
afe29cd
Compare
@BergCyrill, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding
|
afe29cd
to
b83c418
Compare
@BergCyrill, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding
|
Ok tried to fix the dco-required label-issue. Worked for me on the terraform-provider-nsxt github project but not here. |
@BergCyrill, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding
|
f8444ce
to
dc48680
Compare
@BergCyrill, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding
|
Linting should now work with selected go toolchain version. The clabot still behaves weird. |
Is there anything that prevents this PR from being merged? The provider is currently unusable for me since it will not pass vulnerability checks. |
The DCO issue is related to the author mismatch in f930556 where [email protected] is using instead of [email protected].
Try: git checkout f9305564d2cc69d041add802de4a23bb55c69daf
git commit --amend --author="Cyrill Berg <[email protected]>"
git push --force |
Signed-off-by: Cyrill Berg <[email protected]>
Signed-off-by: Cyrill Berg <[email protected]>
Signed-off-by: Cyrill Berg <[email protected]>
dc48680
to
8e43c08
Compare
Thank you, I have totally overlooked this little detail in the commit author field. Should be better now. |
Looks good! |
@tenthirtyam is there anything I could do to get this PR merged and released? |
Anyone who can give an update on this? It gives a bad feeling if high severity CVE are not fixed for such a long time even when someone tries to contribute. I'm willing to help just give me a hint what is missing?! |
I'll ping the PM tomorrow. |
PMs have been informed. |
Due to unfixed CVEs in go <1.22.4 bump the used go version to build the provider to 1.22.6
The CVE (CVE-2024-24790) scores a 9.8 in the national vulnerability database.