Skip to content

Update all dependencies #119

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update all dependencies #119

wants to merge 1 commit into from

Conversation

@bootc-bot
Copy link
Contributor

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

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.7 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.27.1 age confidence
github.com/onsi/gomega v1.32.0 -> v1.38.2 age confidence
github.com/spf13/cobra v1.8.0 -> v1.10.1 age confidence
golang.org/x/sys v0.26.0 -> v0.37.0 age confidence
golang.org/x/term v0.25.0 -> v0.36.0 age confidence
libvirt.org/go/libvirt v1.10002.0 -> v1.11006.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.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.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

Compare Source

2.25.0

AroundNode

This release introduces a new decorator to support more complex spec setup usecases.

AroundNode registers a function that runs before each individual node. This is considered a more advanced decorator.

Please read the docs for more information and some examples.

Allowed signatures:

  • AroundNode(func()) - func will be called before the node is run.
  • AroundNode(func(ctx context.Context) context.Context) - func can wrap the passed in context and return a new one which will be passed on to the node.
  • AroundNode(func(ctx context.Context, body func(ctx context.Context))) - ctx is the context for the node and body is a function that must be called to run the node. This gives you complete control over what runs before and after the node.

Multiple AroundNode decorators can be applied to a single node and they will run in the order they are applied.

Unlike setup nodes like BeforeEach and DeferCleanup, AroundNode is guaranteed to run in the same goroutine as the decorated node. This is necessary when working with lower-level libraries that must run on a single thread (you can call runtime.LockOSThread() in the AroundNode to ensure that the node runs on a single thread).

Since AroundNode allows you to modify the context you can also use AroundNode to implement shared setup that attaches values to the context.

If applied to a container, AroundNode will run before every node in the container. Including setup nodes like BeforeEach and DeferCleanup.

AroundNode can also be applied to RunSpecs to run before every node in the suite. This opens up new mechanisms for instrumenting individual nodes across an entire suite.

v2.24.0

Compare Source

2.24.0

Features

Specs can now be decorated with (e.g.) SemVerConstraint("2.1.0") and ginkgo --sem-ver-filter="2.1.1" will only run constrained specs that match the requested version. Learn more in the docs here! Thanks to @​Icarus9913 for the PR.

Fixes
Maintenance

Numerous dependency bumps and documentation fixes

v2.23.4

Compare Source

2.23.4

Prior to this release Ginkgo would compute the incorrect number of available CPUs when running with -p in a linux container. Thanks to @​emirot for the fix!

Features
  • Add automaxprocs for using CPUQuota [2b9c428]
Fixes
  • clarify gotchas about -vet flag [1f59d07]
Maintenance

v2.23.3

Compare Source

2.23.3

Fixes
  • allow - as a standalone argument [cfcc1a5]
  • Bug Fix: Add GinkoTBWrapper.Chdir() and GinkoTBWrapper.Context() [feaf292]
  • ignore exit code for symbol test on linux [88e2282]

v2.23.2

Compare Source

2.23.2

🎉🎉🎉

At long last, some long-standing performance gaps between ginkgo and go test have been resolved!

Ginkgo operates by running go test -c to generate test binaries, and then running those binaries. It turns out that the compilation step of go test -c is slower than go test's compilation step because go test strips out debug symbols (ldflags=-w) whereas go test -c does not.

Ginkgo now passes the appropriate ldflags to go test -c when running specs to strip out symbols. This is only done when it is safe to do so and symbols are preferred when profiling is enabled and when ginkgo build is called explicitly.

This, coupled, with the instructions for disabling XProtect on MacOS yields a much better performance experience with Ginkgo.

v2.23.1

Compare Source

2.23.1

🚨 For users on MacOS 🚨

A long-standing Ginkgo performance issue on MacOS seems to be due to mac's antimalware XProtect. You can follow the instructions here to disable it in your terminal. Doing so sped up Ginkgo's own test suite from 1m8s to 47s.

Fixes

Ginkgo's CLI is now a bit clearer if you pass flags in incorrectly:

  • make it clearer that you need to pass a filename to the various profile flags, not an absolute directory [a0e52ff]
  • emit an error and exit if the ginkgo invocation includes flags after positional arguments [b799d8d]

This might cause existing CI builds to fail. If so then it's likely that your CI build was misconfigured and should be corrected. Open an issue if you need help.

v2.23.0

Compare Source

2.23.0

Ginkgo 2.23.0 adds a handful of methods to GinkgoT() to make it compatible with the testing.TB interface in Go 1.24. GinkgoT().Context(), in particular, is a useful shorthand for generating a new context that will clean itself up in a DeferCleanup(). This has subtle behavior differences from the golang implementation but should make sense in a Ginkgo... um... context.

Features
  • bump to go 1.24.0 - support new testing.TB methods and add a test to cover testing.TB regressions [37a511b]
Fixes
  • fix edge case where build -o is pointing at an explicit file, not a directory [7556a86]
  • Fix binary paths when precompiling multiple suites. [4df06c6]
Maintenance

v2.22.2

Compare Source

What's Changed

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 from af92060 to a892ecc Compare October 22, 2025 16:12
@bootc-bot
Update all dependencies
acc30b4 
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 a892ecc to acc30b4 Compare October 24, 2025 18:13
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