dependabot[bot] opened a new pull request, #6720: URL: https://github.com/apache/camel-k/pull/6720
Bumps [sigs.k8s.io/gateway-api](https://github.com/kubernetes-sigs/gateway-api) from 1.6.0 to 1.6.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/kubernetes-sigs/gateway-api/releases";>sigs.k8s.io/gateway-api's releases</a>.</em></p> <blockquote> <h1>v1.6.1</h1> <h2>Major Changes Since v1.6.0</h2> <h3>Test & Conformance</h3> <ul> <li>Change the port used in <code>TCPRouteMultipleRoutesAttachment</code>. (<a href="https://redirect.github.com/kubernetes-sigs/gateway-api/issues/5053";>#5053</a>, <a href="https://github.com/davidjumani";><code>@davidjumani</code></a>)</li> <li>Respect <code>CleanupTestResources</code> for <code>BackendTLSPolicy</code>, <code>TCPRouteMultipleRoutesAttachment</code> and <code>UDPRouteMultipleRoutesAttachment</code>(<a href="https://redirect.github.com/kubernetes-sigs/gateway-api/issues/5065";>#5065</a>, <a href="https://github.com/snorwin";><code>@snorwin</code></a>)</li> <li>Fix <code>SetupTimeoutConfig()</code> not respecting defaults for <code>ListenerSetMustHaveCondition</code>, <code>ListenerSetListenersMustHaveConditions</code>, and <code>RequiredConsecutiveSuccesses</code>. (<a href="https://redirect.github.com/kubernetes-sigs/gateway-api/issues/5066";>#5066</a>, <a href="https://github.com/immanuwell";><code>@immanuwell</code></a>)</li> <li>Honour <code>tcpRouteMustHaveCondition</code> and <code>udpRouteMustHaveCondition</code> timeouts which were silently ignore. (<a href="https://redirect.github.com/kubernetes-sigs/gateway-api/issues/5067";>#5067</a>, <a href="https://github.com/immanuwell";><code>@immanuwell</code></a>)</li> </ul> <h3>Other (Cleanup or Flake)</h3> <ul> <li>Fix <code>GatewayStaticAddresses</code> test flake by waiting for status.addresses to be published instead of assuming it appears atomically with Programmed. (<a href="https://redirect.github.com/kubernetes-sigs/gateway-api/issues/5038";>#5038</a>, <a href="https://github.com/howardjohn";><code>@howardjohn</code></a>)</li> <li>Fix <code>GatewayInfrastructure</code> test flake by polling for generated infrastructure resources instead of assuming immediate visibility after the gateway is accepted. (<a href="https://redirect.github.com/kubernetes-sigs/gateway-api/issues/5047";>#5047</a>, <a href="https://github.com/howardjohn";><code>@howardjohn</code></a>)</li> <li>Fix flaky <code>TCPRouteWeightedRouting</code> and <code>UDPRouteWeightedRouting</code> conformance tests by adding a data-plane readiness check before performing weighted routing assertions. (<a href="https://redirect.github.com/kubernetes-sigs/gateway-api/issues/5064";>#5064</a>, <a href="https://github.com/arybolovlev";><code>@arybolovlev</code></a>)</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/kubernetes-sigs/gateway-api/blob/main/RELEASE.md";>sigs.k8s.io/gateway-api's changelog</a>.</em></p> <blockquote> <h1>Release Process</h1> <p>This details how releases of Gateway API are delivered. This process is exercised by a <a href="https://github.com/kubernetes-sigs/gateway-api/blob/main/RELEASE_MANAGEMENT.md";>Release Manager</a>.</p> <h2>Overview</h2> <p>The Gateway API project is an API project that has the following two components:</p> <ul> <li>Kubernetes Custom Resource Definitions (CRDs)</li> <li>Corresponding Go API in the form of <code>sigs.k8s.io/gateway-api</code> Go package</li> </ul> <p>This repository is the home for both of the above components.</p> <h2>Versioning strategy</h2> <p>The versioning strategy for this project is covered in detail in <a href="https://gateway-api.sigs.k8s.io/docs/concepts/versioning/";>the release documentation</a>.</p> <h2>Releasing a monthly version</h2> <h3>Starting point</h3> <p>Make sure all the changes that should be part of the monthly release are merged into <code>main</code>.</p> <h3>Tagging the monthly release</h3> <p>Start by tagging the <code>main</code> branch with a tag of the form <code>monthly-YYYY.MM</code> (for example, <code>monthly-2025.11</code>). Push this to GitHub.</p> <h3>Start the CI workflow</h3> <p>Trigger the <a href="https://github.com/kubernetes-sigs/gateway-api/actions/workflows/monthly-release.yml";><code>monthly-release</code></a> GitHub workflow, passing it the <code>monthly-YYYY.MM</code> tag just created.</p> <p>CI handles the rest of the release process, including creating a <strong>draft</strong> GitHub release which includes an automatically-generated changelog and the various release artifacts. <strong>You will need to publish</strong> this release after making sure that the correct artifacts are attached to it and that the CHANGELOG is what you want.</p> <h3>Writing the Release Changelog</h3> <p>In many cases, the changelog that GitHub generates is going to be OK. However, if there are significant changes in a given monthly, it can be helpful to write a changelog that's more human-readable. Given the <code>$TAG</code> used for this monthly release as well as the <code>$PREV_TAG</code> used for the</p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/kubernetes-sigs/gateway-api/commit/8bb74df00e56ec8f944d48c25e6c1c9c2f6848e3";><code>8bb74df</code></a> update vap (<a href="https://redirect.github.com/kubernetes-sigs/gateway-api/issues/5073";>#5073</a>)</li> <li><a href="https://github.com/kubernetes-sigs/gateway-api/commit/852914db3f1ebc1b89d098ce87bce766abcb6c10";><code>852914d</code></a> chore: Prep for v1.6.1 release (<a href="https://redirect.github.com/kubernetes-sigs/gateway-api/issues/5070";>#5070</a>)</li> <li><a href="https://github.com/kubernetes-sigs/gateway-api/commit/258e73170449820653b7e4260dbd25d4ffb06620";><code>258e731</code></a> fix: honor L4 route timeout YAML overrides (<a href="https://redirect.github.com/kubernetes-sigs/gateway-api/issues/5067";>#5067</a>)</li> <li><a href="https://github.com/kubernetes-sigs/gateway-api/commit/5b4813bcaeecb8d5c193e2f3bed042ca1d749a31";><code>5b4813b</code></a> fix: apply missing conformance timeout defaults (<a href="https://redirect.github.com/kubernetes-sigs/gateway-api/issues/5066";>#5066</a>)</li> <li><a href="https://github.com/kubernetes-sigs/gateway-api/commit/6a8b59084eac93cf8a94a52e56ccca171afd5f54";><code>6a8b590</code></a> [release-1.6] conformance: fix cleanup of stale objects (<a href="https://redirect.github.com/kubernetes-sigs/gateway-api/issues/5065";>#5065</a>)</li> <li><a href="https://github.com/kubernetes-sigs/gateway-api/commit/cb70397073439acb1fe7e4f52249920ef91266af";><code>cb70397</code></a> conformance: wait for TCP and UDP weighted routes to accept traffic (<a href="https://redirect.github.com/kubernetes-sigs/gateway-api/issues/5064";>#5064</a>)</li> <li><a href="https://github.com/kubernetes-sigs/gateway-api/commit/b72d94105cdf9fbc283d799fd8f4bc04d229356a";><code>b72d941</code></a> fix: stop verifying reports on release branches (<a href="https://redirect.github.com/kubernetes-sigs/gateway-api/issues/5062";>#5062</a>)</li> <li><a href="https://github.com/kubernetes-sigs/gateway-api/commit/ef67bf969c2bd4536d74980540a97fafcff9ba69";><code>ef67bf9</code></a> fix: change broken airlock link (<a href="https://redirect.github.com/kubernetes-sigs/gateway-api/issues/5056";>#5056</a>)</li> <li><a href="https://github.com/kubernetes-sigs/gateway-api/commit/ee6cc1cfebb36b4c93a855ee98606ab9ff53b733";><code>ee6cc1c</code></a> fix: only migrate deprecated status code if not already migrate (<a href="https://redirect.github.com/kubernetes-sigs/gateway-api/issues/5051";>#5051</a>)</li> <li><a href="https://github.com/kubernetes-sigs/gateway-api/commit/cc27d5ea784e0727b921ab481a8c8f32b76237e9";><code>cc27d5e</code></a> tests: Change port used in TCPRouteMultipleRoutesAttachment (<a href="https://redirect.github.com/kubernetes-sigs/gateway-api/issues/5053";>#5053</a>)</li> <li>Additional commits viewable in <a href="https://github.com/kubernetes-sigs/gateway-api/compare/v1.6.0...v1.6.1";>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]
