Skip to content

Latest commit

 

History

History
23 lines (14 loc) · 1.34 KB

release-workflow.md

File metadata and controls

23 lines (14 loc) · 1.34 KB

Release workflow

Read this document before creating a pull request or changing release and deployment configuration.

Pull requests

Read defaultBase from nx.json and use it as the pull request base. Use another base only when the task names one.

Releases and deployments

Release branches and deployment workflows can affect production. Change or run them only when the user explicitly requests that work.

The workflow files under .github/workflows/ define the active branch triggers, build configurations, and deployment branches. Inspect those files before release work. Do not rely on a copied branch map in documentation.

CI builds the applications that changed since the latest successful run of the same workflow on the branch. If CI cannot find that run, it uses the commit before the push, then HEAD~1. .github/scripts/get-affected-base.sh selects this base commit.

CI writes the build/<project>/<environment> branches. Do not edit those branches directly.

The workflow generates application-specific changelogs once before the build jobs start. Each changelog includes commits that change the application, its transitive Nx dependencies, or files under shared/. Builds include CHANGELOG.md when generation and artifact transfer succeed. Changelog generation, upload, download, or copy failures do not block tests, builds, or deployment.