chore(deps): bump the minor-patch-updates group across 1 directory with 3 updates

[dependabot]

Bumps the minor-patch-updates group with 3 updates in the / directory: github.com/knadh/koanf/v2, github.com/onsi/ginkgo/v2 and github.com/onsi/gomega.

Updates github.com/knadh/koanf/v2 from 2.3.6 to 2.3.7

Release notes

Sourced from github.com/knadh/koanf/v2's releases.

v2.3.7

What's Changed

• fix: panic from Vault Provider when Transport is not supplied by @​riflowth in knadh/koanf#439
• Preserve empty slice entries in StringsMap by @​jakezwang in knadh/koanf#449
• Bump google.golang.org/grpc from 1.82.1 to 1.83.1 in /examples by @​dependabot[bot] in knadh/koanf#446
• Fix Slices silently dropping a natively-typed []map[string]any by @​Osamaali313 in knadh/koanf#448
• Accept natively-typed slices and maps in the typed getters by @​yu2971512385-ui in knadh/koanf#450

New Contributors

• @​riflowth made their first contribution in knadh/koanf#439
• @​jakezwang made their first contribution in knadh/koanf#449
• @​Osamaali313 made their first contribution in knadh/koanf#448
• @​yu2971512385-ui made their first contribution in knadh/koanf#450

Full Changelog: knadh/koanf@v2.3.6...v2.3.7

Commits

• f3b40fa Fix typed map getter funcs returning empty results (#450)
• c69572c Fix Slices silently dropping a natively-typed []map[string]any (#448)
• 83a6751 Bump google.golang.org/grpc from 1.82.1 to 1.83.1 in /examples (#446)
• c316bd1 Fix empty slices resulting in removed keys in StringsMap() (#449)
• 6ad56fe Fix key collission on 'Unflatten' by making insertions deterministic. Closes ...
• eb15bf7 fix: panic when Config.Transport is not supplied (#439)
• defde9b Fix azurevault throwing 403 incorrectly fetching disabled keys. Closes #436.
• fb45026 Skip env entries without '=' in env provider avoid panicking.
• See full diff in compare view

Updates github.com/onsi/ginkgo/v2 from 2.32.1 to 2.33.0

Release notes

Sourced from github.com/onsi/ginkgo/v2's releases.

v2.33.0

Features

• The JUnit reporter now records each spec's ReportEntrys as <properties> on its <testcase> element, with the entry's name and its JSON-encoded value. Thanks @​pohly! [23db51a]

Maintenance

• Releases are now cut by a GitHub Actions workflow (Actions -> Release -> Run workflow) rather than by hand, with changelog entries collected under ## Unreleased as the work happens. See RELEASING.md. [8616ecb]

v2.32.2

2.32.2

Fixes

• fix bug where ginkgo -race -p was taking extra long to exit [c6792b0]

Changelog

Sourced from github.com/onsi/ginkgo/v2's changelog.

2.33.0

Features

• The JUnit reporter now records each spec's ReportEntrys as <properties> on its <testcase> element, with the entry's name and its JSON-encoded value. Thanks @​pohly! [23db51a]

Maintenance

• Releases are now cut by a GitHub Actions workflow (Actions -> Release -> Run workflow) rather than by hand, with changelog entries collected under ## Unreleased as the work happens. See RELEASING.md. [8616ecb]

2.32.2

Fixes

• fix bug where ginkgo -race -p was taking extra long to exit [c6792b0]

Commits

• 9f94149 v2.33.0
• db78e1b changelog: entries for the JUnit ReportEntry support and the release flow
• 8616ecb ci: release from a single workflow_dispatch button
• d8d9cdd README: add a sponsor badge
• ac70da6 README: dark-mode logo and a docs badge
• 23db51a junit: support ReportEntry
• b9e3bdd v2.32.2
• c6792b0 fix bug where ginkgo -race -p was taking extra long to exit
• See full diff in compare view

Updates github.com/onsi/gomega from 1.43.0 to 1.44.0

Release notes

Sourced from github.com/onsi/gomega's releases.

v1.44.0

Fixes

• BeNumerically compares signed and unsigned integers by value: -1 no longer equals uint64(math.MaxUint64) and uint(5) is now greater than -3 (#925) [26e3c6b]
• BeNumerically("~") no longer overflows when computing the distance between extreme integers (#928) [1955764]
• BeNumerically("==", x, threshold) now honors the threshold for floats, as it already did for integers (#927) [10e2aca]
• HaveKeyWithValue succeeds if any key accepted by the key matcher has a matching value, rather than depending on map iteration order (#929) [ffc577a]
• HaveKey and HaveKeyWithValue treat key and value matcher errors like ContainElement does: a match wins, and an error is only reported when nothing matches (#926) [dc91598]
• MatchJSON no longer treats numbers too large for a float64 as equal to one another (#930) [9d619a5]
• MatchJSON compares integers beyond ±2^53 exactly, so neighboring large integers (e.g. IDs) no longer match; all other numbers are still compared as float64s (#931) [8ef1aa7, 630fe12]
• HaveExactElements reports missing or extra elements that start at index 0, and reports the first extra element's index rather than the last (#934) [af1b777]
• MatchYAML compares every document in a multi-document stream rather than only the first; empty documents (e.g. a leading or trailing ---) are ignored (#933) [2773796]
• MatchXML ignores namespace prefixes: elements and attributes are compared by namespace URI, and the URIs declared on each element must match whatever prefix they are bound to (#932) [c0dbd89, 2565350]

v1.43.1

Maintenance

• Update go.yaml.in/yaml/v3 to v3.0.5 [d547015]
• Releases are now cut by a GitHub Actions workflow (Actions -> Release -> Run workflow) rather than by hand, with changelog entries collected under ## Unreleased as the work happens. Releases still ship the stripped-down tree on master-lite - tests removed and Ginkgo dropped from go.mod - and the workflow now builds it and checks it on every push. See RELEASING.md. [e9dc84d]

Changelog

Sourced from github.com/onsi/gomega's changelog.

1.44.0

Fixes

• BeNumerically compares signed and unsigned integers by value: -1 no longer equals uint64(math.MaxUint64) and uint(5) is now greater than -3 (#925) [26e3c6b]
• BeNumerically("~") no longer overflows when computing the distance between extreme integers (#928) [1955764]
• BeNumerically("==", x, threshold) now honors the threshold for floats, as it already did for integers (#927) [10e2aca]
• HaveKeyWithValue succeeds if any key accepted by the key matcher has a matching value, rather than depending on map iteration order (#929) [ffc577a]
• HaveKey and HaveKeyWithValue treat key and value matcher errors like ContainElement does: a match wins, and an error is only reported when nothing matches (#926) [dc91598]
• MatchJSON no longer treats numbers too large for a float64 as equal to one another (#930) [9d619a5]
• MatchJSON compares integers beyond ±2^53 exactly, so neighboring large integers (e.g. IDs) no longer match; all other numbers are still compared as float64s (#931) [8ef1aa7, 630fe12]
• HaveExactElements reports missing or extra elements that start at index 0, and reports the first extra element's index rather than the last (#934) [af1b777]
• MatchYAML compares every document in a multi-document stream rather than only the first; empty documents (e.g. a leading or trailing ---) are ignored (#933) [2773796]
• MatchXML ignores namespace prefixes: elements and attributes are compared by namespace URI, and the URIs declared on each element must match whatever prefix they are bound to (#932) [c0dbd89, 2565350]

1.43.1

Maintenance

• Update go.yaml.in/yaml/v3 to v3.0.5 [d547015]
• Releases are now cut by a GitHub Actions workflow (Actions -> Release -> Run workflow) rather than by hand, with changelog entries collected under ## Unreleased as the work happens. Releases still ship the stripped-down tree on master-lite - tests removed and Ginkgo dropped from go.mod - and the workflow now builds it and checks it on every push. See RELEASING.md. [e9dc84d]

Commits

• c933817 v1.44.0
• 37fa900 v1.44.0 (full)
• 509f2b0 changelog: entries for #925-#934
• 2565350 fix: MatchXML compares namespace declarations by URI, ignoring the prefix
• 630fe12 fix: MatchJSON only compares integers beyond 2^53 exactly
• c0dbd89 fix: MatchXML ignores namespace prefixes and declarations
• 2773796 fix: MatchYAML compares every document in a multi-document stream
• af1b777 fix: HaveExactElements reports missing/extra elements starting at index 0
• 8ef1aa7 fix: MatchJSON compares numbers exactly
• 9d619a5 fix: MatchJSON reports numbers that do not fit in a float64
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions