chore(deps): update go dependencies (backplane-2.9) #404
Conversation
![red-hat-konflux[bot]](https://avatars.githubusercontent.com/in/296509?s=60&v=4){kind=small}
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: red-hat-konflux[bot] The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
red-hat-konflux
bot
force-pushed
the
konflux/mintmaker/backplane-2.9-backplane-2.9/go-deps
branch
from
275ab04 to
78c6ead
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/backplane-2.9-backplane-2.9/go-deps
branch
from
78c6ead to
285d22e
Compare
|
@red-hat-konflux[bot]: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update ( If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
red-hat-konflux
bot
deleted the
konflux/mintmaker/backplane-2.9-backplane-2.9/go-deps
branch
This PR contains the following updates:
v1.3.2->v1.5.0v3.2.1->v3.3.1v3.2.3->v3.3.0v2.2.0->v2.3.0v0.2.4->v0.4.1v3.11.0->v3.12.2v5.7.0+incompatible->v5.9.11+incompatiblev5.9.0->v5.9.11v1.7.0->v1.9.0v1.4.1->v1.4.3v0.19.6->v0.21.1v0.20.2->v0.21.0v0.22.3->v0.23.141bb18b->2c02b82v0.6.8->v0.6.9v0.6.0->v0.7.04bb14d4->033d6d7v1.4.0->v1.5.0v0.7.7->v0.9.0v0.2.0->v0.5.0v1.19.0->v1.22.0v0.5.0->v0.6.2v0.48.0->v0.64.0v0.12.0->v0.16.1v1.3.1->v1.4.0v1.5.0->v1.9.2v1.0.5->v1.0.6v0.36.0->v0.39.097b1e66->b7579e2v0.34.0->v0.41.0v0.28.0->v0.30.0v0.31.0->v0.33.0v0.30.0->v0.32.0v0.23.0->v0.26.0v0.5.0->v0.12.0v0.21.1-0.20240508182429-e35e4ccd0d2d->v0.34.0v2.4.0->v2.5.094a12d6->513f239v1.33.0->v1.36.6v3.14.2->v3.18.3v0.30.2->v0.33.2v0.30.2->v0.33.2v0.30.2->v0.33.270dd376->8b98d1ebc3834c->cfa47c3v4.4.1->v4.7.0Warning
Some dependencies could not be looked up. Check the warning logs for more information.
Release Notes
BurntSushi/toml (github.com/BurntSushi/toml)
v1.5.0Compare Source
Mostly some small bugfixes, with a few small new features:
Add Position.Col, to mark the column an error occurred (#410)
Print more detailed errors in the
tomlvCLI.Ensure ParseError.Message is always set (#411)
Allow custom string types as map keys (#414)
Mark meta keys as decoded when using Unmarshaler interface (#426)
Fix encoding when nested inline table ends with map (#438)
Fix encoding of several layers of embedded structs (#430)
Fix ErrorWithPosition panic when there is no newline in the TOML document (#433)
v1.4.0Compare Source
This version requires Go 1.18
Add toml.Marshal() (#405)
Require 2-digit hour (#320)
Wrap UnmarshalTOML() and UnmarshalText() return values in ParseError for position information (#398)
Fix inline tables with dotted keys inside inline arrays (e.g.
k=[{a.b=1}]) (#400)Masterminds/semver (github.com/Masterminds/semver/v3)
v3.3.1Compare Source
What's Changed
Full Changelog: Masterminds/semver@v3.3.0...v3.3.1
v3.3.0Compare Source
What's Changed
New Contributors
Full Changelog: Masterminds/semver@v3.2.1...v3.3.0
Masterminds/sprig (github.com/Masterminds/sprig/v3)
v3.3.0Compare Source
What's Changed
New Contributors
Full Changelog: Masterminds/sprig@v3.2.3...v3.3.0
cespare/xxhash (github.com/cespare/xxhash/v2)
v2.3.0Compare Source
cyphar/filepath-securejoin (github.com/cyphar/filepath-securejoin)
v0.4.1Compare Source
This release fixes a regression introduced in one of the hardening
features added to filepath-securejoin 0.4.0.
rootpaths passed toSecureJoinin 0.4.0 wasfound to be too strict and caused some regressions when folks tried to
update, so this restriction has been relaxed to only return an error if the
path contains a
..component. We still recommend users usefilepath.Clean(and even
filepath.EvalSymlinks) on therootpath they are using, but atleast you will no longer be punished for "trivial" unclean paths. (#46)
Signed-off-by: Aleksa Sarai [email protected]
v0.4.0Compare Source
This release primarily includes a few minor breaking changes to make the
MkdirAll and SecureJoin interfaces more robust against accidental
misuse.
SecureJoin(VFS)will now return an error if the providedrootis not afilepath.Clean'd path.While it is ultimately the responsibility of the caller to ensure the root is
a safe path to use, passing a path like
/symlink/..as a root would resultin the
SecureJoin'd path being placed in/even though/symlink/..might be a different directory, and so we should more strongly discourage
such usage.
All major users of
securejoin.SecureJoinalready ensure that the paths theyprovide are safe (and this is ultimately a question of user error), but
removing this foot-gun is probably a good idea. Of course, this is
necessarily a breaking API change (though we expect no real users to be
affected by it).
Thanks to Erik Sjölund, who initially
reported this issue as a possible security issue.
MkdirAllandMkdirHandlenow take anos.FileMode-style mode argumentinstead of a raw
unix.S_*-style mode argument, which may cause compile-timetype errors depending on how you use
filepath-securejoin. For most users,there will be no change in behaviour aside from the type change (as the
bottom
0o777bits are the same in both formats, and most users are probablyonly using those bits).
However, if you were using
unix.S_ISVTXto set the sticky bit withMkdirAll(Handle)you will need to switch toos.ModeStickyotherwise youwill get a runtime error with this update. In addition, the error message you
will get from passing
unix.S_ISUIDandunix.S_ISGIDwill be different asthey are treated as invalid bits now (note that previously passing said bits
was also an error).
Thanks to the following contributors for helping make this release
possible:
Signed-off-by: Aleksa Sarai [email protected]
v0.3.6Compare Source
This release lowers the minimum Go version to Go 1.18 as well as some
library dependencies, in order to make it easier for folks that need to
backport patches using the new filepath-securejoin API onto branches
that are stuck using old Go compilers. For users using Go >= 1.21, this
release contains no functional changes.
The minimum Go version requirement for
filepath-securejoinis now Go 1.18(we use generics internally).
For reference,
[email protected]somewhat-arbitrarily bumped theGo version requirement to 1.21.
While we did make some use of Go 1.21 stdlib features (and in principle Go
versions <= 1.21 are no longer even supported by upstream anymore), some
downstreams have complained that the version bump has meant that they have to
do workarounds when backporting fixes that use the new
filepath-securejoinAPI onto old branches. This is not an ideal situation, but since using this
library is probably better for most downstreams than a hand-rolled
workaround, we now have compatibility shims that allow us to build on older
Go versions.
Lower minimum version requirement for
golang.org/x/systov0.18.0(weneed the wrappers for
fsconfig(2)), which should also make backportingpatches to older branches easier.
Signed-off-by: Aleksa Sarai [email protected]
v0.3.5Compare Source
This release primarily includes a fix for an issue involving two
programs racing to MkdirAll the same directory, which caused a
regression with BuildKit.
MkdirAllwill now no longer return anEEXISTerror if two racingprocesses are creating the same directory. We will still verify that the path
is a directory, but this will avoid spurious errors when multiple threads or
programs are trying to
MkdirAllthe same path. opencontainers/runc#4543Signed-off-by: Aleksa Sarai [email protected]
v0.3.4Compare Source
This release primarily includes a fix that blocked using
filepath-securejoin in Kubernetes.
import "testing"in non-
_test.gocode, which made some downstreams like Kubernetes unhappy.This has been fixed. (#32)
Thanks to all of the contributors who made this release possible:
Signed-off-by: Aleksa Sarai [email protected]
v0.3.3Compare Source
This release primarily includes fixes for spurious errors we hit when
checking that directories created by MkdirAll "look right". Upon further
consideration, these checks were fundamentally buggy and didn't offer
any practical protection anyway.
MkdirAllhas been removed. Thiswas originally intended to protect against some theoretical attacks but upon
further consideration these protections don't actually buy us anything and
they were causing spurious errors with more complicated filesystem setups.
MkdirAllhas also beenremoved. This was not causing us issues yet, but some pseudofilesystems (such
as
cgroup) create non-empty directories and so this logic would've beenwrong for such cases.
Thanks to all of the contributors who made this release possible:
Signed-off-by: Aleksa Sarai [email protected]
v0.3.2Compare Source
This release includes a few fixes for MkdirAll when dealing with S_ISUID
and S_ISGID, to solve a regression runc hit when switching to MkdirAll.
Passing the S_ISUID or S_ISGID modes to MkdirAllInRoot will now return
an explicit error saying that those bits are ignored by mkdirat(2). In
the past a different error was returned, but since the silent ignoring
behaviour is codified in the man pages a more explicit error seems
apt. While silently ignoring these bits would be the most compatible
option, it could lead to users thinking their code sets these bits
when it doesn't. Programs that need to deal with compatibility can
mask the bits themselves. (#23, #25)
If a directory has S_ISGID set, then all child directories will have
S_ISGID set when created and a different gid will be used for any
inode created under the directory. Previously, the "expected owner and
mode" validation in securejoin.MkdirAll did not correctly handle this.
We now correctly handle this case. (#24, #25)
Signed-off-by: Aleksa Sarai [email protected]
v0.3.1Compare Source
By allowing
Open(at)InRootto opt-out of the extra work done byMkdirAllto do the necessary "partial lookups",
Open(at)InRootnow does less workfor both implementations (resulting in a many-fold decrease in the number of
operations for
openat2, and a modest improvement for non-openat2) and isfar more guaranteed to match the correct
openat2(RESOLVE_IN_ROOT)behaviour.
We now use
readlinkat(fd, "")where possible. ForOpen(at)InRootthiseffectively just means that we no longer risk getting spurious errors during
rename races. However, for our hardened procfs handler, this in theory should
prevent mount attacks from tricking us when doing magic-link readlinks (even
when using the unsafe host
/prochandle). UnfortunatelyReopenis stillpotentially vulnerable to those kinds of somewhat-esoteric attacks.
Technically this will only work on post-2.6.39 kernels
but it seems incredibly unlikely anyone is using
filepath-securejoinon apre-2011 kernel.
Several improvements were made to the errors returned by
Open(at)InRootandMkdirAllwhen dealing with invalid paths under the emulated (ie.non-
openat2) implementation. Previously, some paths would return the wrongerror (
ENOENTwhen the last component was a non-directory), and other pathswould be returned as though they were acceptable (trailing-slash components
after a non-directory would be ignored by
Open(at)InRoot).These changes were done to match
openat2's behaviour and purely is aconsistency fix (most users are going to be using
openat2anyway).Signed-off-by: Aleksa Sarai [email protected]
v0.3.0Compare Source
This release contains no changes to SecureJoin.
However, it does introduce a new
*os.File-based API which is much saferto use for most usecases. These are adapted from libpathrs and are
the bare minimum to be able to operate more safely on an untrusted
rootfs where an attacker has write access (something that SecureJoin
cannot protect against). The new APIs are:
OpenInRoot, which resolves a path inside a rootfs and returns an
*os.Filehandle to the path. Note that the file handle returned byOpenInRoot is an O_PATH handle, which cannot be used for reading or
writing (as well as some other operations -- see open(2) for more
details).
Reopen, which takes an O_PATH file handle and safely re-opens it to
"upgrade" it to a regular handle.
MkdirAll, which is a safe implementation of os.MkdirAll that can be
used to create directory trees inside a rootfs.
As these are new APIs, it is possible they may change in the future.
However, they should be safe to start migrating to as we have extensive
tests ensuring they behave correctly and are safe against various races
and other attacks.
Signed-off-by: Aleksa Sarai [email protected]
v0.2.5Compare Source
This release makes some minor improvements to SecureJoin:
Some changes were made to how lexical components are handled during
resolution. There is no change in behaviour, and both implementations
are safe, however the newer implementation is much easier to reason
about.
The error returned when a symlink loop has been detected will now
reference the correct path. #10
Signed-off-by: Aleksa Sarai [email protected]
emicklei/go-restful (github.com/emicklei/go-restful/v3)
v3.12.2Compare Source
v3.12.1Compare Source
v3.12.0Compare Source
v3.11.3Compare Source
v3.11.2Compare Source
v3.11.1Compare Source
evanphx/json-patch (github.com/evanphx/json-patch)
v5.9.11+incompatibleCompare Source
v5.9.10+incompatibleCompare Source
v5.9.0+incompatibleCompare Source
v5.8.1+incompatibleCompare Source
v5.8.0+incompatibleCompare Source
fsnotify/fsnotify (github.com/fsnotify/fsnotify)
v1.9.0Compare Source
Changes and fixes
all: make BufferedWatcher buffered again (#657)
inotify: fix race when adding/removing watches while a watched path is being deleted (#678, #686)
inotify: don't send empty event if a watched path is unmounted (#655)
inotify: don't register duplicate watches when watching both a symlink and its target; previously that would get "half-added" and removing the second would panic (#679)
kqueue: fix watching relative symlinks (#681)
kqueue: correctly mark pre-existing entries when watching a link to a dir on kqueue (#682)
illumos: don't send error if changed file is deleted while processing the event (#678)
v1.8.0Compare Source
Additions
FSNOTIFY_DEBUGto print debug logs to stderr (#619)Changes and fixes
windows: fix behaviour of
WatchList()to be consistent with other platforms (#610)kqueue: ignore events with Ident=0 (#590)
kqueue: set O_CLOEXEC to prevent passing file descriptors to children (#617)
kqueue: emit events as "/path/dir/file" instead of "path/link/file" when watching a symlink (#625)
inotify: don't send event for IN_DELETE_SELF when also watching the parent (#620)
inotify: fix panic when calling Remove() in a goroutine (#650)
fen: allow watching subdirectories of watched directories (#621)
go-logr/logr (github.com/go-logr/logr)
v1.4.3Compare Source
Minor release.
What's Changed
New Contributors
Full Changelog: go-logr/logr@v1.4.2...v1.4.3
v1.4.2Compare Source
What's Changed
Dependencies:
Full Changelog: go-logr/logr@v1.4.1...v1.4.2
go-openapi/jsonpointer (github.com/go-openapi/jsonpointer)
v0.21.1Compare Source
v0.21.0Compare Source
v0.20.3Compare Source
v0.20.2Compare Source
v0.20.1Compare Source
v0.20.0Compare Source
go-openapi/jsonreference (github.com/go-openapi/jsonreference)
v0.21.0Compare Source
v0.20.5Compare Source
v0.20.4Compare Source
v0.20.3Compare Source
go-openapi/swag (github.com/go-openapi/swag)
v0.23.1Compare Source
v0.23.0Compare Source
v0.22.10Compare Source
v0.22.9Compare Source
v0.22.8Compare Source
v0.22.7Compare Source
v0.22.6Compare Source
v0.22.5Compare Source
v0.22.4Compare Source
google/gnostic-models (github.com/google/gnostic-models)
v0.6.9Compare Source
google/go-cmp (github.com/google/go-cmp)
v0.7.0Compare Source
New API:
Panic messaging:
huandu/xstrings (github.com/huandu/xstrings)
v1.5.0: API Change: New APIToPascalCaseand makeToCamelCasecamelCaseCompare Source
Per discuss in #56, I decide to change the result of
ToCamelCaseto make it align with common sense. In the past,ToCamelCaseconvertscamel_case_stringtoCamelCaseString, in which the first letter is upper case; Starting from this release,ToCamelCasereturnscamelCaseStringinstead. If we want to convert string to "upper" camel case, we can use new APIToPascalCase.If you have any concern, please feel free to send issue to me. Thanks.
Full Changelog: huandu/xstrings@v1.4.0...v1.5.0
mailru/easyjson (github.com/mailru/easyjson)
v0.9.0Compare Source
up go version and bugfixes
v0.8.0Compare Source
stable version before go version bump
moby/spdystream (github.com/moby/spdystream)
v0.5.0: [v0.5.0] Avoid leaking timeout timer channels and update github actionsCompare Source
What's Changed
Full Changelog: moby/spdystream@v0.4.0...v0.5.0
v0.4.0: [v0.4.0] fix goroutine leak and remove unused codeCompare Source
What's Changed
New Contributors
Full Changelog: moby/spdystream@v0.3.0...v0.4.0
v0.3.0: [v0.3.0] Release with fixes for a race conditionCompare Source
What's Changed
New Contributors
Full Changelog: moby/spdystream@v0.2.0...v0.3.0
prometheus/client_golang (github.com/prometheus/client_golang)
v1.22.0: - 2025-04-07Compare Source
zstdsupport introduce in #1496Experimental support for
zstdon scrape was added, controlled by the requestAccept-Encodingheader.It was enabled by default since version 1.20, but now you need to add a blank import to enable it.
The decision to make it opt-in by default was originally made because the Go standard library was expected to have default zstd support added soon,
https://github.com/golang/go/issues/62513 however, the work took longer than anticipated and it will be postponed to upcoming major Go versions.
e.g.:
WithLookbackDeltaandWithStatsoptions have been added to API client. #1743All Changes
Configuration
📅 Schedule: Branch creation - "after 5am on sunday" in timezone Asia/Shanghai, Automerge - At any time (no schedule defined).
🚦 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.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
To execute skipped test pipelines write comment
/ok-to-test.This PR has been generated by MintMaker (powered by Renovate Bot).