[dependabot]

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

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

Release notes

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

v2.34.0

Features

• DeferOnFailure registers a callback that runs only when a spec fails - as soon as the failing node returns and before any teardown (JustAfterEach, AfterEach, AfterAll, DeferCleanup) - so it can capture the state teardown is about to destroy. It takes exactly what DeferCleanup takes and shares its scoping: called in BeforeEach/JustBeforeEach/It it covers the spec, in BeforeAll the ordered container, and in BeforeSuite the whole suite. It is also available on GinkgoT(); note that this adds a method to FullGinkgoTInterface, so hand-written implementations of that interface need to add it. See https://onsi.github.io/ginkgo/#capturing-failure-state-deferonfailure

Fixes

• Progress reporters (AttachProgressReporter) are no longer called while Ginkgo holds an internal lock, so a reporter that calls CurrentSpecReport() or AddReportEntry() no longer stalls for 5 seconds and has its output dropped.
• --sleep-on-failure now runs after any DeferOnFailure callbacks, also pauses when a spec times out, and no longer pauses if the suite has already been interrupted.

v2.33.1

Fixes

• Add several missing fields to spec report JSON output.

Changelog

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

2.34.0

Features

• DeferOnFailure registers a callback that runs only when a spec fails - as soon as the failing node returns and before any teardown (JustAfterEach, AfterEach, AfterAll, DeferCleanup) - so it can capture the state teardown is about to destroy. It takes exactly what DeferCleanup takes and shares its scoping: called in BeforeEach/JustBeforeEach/It it covers the spec, in BeforeAll the ordered container, and in BeforeSuite the whole suite. It is also available on GinkgoT(); note that this adds a method to FullGinkgoTInterface, so hand-written implementations of that interface need to add it. See https://onsi.github.io/ginkgo/#capturing-failure-state-deferonfailure

Fixes

• Progress reporters (AttachProgressReporter) are no longer called while Ginkgo holds an internal lock, so a reporter that calls CurrentSpecReport() or AddReportEntry() no longer stalls for 5 seconds and has its output dropped.
• --sleep-on-failure now runs after any DeferOnFailure callbacks, also pauses when a spec times out, and no longer pauses if the suite has already been interrupted.

2.33.1

Fixes

• Add several missing fields to spec report JSON output.

Commits

• 7035669 v2.34.0
• 6698926 docs: DeferOnFailure notes for library authors and pause-style callbacks
• b66a63f Add parallel and JSON integration coverage for DeferOnFailure
• 07edd04 Precompile the fixtures in the multi-suite timeout integration test
• db1c4c8 Add DeferOnFailure
• fba28c7 Query progress reporters without holding selectiveLock
• 7ff96d7 v2.33.1
• 699632a Precompile the fixture in the suite-timeout integration test (#1689)
• 9e02cad ci: default the release bump so a mobile dispatch can't send it empty (#1688)
• ef6a46c Update CHANGELOG.md
• Additional commits viewable in compare view

Updates github.com/onsi/gomega from 1.43.1 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]

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]

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

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: d5cd54a2-8127-4cd3-af59-4db244abcd55

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn