Update all dependencies - #116
Open
bootc-bot[bot] wants to merge 1 commit into
Open
Conversation
Signed-off-by: bootc-bot[bot] <225049296+bootc-bot[bot]@users.noreply.github.com> Signed-off-by: bootc-bot[bot] <225049296+bootc-bot[bot]@users.noreply.github.com>
Contributor
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
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.32.0→v2.32.1v1.9.4→v1.10.0v0.69.0→v0.69.1v6.0.2→v6.1.0Release Notes
onsi/ginkgo (github.com/onsi/ginkgo/v2)
v2.32.1Compare Source
2.32.1
Fixes
e647b3b]sirupsen/logrus (github.com/sirupsen/logrus)
v1.10.0Compare Source
Logrus v1.10.0
This release focuses on substantial performance improvements, concurrency correctness, and better interoperability with modern Go logging APIs.
🚀 Performance
Major improvements across
TextFormatter, entry handling, and common logger paths:WithErroris ~40% fasterTextFormatterpaths are up to ~40% fasterTextFormattercases, with the largest reductions in colored outputThe improvements also show up in complete logger paths:
TextFormatteris ~31% faster, with ~24% fewer allocationsJSONFormatteris ~21% faster, with ~10% fewer allocationsJSONFormatteritself remains largely unchanged in runtime performance, with small allocation reductions.🔄
log/sloginteroperabilityv1.10 adds bidirectional interoperability between Logrus and Go's
log/slog:sloghook can forward existing Logrus entries to ansloglogger.hooks/slog.NewHandlerimplementsslog.Handler, allowinglog/slogrecords to use an existing Logrus logger and its hooks, formatter, and output.ReportCalleroption.sloglevels can be mapped to Logrus levels.log/slogwithout requiring an all-at-once transition.This allows applications to migrate their logging API and logging backend independently: existing Logrus call sites can start using an
slogbackend, while newslogcode can continue using an established Logrus setup.🔒 Concurrency & Correctness
MarshalJSONor formatter code.Log,Logf,Logln, andLogFnmethods unexpectedly panicking when called withPanicLevel, contrary to their documented behavior.➕ Added
TextFormatternow automatically enables colors on Windows terminals with ANSI support, matching behavior on other platforms.Entry.Callercan now be set explicitly and is preserved across derived entries. When caller reporting is enabled, Logrus only detects and populates caller information when none was provided, allowing custom caller detection and wrapper-aware logging without adding additional caller configuration APIs.TextFormatternow renders[]byteas raw/quoted strings instead of numeric slices.If you relied on the previous slice-of-ints output, convert explicitly before logging.
TextFormatternow uses dim cyan for debug output and dim white for trace output in colorized TTY output.Entry.HasCalleris now deprecated in favor of checkingEntry.Callerdirectly. A//go:fix inlinedirective was added so existing uses can be updated automatically.MutexWrap, which was unintentionally exposed as public API, is deprecated. It remains available as an alias for compatibility but should not be used directly.v1.10 is primarily a performance, correctness, and interoperability release with no intentional breaking public API changes.
Benchmarks (sampled at 457e372460c7a80ca7c800b51ebeee5362aaa180)
Full Changelog: sirupsen/logrus@v1.9.4...v1.10.0
podman-container-tools/podman (go.podman.io/podman/v6)
v6.1.0Compare Source
Features
podman volume rename, to allow renaming volumes. Volumes created using volume drivers and volumes that are currently used by a container cannot be renamed (#28189).podman machine restart, to allow easy restart of VMs managed bypodman machine(#28366).podman network rmcommand now includes a new option,--ignore, which suppresses errors when attempting to remove networks that do not exist (#28363).podman manifest pushcommand now includes two new options,--retryand--retry-delay, which allow pushes to be automatically retried on failure (#28590)..containerunits now support a new key,ImageVolume=, to configure how volumes from images are handled (#28875).podman generate kubecommand now includes support for generating container healthchecks as alivenessProbe(#22095).force_port_listen, has been added tocontainers.conf. This is required to be set when running Podman on WSL to support port forwarding from the Windows host. It is automatically set on newly-createdpodman machineVMs on Windows using the WSL provider.Changes
podman infocommand now includes free memory available on the host (in addition to used memory and total memory) (#29116).Bugfixes
podman image scpcommand could not be used with usernames containing an@character (#27655).podman kube playcommand did not properly validate requestedhostPortbindings, allowing the creation of containers with duplicated host ports which would never be able to start at the same time (#26622).podman machineVMs on Windows created using thehypervprovider would sometimes not properly start due to a race conditioning setting up volume mounts.podman machineVMs on Mac where machines could be left in an inconsistent state if thepodman machine startcommand was interrupted by a signal.podman machineVM on Mac that attempted to bind to a port number number 1024 would return a nonsensical error message; a clear error explaining that privileged ports cannot be bound is now returned.podman quadlet listandpodman quadlet rmcommands did not function properly with uninstantiated template Quadlets.podman quadlet installcommand would occasionally fail to install a Quadlet if non-quadlet files were specified.podman quadlet installcommand would not refuse to install Quadlets including non-quadlet files if the--applicationoption was not specified.podman volume prune --allcommand incorrectly discarded label filters, causingpodman volume prune --all --filter label=footo prune all volumes, not just those with thefoolabel.podman events --format=jsoncommand would printnullinstead of an error when the server sent an event that could not be decoded.podman inspectcommand on a container with a single-element command (e.g.podman run fedora bash) would include the command in bothPathandArgs, when it should only have been included inPath(#29155).--formatoption topodman inspecton containers did not properly support some format specifiers supported by Docker (e.g.{{.HostIp}}did not work, but{{.HostIP}}did) (#29164).STDERRbut only to/dev/kmsg, meaning that errors were not visible fromsystemd-analyze --generators verifyand other tooling invoking the systemd generator directly.podman kube generatecommand would improperly generate warning messages only applicable when running as a rootless user on an SELinux enabled system when not running in that configuration (#17743).API
/containers/$CID/exec) did not honor theConsoleSizeparameter in the exec config.Misc
Configuration
📅 Schedule: (in timezone UTC)
🚦 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 Mend Renovate CLI.