fix(deps): update all non-major gomod dependencies #96
+59
−57
Conversation
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
red-hat-konflux
bot
force-pushed
the
konflux/mintmaker/main/all-minor-patch-gomod
branch
7 times, most recently
from
d09a00e to
d90b8a5
Compare
red-hat-konflux
bot
force-pushed
the
konflux/mintmaker/main/all-minor-patch-gomod
branch
11 times, most recently
from
2fdad63 to
f08703c
Compare
red-hat-konflux
bot
force-pushed
the
konflux/mintmaker/main/all-minor-patch-gomod
branch
12 times, most recently
from
6869f0f to
fdf5db7
Compare
red-hat-konflux
bot
force-pushed
the
konflux/mintmaker/main/all-minor-patch-gomod
branch
14 times, most recently
from
91eba3d to
33fa660
Compare
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
red-hat-konflux
bot
force-pushed
the
konflux/mintmaker/main/all-minor-patch-gomod
branch
from
33fa660 to
9de89bc
Compare
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:
v0.4.1->v0.5.1v5.16.2->v5.16.3v4.1.2->v4.1.3v0.23.0->v0.24.0v0.26.0->v0.27.2v1.20.0->v1.22.0v1.2.0->v1.4.0v0.4.0->v0.5.0v1.3.1->v1.3.2v1.10.0->v1.11.1v1.16.3->v1.17.0v0.41.0->v0.43.0v0.43.0->v0.46.0v0.35.0->v0.37.0v0.28.0->v0.30.0v0.12.0->v0.14.0Release Notes
cyphar/filepath-securejoin (github.com/cyphar/filepath-securejoin)
v0.5.1: -- "Spooky scary skeletons send shivers down your spine!"Changed
openat2can return-EAGAINif it detects a possible attack in certainscenarios (namely if there was a rename or mount while walking a path with a
..component). While this is necessary to avoid a denial-of-service in thekernel, it does require retry loops in userspace.
In previous versions,
pathrs-litewould retryopenat232 times beforereturning an error, but we've received user reports that this limit can be
hit on systems with very heavy load. In some synthetic benchmarks (testing
the worst-case of an attacker doing renames in a tight loop on every core of
a 16-core machine) we managed to get a ~3% failure rate in runc. We have
improved this situation in two ways:
We have now increased this limit to 128, which should be good enough for
most use-cases without becoming a denial-of-service vector (the number of
syscalls called by the
O_PATHresolver in a typical case is within thesame ballpark). The same benchmarks show a failure rate of ~0.12% which
(while not zero) is probably sufficient for most users.
In addition, we now return a
unix.EAGAINerror that is bubbled up and canbe detected by callers. This means that callers with stricter requirements
to avoid spurious errors can choose to do their own infinite
EAGAINretryloop (though we would strongly recommend users use time-based deadlines in
such retry loops to avoid potentially unbounded denials-of-service).
v0.5.0Compare Source
This is our first release of
github.com/cyphar/filepath-securejoin,containing a full implementation with a coverage of 93.5% (the only missing
cases are the error cases, which are hard to mocktest at the moment).
go-git/go-git (github.com/go-git/go-git/v5)
v5.16.3Compare Source
What's Changed
Full Changelog: go-git/go-git@v5.16.2...v5.16.3
go-jose/go-jose (github.com/go-jose/go-jose/v4)
v4.1.3Compare Source
This release drops Go 1.23 support as that Go release is no longer supported. With that, we can drop
x/cryptoand no longer have any external dependencies in go-jose outside of the standard library!This release fixes a bug where a critical b64 header was ignored if in an unprotected header. It is now rejected instead of ignored.
What's Changed
Full Changelog: go-jose/go-jose@v4.1.2...v4.1.3
hashicorp/terraform-exec (github.com/hashicorp/terraform-exec)
v0.24.0Compare Source
ENHANCEMENTS:
QueryJSONand introduce new way for consuming Terraform's structured logging (#539)INTERNAL:
v0.23.1Compare Source
BUG FIXES:
SetEnableLegacyPipeClosing(true)to avoid hanging on cancellation.INTERNAL:
hashicorp/terraform-json (github.com/hashicorp/terraform-json)
v0.27.2Compare Source
NOTES / BUG FIXES
UnmarshalLogMessageto usejson.Number(instead of defaultfloat64) (#178)0.27.1consumers.v0.27.1Compare Source
What's Changed
ENHANCEMENTS
json.RawMessagewithanyfor list log messages by @dbanck in #177Full Changelog: hashicorp/terraform-json@v0.27.0...v0.27.1
v0.27.0Compare Source
What's Changed
ENHANCEMENTS
UnmarshalLogMessage()by @radeksimko in #167INTERNAL
New Contributors
Full Changelog: hashicorp/terraform-json@v0.26.0...v0.27.0
hashicorp/vault (github.com/hashicorp/vault/api)
v1.21.0Compare Source
kevinburke/ssh_config (github.com/kevinburke/ssh_config)
v1.4.0Compare Source
pjbgf/sha1cd (github.com/pjbgf/sha1cd)
v0.5.0Compare Source
What's Changed
20a022eto14fd8a5by @dependabot[bot] in #194Full Changelog: pjbgf/sha1cd@v0.4.0...v0.5.0
skeema/knownhosts (github.com/skeema/knownhosts)
v1.3.2Compare Source
stretchr/testify (github.com/stretchr/testify)
v1.11.1Compare Source
This release fixes #1785 introduced in v1.11.0 where expected argument values implementing the stringer interface (
String() string) with a method which mutates their value, when passed to mock.Mock.On (m.On("Method", <expected>).Return()) or actual argument values passed to mock.Mock.Called may no longer match one another where they previously did match. The behaviour prior to v1.11.0 where the stringer is always called is restored. Future testify releases may not call the stringer method at all in this case.What's Changed
Full Changelog: stretchr/testify@v1.11.0...v1.11.1
v1.11.0Compare Source
What's Changed
Functional Changes
v1.11.0 Includes a number of performance improvements.
Fixes
Documentation, Build & CI
New Contributors
Full Changelog: stretchr/testify@v1.10.0...v1.11.0
zclconf/go-cty (github.com/zclconf/go-cty)
v1.17.0Compare Source
ctynow requires Go 1.23 or later.cty.Value.Elementsoffers a moderniter.Seq2-based equivalent ofcty.Value.ElementIterator.cty.DeepValuesoffers a moderniter.Seq2-based equivalent ofcty.Walk.cty.Value.WrangleMarksDeepallows inspecting and modifying individual marks throughout a possibly-nested data structure.Having now got some experience using marks more extensively in some callers, it's become clear that it's often necessary for different subsystems to be able to collaborate using independent marks without upsetting each other's assumptions. Today that tends to be achieved using hand-written transforms either with
cty.Transformorcty.Value.UnmarkDeepWithPaths/cty.Value.MarkWithPaths, both of which can be pretty expensive even in the common case where there are no marks present at all.This new function allows inspecting and transforming marks with far less overhead, by creating new values only for parts of a structure that actually need to change and by reusing (rather than recreating) the "payloads" of the values being modified when we know that only the marks have changed.
cty.ValueMarksOfTypeandcty.ValueMarksOfTypeDeepmake it easier to use type-based rather than value-based mark schemes, where different values of a common type are used to track a specific kind of relationship with multiple external values.cty.Value.HasMarkDeepprovides a "deep" version of the existingcty.Value.HasMark, searching throughout a possibly-nested structure for any values that have the given mark.cty.Value.UnmarkDeepandcty.Value.UnmarkDeepWithPathsare now implemented in terms ofcty.Value.WrangleMarksDeep, so they benefit from its reduced overhead. In particular they avoid reconstructing a data structure that contains no marked values at all.cty.Value.MarkWithPathsnow has a fast path when it's given a zero-lengthPathValueMarks, in which case it just returns the value it was given with no modifications.v1.16.4Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.
To execute skipped test pipelines write comment
/ok-to-test.This PR has been generated by MintMaker (powered by Renovate Bot).