-
Notifications
You must be signed in to change notification settings - Fork 1
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
Update go updates #15
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
028ffd0
to
3b89ba7
Compare
e35c517
to
abe985c
Compare
86cc08c
to
af536f8
Compare
af536f8
to
23d7e9e
Compare
7141f0d
to
0a33fa6
Compare
4bef3ce
to
17e6b73
Compare
17e6b73
to
8d7de88
Compare
434d3dc
to
bc287c4
Compare
bc287c4
to
628aafc
Compare
46d8c1b
to
f9a93cc
Compare
32c0960
to
97598f8
Compare
9cb1a81
to
5a2190c
Compare
87c66e1
to
c36103e
Compare
⚠ Artifact update problemRenovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below: File name: go.sum
|
8a23d58
to
30863b8
Compare
Signed-off-by: Platform Engineering Bot <platform-engineering@redhat.com>
30863b8
to
b21937d
Compare
This update is marked "immortal", so I'm closing it to give the new bot a clean chance to make the update. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v3.11.0
->v3.12.0
v1.2.4
->v1.4.1
v0.20.0
->v0.21.0
v0.20.2
->v0.21.0
v0.22.4
->v0.23.0
v1.5.3
->v1.5.4
v1.3.0
->v1.6.0
v1.8.4
->v1.9.0
v0.8.0
->v0.11.1
v0.17.0
->v0.24.0
v0.13.0
->v0.20.0
v0.13.0
->v0.20.0
v0.13.0
->v0.20.0
v0.13.0
->v0.15.0
v0.3.0
->v0.5.0
v1.6.7
->v2.0.6
v1.31.0
->v1.34.0
v2.4.0
->v3.0.1
v0.28.4
->v0.30.0
v0.28.4
->v0.30.0
v0.28.4
->v0.30.0
v2.100.1
->v2.120.1
a781456
->f0e62f9
3b25d92
->fe8a2dd
v4.3.0
->v4.4.1
v1.3.0
->v1.4.0
Release Notes
emicklei/go-restful (github.com/emicklei/go-restful/v3)
v3.12.0
Compare Source
v3.11.3
Compare Source
v3.11.2
Compare Source
v3.11.1
Compare Source
go-logr/logr (github.com/go-logr/logr)
v1.4.1
Compare Source
What's Changed
Full Changelog: go-logr/logr@v1.4.0...v1.4.1
v1.4.0
Compare Source
This release dramatically improves interoperability with Go's
log/slog
package. In particular,logr.NewContext
andlogr.NewContextWithSlogLogger
use the same context key, which allowslogr.FromContext
andlogr.FromContextAsSlogLogger
to returnlogr.Logger
or*slog.Logger
respectively, including transparently converting each to the other as needed.Functions
logr/slogr.NewLogr
andlogr/slogr.ToSlogHandler
have been superceded bylogr.FromSlogHandler
andlogr.ToSlogHandler
respectively, and typelogr/slogr.SlogSink
has been superceded bylogr.SlogSink
. All of the old names inlogr/slogr
remain, for compatibility.Package
logr/funcr
now supportslogr.SlogSink
, meaning that it's output passes all but one of the Slog conformance tests (that exception being thatfuncr
handles the timestamp itself).Users who have a
logr.Logger
and need a*slog.Logger
can callslog.New(logr.ToSlogHandler(...))
and all output will go through the same stack.Users who have a
*slog.Logger
orslog.Handler
can calllogr.FromSlogHandler(...)
and all output will go through the same stack.What's Changed
New Contributors
Full Changelog: go-logr/logr@v1.3.0...v1.4.0
v1.3.0
Compare Source
This release adds support for slog in a new, self-contained
logr/slogr
package. Implementers of alogr.LogSink
are encouraged, but not required, to extend their implementation to improve the quality of log output coming from aslog
API call.Breaking change: the call depth for
LogSink.Enabled
when called viaLogger.Enabled
was fixed to be the same as for other call paths. Implementers of aLogSink
who have worked around this bug will need to remove their workarounds.Security best practices were improved. Only Go versions >= 1.18 are supported by this release.
What's Changed
New Contributors
Full Changelog: go-logr/logr@v1.2.4...v1.3.0
go-openapi/jsonpointer (github.com/go-openapi/jsonpointer)
v0.21.0
Compare Source
v0.20.3
Compare Source
v0.20.2
Compare Source
v0.20.1
Compare Source
go-openapi/jsonreference (github.com/go-openapi/jsonreference)
v0.21.0
Compare Source
v0.20.5
Compare Source
v0.20.4
Compare Source
v0.20.3
Compare Source
go-openapi/swag (github.com/go-openapi/swag)
v0.23.0
Compare Source
v0.22.10
Compare Source
v0.22.9
Compare Source
v0.22.8
Compare Source
v0.22.7
Compare Source
v0.22.6
Compare Source
v0.22.5
Compare Source
golang/protobuf (github.com/golang/protobuf)
v1.5.4
Compare Source
Notable changes
google/uuid (github.com/google/uuid)
v1.6.0
Compare Source
Features
Bug Fixes
v1.5.0
Compare Source
Features
v1.4.0
Compare Source
Features
Fixes
v1.3.1
Compare Source
Bug Fixes
stretchr/testify (github.com/stretchr/testify)
v1.9.0
Compare Source
What's Changed
Called
by @aud10slave in https://github.com/stretchr/testify/pull/631NotImplements
and variants by @hslatman in https://github.com/stretchr/testify/pull/1385New Contributors
Full Changelog: stretchr/testify@v1.8.4...v1.9.0
arcalot/arcaflow-plugin-sdk-go (go.flow.arcalot.io/pluginsdk)
v0.11.1
Compare Source
What's Changed
Full Changelog: arcalot/arcaflow-plugin-sdk-go@v0.11.0...v0.11.1
v0.11.0
Compare Source
Changes
RootObject()
function to access the scope's root with validation.v0.10.0-beta1
PRs
Full Changelog: arcalot/arcaflow-plugin-sdk-go@v0.8.0...v0.11.0
golang/appengine (google.golang.org/appengine)
v2.0.6
Compare Source
What's Changed
New Contributors
Full Changelog: golang/appengine@v1.6.8...v2.0.6
v2.0.5
Compare Source
What's Changed
New Contributors
Full Changelog: golang/appengine@v2.0.4...v2.0.5
v2.0.4
Compare Source
What's Changed
New Contributors
Full Changelog: golang/appengine@v2.0.3...v2.0.4
v2.0.3
Compare Source
What's Changed
New Contributors
Full Changelog: golang/appengine@v2.0.2...v2.0.3
v2.0.2
: Release App Engine golang SDK v2.0.2Compare Source
What's Changed
New Contributors
Full Changelog: golang/appengine@v2.0.1...v2.0.2
v2.0.1
: Version 2.0.1Compare Source
v1.6.8
Compare Source
protocolbuffers/protobuf-go (google.golang.org/protobuf)
v1.34.0
Compare Source
Notable changes
New Features
Protobuf editions are fully supported. You can now use
edition = "2023"
in .proto files together with theproto-gen-go
. Edition2023 does not introduce any new features but can be used to replacesyntax "proto2/3"
. Future editions might introduce new features. See https://protobuf.dev/editions/overview/ for more details on protobuf editions.Documentation
Various smaller changes to improve existing documentation and to add more examples.
Extensions
These are mostly performance improvements or preparations for performance improvements.
v1.33.0
Compare Source
This release contains one security fix:
encoding/protojson
:Unmarshal
could enter an infinite loop when unmarshaling certain forms of invalid JSON. This condition can occur when unmarshaling into a message which contains agoogle.protobuf.Any
value, or when theUnmarshalOptions.DiscardUnknown
option is set.Unmarshal
now correctly returns an error when handling these inputs. This is CVE-2024-24786.v1.32.0
Compare Source
Full Changelog: protocolbuffers/protobuf-go@v1.31.0...v1.32.0
This release contains commit protocolbuffers/protobuf-go@bfcd647, which fixes a denial of service vulnerability by preventing a stack overflow through a default maximum recursion limit. See https://github.com/golang/protobuf/issues/1583 and https://github.com/golang/protobuf/issues/1584 for details.
go-yaml/yaml (gopkg.in/yaml.v2)
v3.0.1
Compare Source
v3.0.0
Compare Source
kubernetes/api (k8s.io/api)
v0.30.0
Compare Source
v0.29.4
Compare Source
v0.29.3
Compare Source
v0.29.2
Compare Source
v0.29.1
Compare Source
v0.29.0
Compare Source
v0.28.9
Compare Source
v0.28.8
Compare Source
v0.28.7
Compare Source
v0.28.6
[C
Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.