-
Notifications
You must be signed in to change notification settings - Fork 527
[release 1.13] security: up deps in release branch #3463
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 1.13] security: up deps in release branch #3463
Conversation
Signed-off-by: Samantha Coyle <[email protected]>
will revert the go version bump in a bit. Didn't realize that was in my changes as well, but already switched to dapr/dapr updates for this |
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.
Ideally in a release branch we should never update dependencies unless they contain security issues or critical bug fixes. I am concerned with the fact that this PR updates A LOT of dependencies, including SDKs for cloud services.
Signed-off-by: Samantha Coyle <[email protected]>
Signed-off-by: Samantha Coyle <[email protected]>
These are all for security vulnerabilities based on my PR desc here: #3390 |
I see the |
I def did not do a |
Signed-off-by: Samantha Coyle <[email protected]>
Here's my tip:
|
Signed-off-by: Samantha Coyle <[email protected]>
Signed-off-by: Samantha Coyle <[email protected]>
Signed-off-by: Samantha Coyle <[email protected]>
Signed-off-by: Samantha Coyle <[email protected]>
Signed-off-by: Samantha Coyle <[email protected]>
Signed-off-by: Samantha Coyle <[email protected]>
Signed-off-by: Samantha Coyle <[email protected]>
Signed-off-by: Samantha Coyle <[email protected]>
Signed-off-by: Samantha Coyle <[email protected]>
Signed-off-by: Samantha Coyle <[email protected]>
flaky failure?
|
go.mod
Outdated
cloud.google.com/go/pubsub v1.33.0 | ||
cloud.google.com/go/secretmanager v1.11.2 | ||
cloud.google.com/go/storage v1.33.0 | ||
cloud.google.com/go/pubsub v1.36.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.
Why was the Google Cloud SDK updated? This was not in the table with the list of vulnerabilities
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.
this is required due to bumping the grpc package to the version without a security vulnerability. I just tried downgrading it back and it bumps us down for grpc pkg unfortunately
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.
See if using 1.60.1 requires bumping too, see other thread
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.
i think i got it now
Signed-off-by: Samantha Coyle <[email protected]>
Signed-off-by: Samantha Coyle <[email protected]>
Signed-off-by: Samantha Coyle <[email protected]>
Signed-off-by: Samantha Coyle <[email protected]>
@ItalyPaleAle are these transient failures in the build..? I think it's ready ready ready, but yeah need help knowing if these failures are flaky or not 🚀 🤓 ⭐ |
tests/certification/secretstores/hashicorp/vault/metadata_helpers.go
Outdated
Show resolved
Hide resolved
@@ -2,7 +2,7 @@ | |||
"private": true, | |||
"name": "dapr-cfworkers-client", | |||
"description": "Client code for Dapr to interact with Cloudflare Workers", | |||
"version": "20230517", | |||
"version": "20230625", |
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.
"version": "20230625", | |
"version": "20240625", |
:)
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.
This has not been resolved. The date is 1 year off...
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.
done
Signed-off-by: Samantha Coyle <[email protected]>
Signed-off-by: Samantha Coyle <[email protected]>
Signed-off-by: Samantha Coyle <[email protected]>
Signed-off-by: Samantha Coyle <[email protected]>
Signed-off-by: Samantha Coyle <[email protected]>
pls note that make modtidy-all with specifying my go version for go 1.21 creates two require blocks in the tests/certification go mod. That needs to stay to keep linter happy. I think I've addressed everything :) |
Signed-off-by: Alessandro (Ale) Segala <[email protected]>
Signed-off-by: Samantha Coyle <[email protected]>
…mponents-contrib into release-branch-sec-vul-fixing
Signed-off-by: Samantha Coyle <[email protected]>
anything else @ItalyPaleAle or g2g? :) |
There's one comment left PTAL |
Signed-off-by: Samantha Coyle <[email protected]>
done addressing feedback. Anything else? |
Description
I had issues cherry picking my merged commit directly from the main branch as it was bringing in a lot of other changes, so manually copy/pasted. For the cloudflare worker stuff I did up the dep and then recompile everything so that should be g2g.
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #[issue number]
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list: