Release validation workflows

This page is an index. Release validation is documented on five pages, one per reader job. Open the page that matches your task.

Full Release Validation retains all six Docker seed lanes, QA Smoke, and Control UI performance through its normal CI child. Every admitted canonical main run keeps the published-upgrade survivor; the other five Docker seed lanes run in ordinary manual/release validation, including npm qualification scopes. Pull requests and exact-head PR fallbacks omit Docker seed and QA Smoke. See full release coverage for the exact survivor contract and target compatibility limits.

Page	Read it when
Full Release Validation	The release umbrella: Validation/Tooling SHA binding, release publish, Docker Release, profiles, and recovery.
Live and E2E shards	The named live/E2E shards, their coverage, and the images they run in.
Package Acceptance	Validating one installable tarball: jobs, candidate sources, suite profiles, and examples.
Install smoke and Docker E2E	Install Smoke coverage, the local Docker E2E aggregate and tunables, and release-path chunks.
Plugin Prerelease	The separate, more expensive plugin product/package suite and when it is dispatched.

The bounded hybrid hosted offload applies only to automatic CI first attempts. Full Release Validation, candidate/artifact workflows, and frozen-target workloads retain their existing coverage and runner routes.

Where each section moved

Every section heading from the previous single-page version keeps its anchor here, so an existing link such as /ci/release-validation#suite-profiles still resolves. Each entry points at the page that now holds the content.

• Full Release Validation
• Live and E2E shards
• Package Acceptance
• Jobs
• Candidate sources
• Suite profiles
• Legacy compatibility windows
• Examples
• Install smoke
• Local Docker E2E
• Tunables
• Reusable live/E2E workflow
• Release-path chunks
• Plugin Prerelease

Related

• Install overview
• Release channels