Skip to content

Update all dependencies#119

Open
bootc-bot[bot] wants to merge 1 commit intomainfrom
bootc-renovate/all
Open

Update all dependencies#119
bootc-bot[bot] wants to merge 1 commit intomainfrom
bootc-renovate/all

Conversation

@bootc-bot
Copy link
Contributor

@bootc-bot bootc-bot bot commented Sep 8, 2025 •
edited
Loading

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
github.com/adrg/xdg v0.4.0 → v0.5.3 age confidence
github.com/containers/gvisor-tap-vsock v0.7.3 → v0.8.8 age confidence
github.com/distribution/reference v0.5.0 → v0.6.0 age confidence
github.com/gofrs/flock v0.8.1 → v0.13.0 age confidence
github.com/onsi/ginkgo/v2 v2.17.1 → v2.28.1 age confidence
github.com/onsi/gomega v1.32.0 → v1.39.1 age confidence
github.com/sirupsen/logrus v1.9.3 → v1.9.4 age confidence
github.com/spf13/cobra v1.8.0 → v1.10.2 age confidence
golang.org/x/sys v0.26.0 → v0.41.0 age confidence
golang.org/x/term v0.25.0 → v0.39.0 age confidence
libvirt.org/go/libvirt v1.10002.0 → v1.11010.0 age confidence

Release Notes

adrg/xdg (github.com/adrg/xdg)

v0.5.3

Compare Source

Changelog
  • Updated xdg.SearchRuntimeFile to also look in the operating system's temporary directory for runtime files.
    This covers unlikely cases in which runtime files cannot be written relative to the base runtime directory either because it does not exist or it is not accessible, so xdg.RuntimeFile suggests the operating system's temporary directory as a suitable fallback location.
Internal
  • Improved package testing.

v0.5.2

Compare Source

Changelog

  • Updated logic of xdg.RuntimeFile: due to the special nature of the runtime directory, the function no longer attempts to create it if it does not exist. If that's the case, the function uses the operating system's temporary directory as a fallback. The function still creates subdirectories relative to the base runtime directory or its fallback.

    Justification: the creation of the runtime directory is not in the scope of this package as it has special requirements defined by the XDG Base Directory Specification. Relevant excerpt:

    The lifetime of the directory MUST be bound to the user being logged in. It MUST be created when the user first logs in and if the user fully logs out the directory MUST be removed. If the user logs in more than once they should get pointed to the same directory, and it is mandatory that the directory continues to exist from their first login to their last logout on the system, and not removed in between. Files in the directory MUST not survive reboot or a full logout/login cycle.

    Also, on Linux, the parent directories of the default user runtime directory are owned by the root user so they cannot be created by a regular user. pam_systemd is usually responsible for creating the runtime directory (/run/user/$UID).

v0.5.1

Compare Source

Changelog
  • Added support for the non-standard XDG_BIN_HOME base directory.
    See XDG base directories README section for more details.
  • Added more config and data search locations on macOS.
    • Added ~/.config at the end of the list of default locations for XDG_CONFIG_DIRS.
    • Added ~/.local/share at the end of the list of default locations for XDG_DATA_DIRS.
  • Added more application search locations on Windows:
    • %ProgramFiles%
    • %ProgramFiles%\Common Files
    • %LOCALAPPDATA%\Programs
    • %LOCALAPPDATA%\Programs\Common
Internal
  • Updated golang.org/x/sys dependency to the latest version.
  • Improved package testing.

v0.5.0

Compare Source

Changelog
  • user-dirs.dirs config file is now parsed on Unix-like operating systems (except for macOS and Plan 9).
    See XDG user directories README section for more details.
  • Updated golang.org/x/sys dependency to the latest version.
Internal
  • Moved all path related functionality in internal pathutil package.
  • Added internal userdirs package:
    • Moved xdg.UserDirectories to userdirs.Directories.
    • Added parsing functions for user-dirs.dirs config file.
  • Improved package testing.
containers/gvisor-tap-vsock (github.com/containers/gvisor-tap-vsock)

v0.8.8

Compare Source

What's Changed

Dependencies Updates

New Contributors

Full Changelog: containers/gvisor-tap-vsock@v0.8.7...v0.8.8

v0.8.7

Compare Source

What's Changed

Dependency Updates

New Contributors

Full Changelog: containers/gvisor-tap-vsock@v0.8.6...v0.8.7

v0.8.6

Compare Source

The main change in this release is a slight change of behaviour with the gvproxy --debug option. In previous releases, it was creating a capture.pcap file in gvproxy’s working directory. This was problematic for some users, as if this directory is not writable, gvproxy exits with an error.

Starting with 0.8.6, --debug will no longer dump network traffic automatically. If you need network traffic dumps, there’s a new --pcap option, and the path where to dump the data is configurable.

If this behaviour change is problematic for you, please file an issue so that we can revisit this in future releases.

What's Changed

Dependency Updates

Full Changelog: containers/gvisor-tap-vsock@v0.8.5...v0.8.6

v0.8.5

Compare Source

What's Changed

Full Changelog: containers/gvisor-tap-vsock@v0.8.4...v0.8.5

v0.8.4

Compare Source

What's Changed

Full Changelog: containers/gvisor-tap-vsock@v0.8.3...v0.8.4

v0.8.3

Compare Source

What's Changed

Dependencies updates

Full Changelog: containers/gvisor-tap-vsock@v0.8.2...v0.8.3

v0.8.2

Compare Source

What's Changed

Dependencies updates

New Contributors

Full Changelog: containers/gvisor-tap-vsock@v0.8.1...v0.8.2

v0.8.1

Compare Source

This release fixes a few regressions in the DNS code introduced in v0.8.0, and a race condition in one of our test cases.
There are also a few dependencies updates.

What's Changed

Dependency updates

New Contributors

Full Changelog: containers/gvisor-tap-vsock@v0.8.0...v0.8.1

v0.8.0

Compare Source

What's Changed

Dependency Updates

New Contributors

Full Changelog: containers/gvisor-tap-vsock@v0.7.5...v0.8.0

v0.7.5

Compare Source

This release fixes a podman regression: containers/podman#23616

What's Changed

Dependency updates

Full Changelog: containers/gvisor-tap-vsock@v0.7.4...v0.7.5

v0.7.4

Compare Source

What's Changed

Dependency Updates

New Contributors

Full Changelog: containers/gvisor-tap-vsock@v0.7.3...v0.7.4

distribution/reference (github.com/distribution/reference)

v0.6.0

Compare Source

What's Changed

New Contributors

Full Changelog: distribution/reference@v0.5.0...v0.6.0

gofrs/flock (github.com/gofrs/flock)

v0.13.0

Compare Source

What's Changed

Minimum Go version 1.24

  • feat: add Stat method by @​ferhatelmas in #​127
  • chore(deps): bump golang.org/x/sys from 0.22.0 to 0.37.0

Full Changelog: gofrs/flock@v0.12.1...v0.13.0

v0.12.1

Compare Source

What's Changed

New Contributors

Full Changelog: gofrs/flock@v0.12.0...v0.12.1

v0.12.0

Compare Source

What's Changed

  • feat: differentiation of Solaris and Illumos by @​ldez in #​80
  • feat(windows): replace custom implementation with golang.org/x/sys/windows by @​ldez in #​81
  • fix: update fnctl implementation by @​ldez in #​84
  • feat: use runtime errors instead of compilation errors for unsupported platforms by @​ldez in #​85
  • refactor: use x/sys/* instead of Syscall when possible by @​ldez in #​87

Full Changelog: gofrs/flock@v0.11.0...v0.12.0

v0.11.0

Compare Source

What's Changed

  • feat: add options to define flag and permissions of the file by @​ldez in #​76
  • tests: remove files generated during tests by @​ldez in #​77

Full Changelog: gofrs/flock@v0.10.0...v0.11.0

v0.10.0

Compare Source

What's Changed

New Contributors

Full Changelog: gofrs/flock@v0.9.0...v0.10.0

v0.9.0

Compare Source

What's Changed

New Contributors

Full Changelog: gofrs/flock@v0.8.1...v0.9.0

onsi/ginkgo (github.com/onsi/ginkgo/v2)

v2.28.1

Compare Source

2.28.1

Update all dependencies. This auto-updated the required version of Go to 1.24, consistent with the fact that Go 1.23 has been out of support for almost six months.

v2.28.0

Compare Source

2.28.0

Ginkgo's SemVer filter now supports filtering multiple components by SemVer version:

It("should work in a specific version range (1.0.0, 2.0.0) and third-party dependency redis in [8.0.0, ~)", SemVerConstraint(">= 3.2.0"), ComponentSemVerConstraint("redis", ">= 8.0.0") func() {
    // This test will only run when version is between 1.0.0 (exclusive) and 2.0.0 (exclusive) and redis version is >= 8.0.0
})

can be filtered in or out with an invocation like:

ginkgo --sem-ver-filter="2.1.1, redis=8.2.0"

Huge thanks to @​Icarus9913 for working on this!

v2.27.5

Compare Source

2.27.5

Fixes

Don't make a new formatter for each GinkgoT(); that's just silly and uses precious memory

v2.27.4

Compare Source

2.27.4

Fixes
  • CurrentTreeConstructionNodeReport: fix for nested container nodes [59bc751]

v2.27.3

Compare Source

2.27.3

Fixes

report exit result in case of failure [1c9f356]
fix data race [ece19c8]

v2.27.2

Compare Source

2.27.2

Fixes
  • inline automaxprocs to simplify dependencies; this will be removed when Go 1.26 comes out [a69113a]
Maintenance
  • Fix syntax errors and typo [a99c6e0]
  • Fix paragraph position error [f993df5]

v2.27.1

Compare Source

2.27.1

Fixes
  • Fix Ginkgo Reporter slice-bounds panic [606c1cb]
  • Bug Fix: Add GinkoTBWrapper.Attr() and GinkoTBWrapper.Output() [a6463b3]

v2.27.0

Compare Source

2.27.0

Features
Transforming Nodes during Tree Construction

This release adds support for NodeArgsTransformers that can be registered with AddTreeConstructionNodeArgsTransformer.

These are called during the tree construction phase as nodes are constructed and can modify the node strings and decorators. This enables frameworks built on top of Ginkgo to modify Ginkgo nodes and enforce conventions.

Learn more here.

Spec Prioritization

A new SpecPriority(int) decorator has been added. Ginkgo will honor priority when ordering specs, ensuring that higher priority specs start running before lower priority specs

Learn more here.

Maintenance

v2.26.0

Compare Source

2.26.0

Features

Ginkgo can now generate json-formatted reports that are compatible with the go test json format. Use ginkgo --gojson-report=report.go.json. This is not intended to be a replacement for Ginkgo's native json format which is more information rich and better models Ginkgo's test structure semantics.

v2.25.3

Compare Source

2.25.3

Fixes
  • emit --github-output group only for progress report itself [f01aed1]

v2.25.2

Compare Source

2.25.2

Fixes

Add github output group for progress report content

Maintenance

Bump Gomega

v2.25.1

Compare Source

2.25.1

Fixes
  • fix(types): ignore nameless nodes on FullText() [10866d3]
  • chore: fix some CodeQL warnings [2e42cff]

v2.25.0

[

Configuration

📅 Schedule: Branch creation - "on sunday" in timezone UTC, 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.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@bootc-bot
Copy link
Contributor Author

bootc-bot bot commented Sep 8, 2025

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@bootc-bot bootc-bot bot force-pushed the bootc-renovate/all branch from 06ed494 to 1dfe0b7 Compare September 8, 2025 12:16
@bootc-bot bootc-bot bot changed the title Update actions/checkout action to v5 Update all dependencies Sep 8, 2025
@bootc-bot
Copy link
Contributor Author

bootc-bot bot commented Sep 8, 2025

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 14 additional dependencies were updated
  • The go directive was updated for compatibility reasons

Details:

Package Change
go 1.22.6 -> 1.24.0
golang.org/x/crypto v0.28.0 -> v0.41.0
github.com/Microsoft/go-winio v0.6.1 -> v0.6.2
github.com/fsnotify/fsnotify v1.7.0 -> v1.8.0
github.com/go-logr/logr v1.4.1 -> v1.4.3
github.com/google/go-cmp v0.6.0 -> v0.7.0
github.com/google/pprof v0.0.0-20230323073829-e72429f035bd -> v0.0.0-20250403155104-27863c87afa6
github.com/spf13/pflag v1.0.5 -> v1.0.9
golang.org/x/mod v0.17.0 -> v0.27.0
golang.org/x/net v0.30.0 -> v0.43.0
golang.org/x/sync v0.8.0 -> v0.16.0
golang.org/x/text v0.19.0 -> v0.28.0
golang.org/x/time v0.3.0 -> v0.5.0
golang.org/x/tools v0.21.1-0.20240508182429-e35e4ccd0d2d -> v0.36.0
google.golang.org/protobuf v1.35.1 -> v1.36.7

@bootc-bot bootc-bot bot force-pushed the bootc-renovate/all branch from 1dfe0b7 to 3179935 Compare September 9, 2025 13:19
@bootc-bot bootc-bot bot force-pushed the bootc-renovate/all branch from 3179935 to 282bf6f Compare September 24, 2025 16:12
@bootc-bot bootc-bot bot force-pushed the bootc-renovate/all branch 4 times, most recently from 47db32d to 2ab0deb Compare October 8, 2025 16:12
@bootc-bot bootc-bot bot force-pushed the bootc-renovate/all branch 2 times, most recently from 928437b to af92060 Compare October 13, 2025 22:10
@bootc-bot bootc-bot bot force-pushed the bootc-renovate/all branch 3 times, most recently from acc30b4 to 125aae8 Compare October 27, 2025 20:10
@bootc-bot bootc-bot bot force-pushed the bootc-renovate/all branch 3 times, most recently from b894e83 to 960c46f Compare November 11, 2025 17:11
@bootc-bot bootc-bot bot force-pushed the bootc-renovate/all branch 6 times, most recently from e503fa5 to f3695e5 Compare December 8, 2025 16:13
@bootc-bot bootc-bot bot force-pushed the bootc-renovate/all branch from f3695e5 to f5c9700 Compare December 8, 2025 18:16
@bootc-bot
Copy link
Contributor Author

bootc-bot bot commented Dec 18, 2025 •
edited
Loading

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 14 additional dependencies were updated
  • The go directive was updated for compatibility reasons

Details:

Package Change
go 1.22.6 -> 1.24.0
golang.org/x/crypto v0.28.0 -> v0.47.0
github.com/Microsoft/go-winio v0.6.1 -> v0.6.2
github.com/fsnotify/fsnotify v1.7.0 -> v1.8.0
github.com/go-logr/logr v1.4.1 -> v1.4.3
github.com/google/go-cmp v0.6.0 -> v0.7.0
github.com/google/pprof v0.0.0-20230323073829-e72429f035bd -> v0.0.0-20260115054156-294ebfa9ad83
github.com/spf13/pflag v1.0.5 -> v1.0.9
golang.org/x/mod v0.17.0 -> v0.32.0
golang.org/x/net v0.30.0 -> v0.49.0
golang.org/x/sync v0.8.0 -> v0.19.0
golang.org/x/text v0.19.0 -> v0.33.0
golang.org/x/time v0.3.0 -> v0.5.0
golang.org/x/tools v0.21.1-0.20240508182429-e35e4ccd0d2d -> v0.41.0
google.golang.org/protobuf v1.35.1 -> v1.36.7

@bootc-bot bootc-bot bot force-pushed the bootc-renovate/all branch 4 times, most recently from decd882 to 80c5d60 Compare January 12, 2026 23:11
@bootc-bot bootc-bot bot force-pushed the bootc-renovate/all branch 2 times, most recently from 61d5e77 to 3a35958 Compare January 15, 2026 19:16
@bootc-bot bootc-bot bot force-pushed the bootc-renovate/all branch from 3a35958 to d138d10 Compare January 22, 2026 14:23
@bootc-bot bootc-bot bot force-pushed the bootc-renovate/all branch 3 times, most recently from a79ceb5 to 65d382a Compare February 6, 2026 12:22
@bootc-bot
Update all dependencies
2d2b4ba 
Signed-off-by: bootc-bot[bot] <225049296+bootc-bot[bot]@users.noreply.github.com>
@bootc-bot bootc-bot bot force-pushed the bootc-renovate/all branch from 65d382a to 2d2b4ba Compare February 8, 2026 17:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants