diff --git a/docs/en/install-upgrade/release-notes/release-notes-elasticsearch-rc1.asciidoc b/docs/en/install-upgrade/release-notes/release-notes-elasticsearch-rc1.asciidoc
index 7e9f06153..50b8f4235 100644
--- a/docs/en/install-upgrade/release-notes/release-notes-elasticsearch-rc1.asciidoc
+++ b/docs/en/install-upgrade/release-notes/release-notes-elasticsearch-rc1.asciidoc
@@ -28,6 +28,21 @@ The dropped ciphers are `TLS_RSA_WITH_AES_256_GCM_SHA384`, `TLS_RSA_WITH_AES_128
 // TLS::
 // * Drop `TLS_RSA` cipher support for JDK 24 {es-pull}123600[#123600]
 
+[discrete]
+[[breaking_90_esql_changes]]
+==== ES|QL changes
+
+[[limit_scope_skip_unavailable_setting_remote_clusters]]
+.Limit the scope of the skip_unavailable setting for remote clusters
+[%collapsible]
+====
+*Details* +
+Before this change, ES|QL would honor the skip_unavailable setting for nonmatching indices errors at planning time, meaning that when a query with a concrete (non-wildcarded) index was issued to a cluster where skip_unavailable=true, the index would be skipped, allowing the query to proceed on any other specified clusters rather than returning an error.
+
+*Impact* +
+Remote clusters, regardless of their skip_unavailable setting, will now use the same logic as the local cluster for index expression analysis at plan time. As a result, any missing concrete index in your index expression will return an error rather than partial results.
+====
+
 [discrete]
 [[deprecated-9.0-rc1]]
 === Deprecations