dependabot[bot] opened a new pull request, #6853:
URL: https://github.com/apache/camel-k/pull/6853

   Bumps [github.com/onsi/gomega](https://github.com/onsi/gomega) from 1.43.1 
to 1.44.0.
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/onsi/gomega/releases";>github.com/onsi/gomega's 
releases</a>.</em></p>
   <blockquote>
   <h2>v1.44.0</h2>
   <h3>Fixes</h3>
   <ul>
   <li><code>BeNumerically</code> compares signed and unsigned integers by 
value: <code>-1</code> no longer equals <code>uint64(math.MaxUint64)</code> and 
<code>uint(5)</code> is now greater than <code>-3</code> (<a 
href="https://redirect.github.com/onsi/gomega/issues/925";>#925</a>) 
[26e3c6b]</li>
   <li><code>BeNumerically(&quot;~&quot;)</code> no longer overflows when 
computing the distance between extreme integers (<a 
href="https://redirect.github.com/onsi/gomega/issues/928";>#928</a>) 
[1955764]</li>
   <li><code>BeNumerically(&quot;==&quot;, x, threshold)</code> now honors the 
threshold for floats, as it already did for integers (<a 
href="https://redirect.github.com/onsi/gomega/issues/927";>#927</a>) 
[10e2aca]</li>
   <li><code>HaveKeyWithValue</code> succeeds if any key accepted by the key 
matcher has a matching value, rather than depending on map iteration order (<a 
href="https://redirect.github.com/onsi/gomega/issues/929";>#929</a>) 
[ffc577a]</li>
   <li><code>HaveKey</code> and <code>HaveKeyWithValue</code> treat key and 
value matcher errors like <code>ContainElement</code> does: a match wins, and 
an error is only reported when nothing matches (<a 
href="https://redirect.github.com/onsi/gomega/issues/926";>#926</a>) 
[dc91598]</li>
   <li><code>MatchJSON</code> no longer treats numbers too large for a float64 
as equal to one another (<a 
href="https://redirect.github.com/onsi/gomega/issues/930";>#930</a>) 
[9d619a5]</li>
   <li><code>MatchJSON</code> compares integers beyond ±2^53 exactly, so 
neighboring large integers (e.g. IDs) no longer match; all other numbers are 
still compared as float64s (<a 
href="https://redirect.github.com/onsi/gomega/issues/931";>#931</a>) [8ef1aa7, 
630fe12]</li>
   <li><code>HaveExactElements</code> reports missing or extra elements that 
start at index 0, and reports the first extra element's index rather than the 
last (<a href="https://redirect.github.com/onsi/gomega/issues/934";>#934</a>) 
[af1b777]</li>
   <li><code>MatchYAML</code> compares every document in a multi-document 
stream rather than only the first; empty documents (e.g. a leading or trailing 
<code>---</code>) are ignored (<a 
href="https://redirect.github.com/onsi/gomega/issues/933";>#933</a>) 
[2773796]</li>
   <li><code>MatchXML</code> 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 (<a 
href="https://redirect.github.com/onsi/gomega/issues/932";>#932</a>) [c0dbd89, 
2565350]</li>
   </ul>
   </blockquote>
   </details>
   <details>
   <summary>Changelog</summary>
   <p><em>Sourced from <a 
href="https://github.com/onsi/gomega/blob/master/CHANGELOG.md";>github.com/onsi/gomega's
 changelog</a>.</em></p>
   <blockquote>
   <h2>1.44.0</h2>
   <h3>Fixes</h3>
   <ul>
   <li><code>BeNumerically</code> compares signed and unsigned integers by 
value: <code>-1</code> no longer equals <code>uint64(math.MaxUint64)</code> and 
<code>uint(5)</code> is now greater than <code>-3</code> (<a 
href="https://redirect.github.com/onsi/gomega/issues/925";>#925</a>) 
[26e3c6b]</li>
   <li><code>BeNumerically(&quot;~&quot;)</code> no longer overflows when 
computing the distance between extreme integers (<a 
href="https://redirect.github.com/onsi/gomega/issues/928";>#928</a>) 
[1955764]</li>
   <li><code>BeNumerically(&quot;==&quot;, x, threshold)</code> now honors the 
threshold for floats, as it already did for integers (<a 
href="https://redirect.github.com/onsi/gomega/issues/927";>#927</a>) 
[10e2aca]</li>
   <li><code>HaveKeyWithValue</code> succeeds if any key accepted by the key 
matcher has a matching value, rather than depending on map iteration order (<a 
href="https://redirect.github.com/onsi/gomega/issues/929";>#929</a>) 
[ffc577a]</li>
   <li><code>HaveKey</code> and <code>HaveKeyWithValue</code> treat key and 
value matcher errors like <code>ContainElement</code> does: a match wins, and 
an error is only reported when nothing matches (<a 
href="https://redirect.github.com/onsi/gomega/issues/926";>#926</a>) 
[dc91598]</li>
   <li><code>MatchJSON</code> no longer treats numbers too large for a float64 
as equal to one another (<a 
href="https://redirect.github.com/onsi/gomega/issues/930";>#930</a>) 
[9d619a5]</li>
   <li><code>MatchJSON</code> compares integers beyond ±2^53 exactly, so 
neighboring large integers (e.g. IDs) no longer match; all other numbers are 
still compared as float64s (<a 
href="https://redirect.github.com/onsi/gomega/issues/931";>#931</a>) [8ef1aa7, 
630fe12]</li>
   <li><code>HaveExactElements</code> reports missing or extra elements that 
start at index 0, and reports the first extra element's index rather than the 
last (<a href="https://redirect.github.com/onsi/gomega/issues/934";>#934</a>) 
[af1b777]</li>
   <li><code>MatchYAML</code> compares every document in a multi-document 
stream rather than only the first; empty documents (e.g. a leading or trailing 
<code>---</code>) are ignored (<a 
href="https://redirect.github.com/onsi/gomega/issues/933";>#933</a>) 
[2773796]</li>
   <li><code>MatchXML</code> 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 (<a 
href="https://redirect.github.com/onsi/gomega/issues/932";>#932</a>) [c0dbd89, 
2565350]</li>
   </ul>
   </blockquote>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/onsi/gomega/commit/c933817422c6e533357f6e1171585e7a07d5aeba";><code>c933817</code></a>
 v1.44.0</li>
   <li><a 
href="https://github.com/onsi/gomega/commit/37fa9004bf0672d6f87a38c0af24625a93de9cf8";><code>37fa900</code></a>
 v1.44.0 (full)</li>
   <li><a 
href="https://github.com/onsi/gomega/commit/509f2b09e0700917a1ce424c3fbd12af7cdf678e";><code>509f2b0</code></a>
 changelog: entries for #925-<a 
href="https://redirect.github.com/onsi/gomega/issues/934";>#934</a></li>
   <li><a 
href="https://github.com/onsi/gomega/commit/25653503b45d4602ed68b5ee930294c5433532a2";><code>2565350</code></a>
 fix: MatchXML compares namespace declarations by URI, ignoring the prefix</li>
   <li><a 
href="https://github.com/onsi/gomega/commit/630fe124b28d1560f6490b1b6c53393efe1f8158";><code>630fe12</code></a>
 fix: MatchJSON only compares integers beyond 2^53 exactly</li>
   <li><a 
href="https://github.com/onsi/gomega/commit/c0dbd89c8ed6325e67a7cc7e6ab194fbfb66e607";><code>c0dbd89</code></a>
 fix: MatchXML ignores namespace prefixes and declarations</li>
   <li><a 
href="https://github.com/onsi/gomega/commit/2773796edf3abe3683e12613a134fbb0f6663f57";><code>2773796</code></a>
 fix: MatchYAML compares every document in a multi-document stream</li>
   <li><a 
href="https://github.com/onsi/gomega/commit/af1b777bb1add8e0ff3e8d9b3aa1613642e65855";><code>af1b777</code></a>
 fix: HaveExactElements reports missing/extra elements starting at index 0</li>
   <li><a 
href="https://github.com/onsi/gomega/commit/8ef1aa725e129bca37281826caf3297c2db632cd";><code>8ef1aa7</code></a>
 fix: MatchJSON compares numbers exactly</li>
   <li><a 
href="https://github.com/onsi/gomega/commit/9d619a507a5f2af5a61c7ad087dff7133b39a402";><code>9d619a5</code></a>
 fix: MatchJSON reports numbers that do not fit in a float64</li>
   <li>Additional commits viewable in <a 
href="https://github.com/onsi/gomega/compare/v1.43.1...v1.44.0";>compare 
view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=github.com/onsi/gomega&package-manager=go_modules&previous-version=1.43.1&new-version=1.44.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   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-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   <details>
   <summary>Dependabot commands and options</summary>
   <br />
   
   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 this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this minor version` will close this PR and stop 
Dependabot creating any more for this minor version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this dependency` will close this PR and stop 
Dependabot creating any more for this dependency (unless you reopen the PR or 
upgrade to it yourself)
   
   
   </details>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to