Update all dependencies #119
Open
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:
v0.4.0
->v0.5.3
v0.7.3
->v0.8.7
v0.5.0
->v0.6.0
v0.8.1
->v0.12.1
v2.17.1
->v2.25.3
v1.32.0
->v1.38.2
v1.8.0
->v1.10.1
v0.26.0
->v0.36.0
v0.25.0
->v0.35.0
v1.10002.0
->v1.11006.0
Release Notes
adrg/xdg (github.com/adrg/xdg)
v0.5.3
Compare Source
Changelog
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
v0.5.2
Compare Source
Changelog
Updated logic of
xdg.RuntimeFile
: due to the special nature of theruntime 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'stemporary 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:
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
XDG_BIN_HOME
base directory.See XDG base directories README section for more details.
macOS
.~/.config
at the end of the list of default locations forXDG_CONFIG_DIRS
.~/.local/share
at the end of the list of default locations forXDG_DATA_DIRS
.Windows
:%ProgramFiles%
%ProgramFiles%\Common Files
%LOCALAPPDATA%\Programs
%LOCALAPPDATA%\Programs\Common
Internal
golang.org/x/sys
dependency to the latest version.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.
golang.org/x/sys
dependency to the latest version.Internal
pathutil
package.userdirs
package:xdg.UserDirectories
touserdirs.Directories
.user-dirs.dirs
config file.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 acapture.pcap
file ingvproxy
’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
PortsForwarder.Expose()
proxy check by @cpick in #441Dependencies 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
replace inet.af/tcpproxy => github.com/inetaf/tcpproxy
by @AkihiroSuda in #409pull/395
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
2862066
by @cfergeau in #386Dependency 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.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
Full Changelog: gofrs/flock@v0.11.0...v0.12.0
v0.11.0
Compare Source
What's Changed
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.25.3
Compare Source
2.25.3
Fixes
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
10866d3
]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 andbody
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
andDeferCleanup
,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 callruntime.LockOSThread()
in theAroundNode
to ensure that the node runs on a single thread).Since
AroundNode
allows you to modify the context you can also useAroundNode
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 likeBeforeEach
andDeferCleanup
.AroundNode
can also be applied toRunSpecs
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")
andginkgo --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
3f5d379
]. fixes #1582Maintenance
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
2b9c428
]Fixes
1f59d07
]Maintenance
2d134d5
]v2.23.3
Compare Source
2.23.3
Fixes
-
as a standalone argument [cfcc1a5
]feaf292
]88e2282
]v2.23.2
Compare Source
2.23.2
🎉🎉🎉
At long last, some long-standing performance gaps between
ginkgo
andgo 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 ofgo test -c
is slower thango test
's compilation step becausego test
strips out debug symbols (ldflags=-w
) whereasgo test -c
does not.Ginkgo now passes the appropriate
ldflags
togo 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 whenginkgo 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:
a0e52ff
]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 thetesting.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 aDeferCleanup()
. This has subtle behavior differences from the golang implementation but should make sense in a Ginkgo... um... context.Features
37a511b
]Fixes
7556a86
]4df06c6
]Maintenance
cbcf39a
]9b261ff
]00f19c8
]e98a4df
]60cc4e2
]fea6f2d
]31d7813
]fc3bbd6
]aee0d56
]809a710
]v2.22.2
Compare Source
What's Changed
Full Changelog: onsi/ginkgo@v2.22.1...v2.22.2
v2.22.1
Compare Source
2.22.1
Fixes
Fix CSV encoding
aab3da6
]c09df39
]96a80fc
]43dad69
]Maintenance
c88c634
]4df44bf
]v2.22.0
Compare Source
2.22.0
Features
0fcaa08
]This allows serial tests to be filtered using the
label-filter
Maintenance
Various doc fixes
v2.21.0
Compare Source
2.21.0
Features
a69eb39
]bcab9c8
]Fixes
e548367
]SpecsThatWillBeRun
withSpecsThatWillRun
[
c2c4d3c
]Maintenance
7e65a00
]v2.20.2
Compare Source
2.20.2
Require Go 1.22+
Maintenance
a671816
]v2.20.1
Compare Source
2.20.1
Fixes
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.
This PR has been generated by Renovate Bot.