Previous deployment examples, from a release perspective, are imperative. For example, should a solution combine changes in both front-end (React) and back-end (NodeJS), each deployment would need to be coordinated manually to perform a Release.
Based on the Autonomous Development, Authoritative Release approach, instead of each application component deploying separately, they produce a deployable asset, and the solution is released authoritatively. The Autonomous Development pipeline outputs an immutable, versioned, environment agnostic, deployment package. For example, an Image in a Container Registry, a WAR file in Nexus/Artifactory, a Nuget Package in Octopus or a versioned zip file in a generic package store (Azure DevOps, GitLab, GitHub, etc.). This approach is based on the build once, deploy many Continuous Delivery Maturity Model.
These assets are gathered and released by an independent coordinating pipeline, the following example is based on Kubernetes Containers.
Imperative Image Construction
Declarative Desired State Container Deployment using Helm