Repository navigation
Update go updates - #70
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/go-updates
branch
from
May 21, 2026 22:49
2af320d to
8fa81d6
Compare
renovate
Bot
force-pushed
the
renovate/go-updates
branch
from
June 8, 2026 16:09
8fa81d6 to
bf8b3be
Compare
renovate
Bot
force-pushed
the
renovate/go-updates
branch
2 times, most recently
from
June 26, 2026 16:46
98f6bb1 to
645530b
Compare
renovate
Bot
force-pushed
the
renovate/go-updates
branch
2 times, most recently
from
July 11, 2026 18:31
b846be7 to
b6f4eb8
Compare
renovate
Bot
force-pushed
the
renovate/go-updates
branch
2 times, most recently
from
August 2, 2026 08:49
9d04624 to
0c31fb2
Compare
renovate
Bot
force-pushed
the
renovate/go-updates
branch
3 times, most recently
from
August 21, 2026 02:15
6ffe2d8 to
2a28708
Compare
renovate
Bot
force-pushed
the
renovate/go-updates
branch
3 times, most recently
from
September 8, 2026 16:15
992f766 to
58606aa
Compare
Contributor
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Due to Go's usage of Minimal Version Selection (MVS), these packages have been updated to the minimum version available, so will still abide by Details:
|
renovate
Bot
force-pushed
the
renovate/go-updates
branch
2 times, most recently
from
September 17, 2026 20:25
adb5cdf to
af5f90f
Compare
renovate
Bot
force-pushed
the
renovate/go-updates
branch
from
October 10, 2026 00:49
af5f90f to
3326744
Compare
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovate
Bot
force-pushed
the
renovate/go-updates
branch
from
October 13, 2026 01:50
3326744 to
730e687
Compare
This file contains hidden or 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
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:
v2.9.1→v2.9.6v0.43.0→v0.49.0v0.42.0→v0.47.0Release Notes
fxamacker/cbor (github.com/fxamacker/cbor/v2)
v2.9.6Compare Source
v2.9.6 fixes 12 bugs, including an important fix for apps that decode CBOR maps into Go maps, and has one behavior change. API is unchanged but more errors are detected.
Most of these bugs were identified while improving tests and reviewing code for an upcoming release.
Tests and fuzz tests were extended.
Upgrading to v2.9.6 from all prior versions is recommended.
🐞 Important Fix
Not affected:
map[any]any, and intoany(with unchangedDefaultMapType).For use cases outside the "not affected" list, decoding a CBOR null or undefined map key or value (including
55799(null)) into a Go map whose key or value type is of bool, integer, float, or string kind kept the previous map entry's key or value (instead of the zero value). See PR #855 for details.Decoding CBOR null or undefined into an interface that holds a value now sets it to nil, matching encoding/json (v1 and v2). Previously, the interface kept its value (PR #827), which was not the intended behavior.
What's Changed
Some of these bugs could only be triggered by incorrect usage in user apps, such as invalid struct tags or an unsupported DefaultByteStringType setting, etc. None of these bugs were reported by a project affected by them.
Decoding
Encoding
CI / GitHub Actions and Docs
Full Changelog: fxamacker/cbor@v2.9.4...v2.9.6
v2.9.5Compare Source
This version was tagged from the wrong branch by mistake and is retracted.
Use v2.9.6 (https://github.com/fxamacker/cbor/releases/tag/v2.9.6) instead.
v2.9.4Compare Source
This release fixes potential panics when decoding a CBOR map whose key decodes to an uncomparable Go value under certain conditions.
Not affected: user apps that don't register tag types and don't use map key types that are either named empty interfaces (e.g.
type MyAny any) or contain interfaces.These potential panics can be encountered when one of these two conditions is met:
TagSetinterface) that is an array or struct with uncomparable orinterface{}element or field type, orThis was identified while improving tests and reviewing code for an upcoming release.
Tests and fuzz tests were extended to cover this bug.
Upgrading to v2.9.4 is recommended.
What's Changed
Full Changelog: fxamacker/cbor@v2.9.3...v2.9.4
v2.9.3Compare Source
This release fixes a potential panic when decoding into a
time.Timefrom a CBOR byte string, map, or array under certain conditions.Not affected: standard CBOR time data (RFC 8949 tag 0 or tag 1), and decoders configured with
timeTag = DecTagRequired.Upgrading to v2.9.3 is recommended.
The panic stack trace was publicly reported on 2026-08-17, and the fix was released the same day. Fuzz testing was extended to cover this class of bug, and fuzzing of v2.9.3 is ongoing.
What's Changed
Full Changelog: fxamacker/cbor@v2.9.2...v2.9.3
v2.9.2Compare Source
This release refactors and hardens the streaming encoder by adding stricter checks for encoding CBOR indefinite-length data. Other changes include minor bugfixes, defensive checks, and more tests.
Projects that don't use CBOR indefinite-length data may also want to upgrade (summary of prior releases).
The stricter checks in the encoder prevent improper use of the library and bad inputs from producing malformed CBOR indefinite-length data that would be rejected by the decoder.
This release passed fuzz tests (billions of execs) and it is production quality.
What's Changed
CI / GitHub Actions and Docs
🔎 Details...
Full Changelog: fxamacker/cbor@v2.9.1...v2.9.2
Configuration
📅 Schedule: (UTC)
* 0-3 * * 1)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.