Repository navigation
fix(deps): update go direct - autoclosed - #166
Closed
bootc-bot[bot] wants to merge 1 commit into
Closed
bootc-bot[bot] wants to merge 1 commit into
bootc-bot[bot] wants to merge 1 commit into
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:
v6.1.4→v6.2.0v0.58.0→v0.59.0v0.47.0→v0.48.0Release Notes
podman-container-tools/podman (go.podman.io/podman/v6)
v6.2.0Compare Source
Security
Features
podman pushcommand now supports a new option,--platform, which selects and pushes a single platform-specific manifest instead of the entire list.podman kube playcommand now supports a new option,--validate, which determines how unrecognized YAML fields are handled (#18332).podman kube playcommand now supports a new option,--label, to set labels on created containers, pods, volumes, and secrets (#26450).podman kube playcommand can now create multiple pods if more than 1 replica is requested by a deployment using the new--multiple-podsoption (#26769).podman kube play --buildcommand now supports building images from subdirectories of the main context directory (#28148)..containerfiles now support a new key,Umask, to set the default umask for the created container (#25278).SetMountsDependency, configuring whether the generated unit will useRequiresMountsFor,WantsMountsFor, or no dependency at all on required source paths (#29946).podman farm listcommand now supports two new options,--quiet, which will print only the names of active farms, and--noheading, which omits column headers from the output.podman artifact lscommand now supports two new options,--format=json, which will output machine-readable JSON, and--quiet, which prints only artifact digests.podman createcommand now supports a new option,--passwd, to add entries to/etc/passwdin the container (this has previously been available withpodman run).podman infocommand now includes detailed information on the features supported by OCI runtimes.podman events --filtercommand now supports a new filter,network=, to filter to events pertaining to a specific network (#29387).podman auto-updatecommand has been enabled on the remote Podman client.StartIntervalfield in image healthcheck configuration is now respected, allowing images to configure startup healthchecks (#27724).podman image scpcommand now supports two new options,--compression-formatand--compression-level, to compress data during transfer (#23192).podman auto-updatecommand now supports a new option,--filter, to selectively update only containers that match the given filters.podman ps --sortcommand now allows sorting by pod.podman ps --filtercommand now supports a new filter,status!, which matches containers not in the given state (#21398).Changes
podman kube playcommand now uses thesecurityContext.seccompProfilefields in Kubernetes YAML for Seccomp configuration. Support for the existing annotation-based configuration of Seccomp is now deprecated, and will be removed with Podman 7.0.podman inspectcommand on containers now includes three new fields,DNSNames(containing all names the container can be accessed via),IsInitCtr(whether the container is an init container), andInitContainerType(what type of init container this is, if it is one) (#29811).podman inspectcommand on containers now only includes user-added DNS aliases in theAliasesfield, which previously displayed all DNS aliases, improving Docker compatibility.podman inspectcommand on containers now properly populates theConsoleSizefield for running containers (#28368).libpod-healthcheck-$CONTAINERID-$randsuffix.service) (#29373).podman execcommands. As such, killing apodman execcommand with Control-C or similar should now also kill the processes started in the container (similar to howpodman runalready works) (#19486).--cpu-rt-periodand--cpu-rt-runtimeoptions forpodman create,podman run,podman update, andpodman container cloneare now hidden and undocumented. They have not been functional since the removal of cgroups v1 support and will be removed entirely in Podman v7.--health-startup-intervaloption topodman create,podman run, andpodman updatehas a new alias,--health-start-interval.journaldevent driver, timestamps are no longer included in logged events, asjournaldincludes a timestamp already (#29835).Bugfixes
--ignorefileoption topodman buildwould cause the.dockerignoreor.containerignorefile in the context directory to be used, instead of not using an ignorefile at all (#25147).Pod=key in Quadlet.containerfiles did not expand the%Nspecifier (#29108).--userns=autowould report having aprivateuser namespace inpodman inspectafter they started, but not when they were first created.podman system prune --buildcommand could fail if a build container was removed while it was running.copyevents frompodman machine cpwere not properly displayed by the remote Podman client.podman farm build --tagcommand would fail if given a tag including a colon (#25039).podman machine init --imagecommand would fail when given a read-only disk image.podman machine startandpodman machine init --nowcommands could hang on Windows systems using the Hyper-V provider if the VM failed to start (#29455).podman machine startcommand on Windows (both Hyper-V and WSL providers) would sometimes fail due to leftover processes from previous machines (#29474).podman machine startcommand could hang indefinitely if the VM failed to start properly (#29880).podman machine startcommand could create a VM that cannot be connected to on Windows if the host was shut down or restarted when the VM was running (#29971).podman machine initcommand on Windows when using the Hyper-V provider did not correctly detach the file server process, causing VMs to lose access to host shares when the console that ranpodman machine initclosed (#29573).podman kube playcommand incorrectly handledemptyDirvolumes withmedium: Memory, causing them to not be shared between containers in the pod and to ignore thesizeLimitparameter (#29555).podman kube playcommand incorrectly handled authentication credentials in API requests.podman volume importcommand would not adjust their permissions on being mounted into a container (#25442).podman buildcommand could leak temporary directories if a build failed (#22642).--userns=keep-idwould use an image-specified user instead of forcing the same UID/GID in use on the host (#29600).podman push,podman artifact push, andpodman manifest pushcommands would push an unsigned image instead of failing when the--sign-byor--sign-by-sigstore-private-keyoptions were used.--userns=autothat had overlay volume mounts would fail (#28758).=character in the path were handled incorrectly.podman manifest annotate --subjectandpodman manifest add --artifact subjectcommands.podman manifest add --artifactcommand could hang under some circumstances.podman manifest annotate --os-featurescommand did not properly save the OS features in the manifest.podman image prune --filterdid not correctly handle filters with values including the=character..volumeunits did not recreate the volume if it was removed in Podman (#27862).--sdnotify=healthyand aHealthStartPeriodlonger than the unit'sTimeoutStartSeccould be automatically killed by systemd if the healthcheck took an extended period to become healthy (#27290).--pids-limit=0argument topodman runandpodman createwas incorrectly setting a process limit, instead of removing the limit, when theruncOCI runtime was in use (#29826).podman psandpodman pod pscommands would fail when the--formatargument was used with a format string including.Label(#29831).podman cpcommand did not respect volume subpaths when copying into a mounted named or image volumes in a container that is not running (#29840 and #29857).podman exportcommand, when run by a rootless user on a container created with--userns=keep-id, would create an archive with incorrect UIDs and GIDs (#29856).podman system servicecommand would fail to start when run as a systemd unit and autostarted at the same time as other Podman units (#29964).podman eventscommand would return incomplete output when using thefileevents backend and--untilspecified with a time in the past (#29579).podman updatecommand allowed setting a startup healthcheck on a container without a normal healthcheck.podman secret rmcommand would fail when given an ambiguous name that could match multiple possible secrets.podman machine infocommand would report the default VM type and config/image directories, not those used by the current machine.podman inspectcommand on containers did not includeCheckpointLogafter a failed container checkpoint (#25154).API
POST /libpod/autoupdate, which automatically updates containers with theio.containers.autoupdatelabel.GET /distribution/{name}/json, which inspects an image on a registry (#17726).HostConfig.Mounts.TmpfsOptions.Options, to set additional options for tmpfs mounts.HostConfig.SecurityOptfield (instead of a path to a file containing a profile), improving Docker compatibility (#27710).platform, to push only a single platform-specific manifest instead of the entire list.autouserns mode also specify full UID/GID mappings for the created container.{}as the user explicitly requesting no healthcheck, instead of using the image's healthcheck as Docker does (#29467).showsecretquery parameter, which should be restricted to Libpod API requests only (#29570).Createdfield even when it was empty.IPRangein the returnedIPAMConfig(#28378).deadandrestarting) (#28904).system_cpu_usageandpercpu_statswhen not streaming (#28761, #24730, #25709, #29912).cgroupfscgroup manager (#27824).stream=0andlogs=1) attach, incorrectly reinitialize the container, changing its exit code and status (#29664).Detach=true.Misc
gvproxyto start when starting apodman machineVM now uses a notification socket, instead of polling, improving reliability and startup time.--image-volumeoption topodman createandpodman runto remove the deprecatedbindoption and add the new default,anonymous, which was not shown as a valid option. Using the deprecatedbindoption now prints a warning.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.