-
Notifications
You must be signed in to change notification settings - Fork 30
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
chore: minor updates to deps #330
Conversation
These were tested working, reason for not upgrading
|
Also just noticed we have Dependabot PRs for some of these... |
@graza-io Can we use the Dependabot PRs for any packages covered in both sets of PRs? Any not caught by Dependabot we can then update in this PR. |
The following Dependabot PRs are captured here & tested but should just use their own PR:
The following Dependabot PR is probably a good one to include but untested: This one can't be done right now as latest would break build, which is the main purpose of this PR, to update to a reasonable version in between current and latest, which contains some fixes. |
@cbruno10 reworked so now only contains the update for |
@graza-io I think we could update to use Go 1.21 (the latest Steampipe plugin SDK will require it I believe), unless there's a larger issue that you know of. If we update to Go 1.21, would we be able to merge in #324, or are there other breaking changes affecting us in argonsecurity/pipeline-parser v1.3.4? |
Actually I think I read this wrong and that it requires being built with a version of go prior to 1.21. Starting with This seems to have issues being built. Because my local ❯ go version
go version go1.21.1 darwin/arm64
Options:
|
@graza-io Thanks for the details, my vote would be to update to |
No description provided.