main - 5b010dc build: update cross-repo angular dependencies (#32997)

Author: angular-robot

docs-content/api-docs/material-tooltip.html

@@ -348,13 +348,24 @@ <h4 id="MatTooltipDefaultOptions" class="docs-header-link docs-api-h4 docs-api-i
 
 <tr class="docs-api-properties-row">
   <td class="docs-api-properties-name-cell"><p class="docs-api-property-name">
-      <code>detectHoverCapability: <code class="docs-api-property-type">boolean</code></code>
+      <code>detectHoverCapability: <code class="docs-api-property-type">boolean | (() =&gt; boolean)</code></code>
     </p>
   </td>
-  <td class="docs-api-property-description"><p>Whether the tooltip should use a media query to detect if the device is able to hover.
-Note that this may affect tests that run in a headless browser which reports that it&#39;s
-unable to hover. In such cases you may need to include an additional timeout, because
-the tooltip will fall back to treating the device as a touch screen.</p>
+  <td class="docs-api-property-description"><p>By default the tooltip attempts to detect whether the user&#39;s device is able to hover by
+consulting the <code>Platform</code> provider that was created a long time ago and is based on
+some data points that may not be entirely accurate anymore (e.g. user agent string and
+Android/iOS-specific APIs), however changing them will break existing users. You can use this
+config property to opt into a more modern detection mechanism.</p>
+<p>The supported values include:</p>
+<ul>
+<li><code>false</code> - Default value. Detection is based on the <code>Platform</code> provider.</li>
+<li><code>true</code> - The tooltip will use the <code>any-hover</code> media query for more accurate detection.
+Note that this may break existing unit tests running in a headless browser.</li>
+<li><code>() =&gt; boolean</code> - If the automatic detection doesn&#39;t work properly in your case (e.g. the
+<code>any-hover</code> media query isn&#39;t supported) and you&#39;re able to detect more accurately, you can
+pass in a function that will be used for detection instead. It should return <code>true</code> if the
+device <strong>has the ability to hover</strong>, or <code>false</code> if it cannot.</li>
+</ul>
 </td>
 </tr>
 

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@angular/components-examples",
-  "version": "22.0.0-next.2+sha-43320d4",
+  "version": "22.0.0-next.2+sha-5b010dc",
   "description": "Angular Components Examples",
   "private": true,
   "repository": {
@@ -255,15 +255,15 @@
   },
   "homepage": "https://github.com/angular/components#readme",
   "peerDependencies": {
-    "@angular/aria": "22.0.0-next.2+sha-43320d4",
-    "@angular/cdk": "22.0.0-next.2+sha-43320d4",
-    "@angular/cdk-experimental": "22.0.0-next.2+sha-43320d4",
+    "@angular/aria": "22.0.0-next.2+sha-5b010dc",
+    "@angular/cdk": "22.0.0-next.2+sha-5b010dc",
+    "@angular/cdk-experimental": "22.0.0-next.2+sha-5b010dc",
     "@angular/core": "^22.0.0-0 || ^22.1.0-0 || ^22.2.0-0 || ^22.3.0-0 || ^23.0.0-0",
     "@angular/common": "^22.0.0-0 || ^22.1.0-0 || ^22.2.0-0 || ^22.3.0-0 || ^23.0.0-0",
-    "@angular/material": "22.0.0-next.2+sha-43320d4",
-    "@angular/material-experimental": "22.0.0-next.2+sha-43320d4",
-    "@angular/material-luxon-adapter": "22.0.0-next.2+sha-43320d4",
-    "@angular/material-date-fns-adapter": "22.0.0-next.2+sha-43320d4"
+    "@angular/material": "22.0.0-next.2+sha-5b010dc",
+    "@angular/material-experimental": "22.0.0-next.2+sha-5b010dc",
+    "@angular/material-luxon-adapter": "22.0.0-next.2+sha-5b010dc",
+    "@angular/material-date-fns-adapter": "22.0.0-next.2+sha-5b010dc"
   },
   "devDependencies": {
     "@angular/aria": "workspace:*",