dependabot[bot] opened a new pull request, #6592: URL: https://github.com/apache/camel-k/pull/6592
Bumps [github.com/onsi/gomega](https://github.com/onsi/gomega) from 1.39.1 to 1.40.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.40.0</h2> <h2>1.40.0</h2> <p>We're adopting a new release strategy to minimize dependency bloat in projects that consume Gomega. It is a limitation of the go mod toolchain that <em>test</em> subdependencies of your project's direct dependencies get pulled in as <em>indirect</em> dependencies. In the case of Gomega, this ends up pulling in all of Ginkgo into your <code>go.mod</code> even if you are only using Gomega (Gomega uses Ginkgo for its own tests).</p> <p>Going forward, releases will strip out all tests, tidy up the <code>go.mod</code> and then push this stripped down version to a new <code>master-lite</code> branch. These stripped-down versions will receive the <code>vx.y.z</code> git tag and will be picked up by the go toolchain.</p> <p>Please open an issue if this new release process causes unexpected changes for your projects.</p> </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.40.0</h2> <p>We're adopting a new release strategy to minimize dependency bloat in projects that consume Gomega. It is a limitation of the go mod toolchain that <em>test</em> subdependencies of your project's direct dependencies get pulled in as <em>indirect</em> dependencies. In the case of Gomega, this ends up pulling in all of Ginkgo into your <code>go.mod</code> even if you are only using Gomega (Gomega uses Ginkgo for its own tests).</p> <p>Going forward, releases will strip out all tests, tidy up the <code>go.mod</code> and then push this stripped down version to a new <code>master-lite</code> branch. These stripped-down versions will receive the <code>vx.y.z</code> git tag and will be picked up by the go toolchain.</p> <p>Please open an issue if this new release process causes unexpected changes for your projects.</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/onsi/gomega/commit/87ee9d3caabba627e5951958be800828b85f0370";><code>87ee9d3</code></a> v1.40.0</li> <li><a href="https://github.com/onsi/gomega/commit/ea660274df4319411eea463c942d1d3a56e6c2e6";><code>ea66027</code></a> v1.40.0 (full)</li> <li><a href="https://github.com/onsi/gomega/commit/e3fd789576a5f5b9a35847683804349bb4bbc761";><code>e3fd789</code></a> update docs to reflect new versioning strategy</li> <li><a href="https://github.com/onsi/gomega/commit/7d4ee309b2c28ab1854424f70c99a173650ab2f6";><code>7d4ee30</code></a> first push to master-lite</li> <li><a href="https://github.com/onsi/gomega/commit/e4a82d1a2de91721bb249fe9532c4d9211920363";><code>e4a82d1</code></a> Bump github/codeql-action from 3 to 4 (<a href="https://redirect.github.com/onsi/gomega/issues/875";>#875</a>)</li> <li><a href="https://github.com/onsi/gomega/commit/af627234340a2e1d40074d6e6860a1b41dc03204";><code>af62723</code></a> Bump rexml from 3.4.0 to 3.4.2 in /docs (<a href="https://redirect.github.com/onsi/gomega/issues/870";>#870</a>)</li> <li><a href="https://github.com/onsi/gomega/commit/e1642211b3906ab5456d9d3ed7cfd9edd11f2d63";><code>e164221</code></a> Bump github.com/onsi/ginkgo/v2 from 2.28.0 to 2.28.1 (<a href="https://redirect.github.com/onsi/gomega/issues/895";>#895</a>)</li> <li><a href="https://github.com/onsi/gomega/commit/334a282f9d59760a3e737e5b61400a3162997803";><code>334a282</code></a> Bump faraday from 2.12.2 to 2.14.1 in /docs (<a href="https://redirect.github.com/onsi/gomega/issues/896";>#896</a>)</li> <li>See full diff in <a href="https://github.com/onsi/gomega/compare/v1.39.1...v1.40.0";>compare view</a></li> </ul> </details> <br /> [](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]
