[18-stable] Update module github.com/onsi/gomega to v1.44.0 (18-stable) - #530
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: Central YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
|
Hi @ospk8s-renovate[bot]. Thanks for your PR. I'm waiting for a openstack-k8s-operators member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
68e60de to
7914187
Compare
|
/ok-to-test |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kstrenkova, ospk8s-renovate[bot] The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This PR contains the following updates:
v1.43.1→v1.44.0Release Notes
onsi/gomega (github.com/onsi/gomega)
v1.44.0Compare Source
Fixes
BeNumericallycompares signed and unsigned integers by value:-1no longer equalsuint64(math.MaxUint64)anduint(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]HaveKeyWithValuesucceeds if any key accepted by the key matcher has a matching value, rather than depending on map iteration order (#929) [ffc577a]HaveKeyandHaveKeyWithValuetreat key and value matcher errors likeContainElementdoes: a match wins, and an error is only reported when nothing matches (#926) [dc91598]MatchJSONno longer treats numbers too large for a float64 as equal to one another (#930) [9d619a5]MatchJSONcompares 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]HaveExactElementsreports missing or extra elements that start at index 0, and reports the first extra element's index rather than the last (#934) [af1b777]MatchYAMLcompares every document in a multi-document stream rather than only the first; empty documents (e.g. a leading or trailing---) are ignored (#933) [2773796]MatchXMLignores 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]Configuration
📅 Schedule: (in timezone America/New_York)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate CLI.