The post-release baseline loop

A triggered release workflow that runs standard benchmarks against the completed release and records a reproducible baseline for future comparisons.

Use when

Use this immediately after a release when future regressions or improvements need to be measured against the exact version now in production.

The loop

After current releases finish, run the standard benchmarks and record the results as the new baseline.

Steps

• Confirm every in-scope release is complete and record the production revision or artifact identity.
• Run the standard benchmark suite under its documented environment, data, warm-up, and repetition rules.
• Investigate invalid or unstable runs, then rerun only under the same documented conditions.
• Store the final results with the release identity and benchmark metadata, and mark them as the new comparison baseline.

Verification

The new baseline belongs to the completed release. Revision, environment, benchmark version, conditions, and results are recorded together.

Why it works

Tying the baseline to a verified release creates a trustworthy reference point for later performance and quality work. Recording the conditions prevents unrelated environment changes from masquerading as product changes.