Finalize 25.10 migration notes (#6502)

---------

Signed-off-by: Ben Sherman <[email protected]>
Co-authored-by: Chris Hakkaart <[email protected]>

Author: bentsherman

docs/migrations/25-10.md

@@ -1,12 +1,8 @@
 (migrating-25-10-page)=
 
-# Migrating to 25.10 (preview)
+# Migrating to 25.10
 
-This page summarizes the upcoming changes in Nextflow 25.10, which will be released in October 2025.
-
-:::{note}
-This page is a work in progress and will be updated as features are finalized. It should not be considered complete until the 25.10 release.
-:::
+[Nextflow 25.10](https://github.com/nextflow-io/nextflow/releases/tag/v25.10.0) was released on October 22, 2025.
 
 ## New features
 
@@ -148,6 +144,26 @@ Nextflow supports Groovy-style type annotations using the `<type> <name>` syntax
 
 See {ref}`migrating-static-types` for details.
 
+<h3>Auth and Launch commands</h3>
+
+The Nextflow CLI has two new commands: `nextflow auth` and `nextflow launch`. Together, they allow you to authenticate with Seqera Platform and launch pipelines from the command line. This approach streamlines the previous workflow of using `nextflow run` with the `-with-tower` option.
+
+```bash
+# Authenticate with Seqera Cloud
+nextflow auth login
+
+# Check authentication status
+nextflow auth status
+
+# Configure Seqera Platform settings
+nextflow auth config
+
+# Launch a pipeline in Seqera Platform
+nextflow launch nextflow-io/hello
+```
+
+See {ref}`cli-auth` and {ref}`cli-launch` for details.
+
 ## Enhancements
 
 <h3>Nextflow plugin registry</h3>
@@ -226,6 +242,8 @@ This feature addresses previous inconsistencies in timestamp representations.
 
 ## Breaking changes
 
+- The `google-lifesciences` executor is no longer supported because the Google Cloud Life Sciences API was discontinued in July 2025. Use the `google-batch` executor instead.
+
 - The AWS Java SDK used by Nextflow was upgraded from v1 to v2, which introduced some breaking changes to the `aws.client` config options. See {ref}`the guide <aws-java-sdk-v2-page>` for details.
 
 - The `nextflow.config.schema` package was renamed to `nextflow.config.spec`. Plugin developers that define custom {ref}`configuration scopes <dev-plugins-extension-points-config>` will need to update their imports accordingly.
@@ -235,3 +253,12 @@ This feature addresses previous inconsistencies in timestamp representations.
 - The legacy type detection of CLI parameters is disabled when using the strict syntax (`NXF_SYNTAX_PARSER=v2`). {ref}`Legacy parameters <workflow-params-legacy>` in the strict syntax should not rely on legacy type detection. Alternatively, use the new `params` block to convert CLI parameters based on their type annotations. Legacy type detection can be disabled globally by setting the environment variable `NXF_DISABLE_PARAMS_TYPE_DETECTION=true`.
 
 - The use of workflow handlers in the configuration file has been deprecated. You should define workflow handlers in the pipeline script or a plugin instead. See {ref}`config-workflow-handlers` for details.
+
+- The `nextflow.enable.configProcessNamesValidation` feature flag is deprecated. It was originally introduced to suppress false warnings for process selectors targeting conditional processes. The {ref}`strict syntax <strict-syntax-page>` now validates process selectors without producing false warnings.
+
+## Miscellaneous
+
+- New config option: `docker.registryOverride`
+- New config options: `wave.build.compression.*`
+- New executor: Fujitsu Technical Computing Suite (`tcs`)
+- Support Java 25