fix(deps): update gomod dependencies#445
fix(deps): update gomod dependencies#445red-hat-konflux-kflux-prd-rh03[bot] wants to merge 1 commit into
Conversation
red-hat-konflux-kflux-prd-rh03
Bot
added
approved
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
openshift-ci
Bot
added
the
needs-ok-to-test
|
Hi @red-hat-konflux-kflux-prd-rh03[bot]. Thanks for your PR. I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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. |
|
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: red-hat-konflux-kflux-prd-rh03[bot] The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
1 similar comment
|
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: red-hat-konflux-kflux-prd-rh03[bot] The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/ok-to-test |
openshift-ci
Bot
added
ok-to-test
red-hat-konflux-kflux-prd-rh03
Bot
force-pushed
the
konflux/mintmaker/master/gomod-dependencies
branch
from
fc39227 to
ac70c68
Compare
|
New changes are detected. LGTM label has been removed. |
red-hat-konflux-kflux-prd-rh03
Bot
force-pushed
the
konflux/mintmaker/master/gomod-dependencies
branch
3 times, most recently
from
2a4ce19 to
0c3b39a
Compare
|
@red-hat-konflux-kflux-prd-rh03[bot]: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
Signed-off-by: red-hat-konflux-kflux-prd-rh03 <206760901+red-hat-konflux-kflux-prd-rh03[bot]@users.noreply.github.com>
red-hat-konflux-kflux-prd-rh03
Bot
force-pushed
the
konflux/mintmaker/master/gomod-dependencies
branch
from
0c3b39a to
02bb451
Compare
1 participant
This PR contains the following updates:
v2.2.0→v2.3.0v3.9.0→v3.13.0v5.6.0+incompatible→v5.9.11+incompatiblev5.6.0→v5.9.11v1.6.0→v1.10.1v1.2.4→v1.4.3v1.2.4→v1.3.0v0.19.6→v0.23.1v0.20.1→v0.21.6v0.22.3→v0.26.141bb18b→2c02b82v1.5.3→v1.5.4v0.6.9→v0.7.1v0.6.0→v0.7.04bb14d4→7023385v1.3.0→v1.6.0v0.3.13→v0.3.16v0.7.7→v0.9.2v0.2.0→v0.5.1v2.9.5→v2.31.0v2.32.0v1.27.7→v1.42.0a83e6f8→534616177b8897→5346161v0.5.0→v0.5.11b1a774→751e0d2v0.11.0→v0.19.0v0.58.0→v0.92.0v0.58.0→v0.92.0v1.15.1→v1.23.2v0.4.0→v0.6.2v0.43.0→v0.69.0v0.9.0→v0.20.1v1.0.5→v1.0.10v1.8.2→v1.11.1v1.7.0→v1.11.0v1.6.0→v1.11.0v1.24.0→v1.28.0v0.38.0→v0.56.0v0.27.0→v0.36.0v0.31.0→v0.46.0v0.30.0→v0.44.0v0.23.0→v0.38.0v0.3.0→v0.15.0v0.21.1-0.20240508182429-e35e4ccd0d2d→v0.46.0v2.3.0→v2.5.0v1.33.0→v1.36.11v0.27.2→v0.36.2v0.27.2→v0.36.2v0.27.2→v0.36.2v0.27.2→v0.36.2v0.27.2→v0.36.2v2.90.1→v2.140.08b0f38b→bc653b6a36077c→a95e086v0.15.0→v0.24.1v0.2.0→v0.7.0c049b76→2d32026bc3834c→2d32026v4.2.3→v4.7.0v1.3.0→v1.6.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
cespare/xxhash (github.com/cespare/xxhash/v2)
v2.3.0Compare Source
emicklei/go-restful (github.com/emicklei/go-restful/v3)
v3.13.0Compare Source
v3.12.2Compare Source
v3.12.1Compare Source
v3.12.0Compare Source
v3.11.3Compare Source
v3.11.2Compare Source
v3.11.1Compare Source
v3.11.0Compare Source
v3.10.2Compare Source
see comment in Readme how to customize this behaviour.
v3.10.1Compare Source
v3.10.0Compare 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
v5.7.0+incompatibleCompare Source
fsnotify/fsnotify (github.com/fsnotify/fsnotify)
v1.10.1Compare Source
Changes and fixes
inotify: don't remove sibling watches sharing a path prefix (#754)
inotify, windows: don't rename sibling watches sharing a path prefix
(#755)
v1.10.0Compare Source
This version of fsnotify needs Go 1.23.
Changes and fixes
inotify: improve initialization error message (#731)
inotify: send Rename event if recursive watch is renamed (#696)
inotify: avoid copying event buffers when reading names (#741)
kqueue: skip dangling symlinks (ENOENT) in watchDirectoryFiles, so a bad entry no longer aborts Watcher.Add for the whole directory (#748)
kqueue: drop watches directly in Close() to fix a file descriptor leak when recycling watchers (#740)
windows: fix nil pointer dereference in remWatch (#736)
windows: lock watch field updates against concurrent WatchList to fix a race introduced in v1.9.0 (#709, #749)
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)
v1.7.0Compare Source
This version of fsnotify needs Go 1.17.
Additions
illumos: add FEN backend to support illumos and Solaris. (#371)
all: add
NewBufferedWatcher()to use a buffered channel, which can be useful in cases where you can't control the kernel buffer and receive a large number of events in bursts. (#550, #572)all: add
AddWith(), which is identical toAdd()but allows passing options. (#521)windows: allow setting the ReadDirectoryChangesW() buffer size with
fsnotify.WithBufferSize(); the default of 64K is the highest value that works on all platforms and is enough for most purposes, but in some cases a highest buffer is needed. (#521)Changes and fixes
inotify: remove watcher if a watched path is renamed (#518)
After a rename the reported name wasn't updated, or even an empty string. Inotify doesn't provide any good facilities to update it, so just remove the watcher. This is already how it worked on kqueue and FEN.
On Windows this does work, and remains working.
windows: don't listen for file attribute changes (#520)
File attribute changes are sent as
FILE_ACTION_MODIFIEDby the Windows API, with no way to see if they're a file write or attribute change, so would show up as a fsnotify.Write event. This is never useful, and could result in many spurious Write events.windows: return
ErrEventOverflowif the buffer is full (#525)Before it would merely return "short read", making it hard to detect this error.
kqueue: make sure events for all files are delivered properly when removing a watched directory (#526)
Previously they would get sent with
""(empty string) or"."as the path name.kqueue: don't emit spurious Create events for symbolic links (#524)
The link would get resolved but kqueue would "forget" it already saw the link itself, resulting on a Create for every Write event for the directory.
all: return
ErrClosedonAdd()when the watcher is closed (#516)other: add
Watcher.ErrorsandWatcher.Eventsto the no-opWatcherinbackend_other.go, making it easier to use on unsupported platforms such as WASM, AIX, etc. (#528)other: use the
backend_other.gono-op if theappenginebuild tag is set; Google AppEngine forbids usage of the unsafe package so the inotify backend won't compile there.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
v1.4.1Compare Source
What's Changed
Full Changelog: go-logr/logr@v1.4.0...v1.4.1
v1.4.0Compare Source
This release dramatically improves interoperability with Go's
log/slogpackage. In particular,logr.NewContextandlogr.NewContextWithSlogLoggeruse the same context key, which allowslogr.FromContextandlogr.FromContextAsSlogLoggerto returnlogr.Loggeror*slog.Loggerrespectively, including transparently converting each to the other as needed.Functions
logr/slogr.NewLograndlogr/slogr.ToSlogHandlerhave been superceded bylogr.FromSlogHandlerandlogr.ToSlogHandlerrespectively, and typelogr/slogr.SlogSinkhas been superceded bylogr.SlogSink. All of the old names inlogr/slogrremain, for compatibility.Package
logr/funcrnow supportslogr.SlogSink, meaning that it's output passes all but one of the Slog conformance tests (that exception being thatfuncrhandles the timestamp itself).Users who have a
logr.Loggerand need a*slog.Loggercan callslog.New(logr.ToSlogHandler(...))and all output will go through the same stack.Users who have a
*slog.Loggerorslog.Handlercan 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.0Compare Source
This release adds support for slog in a new, self-contained
logr/slogrpackage. Implementers of alogr.LogSinkare encouraged, but not required, to extend their implementation to improve the quality of log output coming from aslogAPI call.Breaking change: the call depth for
LogSink.Enabledwhen called viaLogger.Enabledwas fixed to be the same as for other call paths. Implementers of aLogSinkwho 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-logr/zapr (github.com/go-logr/zapr)
v1.3.0Compare Source
This release adds support for slog. zapr implements
slogr.SlogSinkand therefore can be used throughslogr.NewSlogHandleras backend for slog.What's Changed
Configuration
📅 Schedule: Branch creation - Between 02:00 AM and 04:59 AM, Monday through Friday ( * 2-4 * * 1-5 ) in timezone UTC, Automerge - Between 02:00 AM and 04:59 AM, Monday through Friday ( * 2-4 * * 1-5 ) in timezone UTC.
🚦 Automerge: Enabled.
♻ 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.Documentation
Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.