deployment_flow

On push to main, the release workflow first completes ci_gate.
If pending changesets remain, it then applies them with `pnpm changeset version`.
This bumps package. json for each affected package and writes changelogs.
prepare-native-packages.mjs then copies the `@reqlan/analytical` version onto each platform package ( version_management ).
The workflow commits the result, creates annotated tags for every bumped publishable package, and pushes the commit and tags back to main.
Release tags use `site/v{version}`, `ext/v{version}`, `language/v{version}`, `analytical/v{version}`, `cli/v{version}`, and `mcp/v{version}` where `{version}` is the semver from that package's package. json.
Deployment is tag-driven for every channel per release_tagging; after ci_gate, the release workflow only versions and tags.
GitHub Actions pushes with the default `GITHUB_TOKEN` do not trigger other workflows, so site and npm deploy are also invoked directly from the release workflow.
Optional `RELEASE_PAT` allows tag pushes to trigger downstream workflows for manual reruns and external CI.
Recursive runs are prevented by skipping the release workflow for release commits.
Tag patterns and downstream deploy workflows follow release_tagging.
The implementation lives in release.yml.

Jump to outbound references

Jump to inbound references