Commit-based release identity

Tie an artifact to its source revision

Lesson 16 of 20 · 12 min · Module 5: Environments and release identity

A release reference should help answer which change reached an environment.

Start this lesson →

Free. No installation: you write and run the code in your browser, and it is checked automatically.

By the end, you’ll be able to…

  • Carry source identity forward
  • Resolve the run context

The idea

A workflow combines an event boundary, job dependencies, and ordered steps. Conditions and prerequisite outcomes determine which jobs can run.

01Carry source identity forward

The source commit is useful metadata for build artifacts, deployment records, and incident investigation.

02Resolve the run context

github.sha is provided by the real workflow context. The lab substitutes its scenario SHA so the recorded release can be checked deterministically.

03Record more than a display name

A commit tag helps trace source. An actual image digest and deployment record provide stronger evidence of the exact content that ran.

Your turn

Create release with run lab deploy notes:${{ github.sha }} in staging. The lab SHA is a1b2c3d. Verify the recorded deployment uses notes:a1b2c3d.

What the checks look for

  • References the source context
  • Deploys the resolved lab reference
Try it in the editor →

Take this with you

Keep source, artifact, and deployment identity connected.

Go a little further

Design a release record containing commit, artifact digest, environment, and time.

Learn CI/CD & Release Engineering for free

20 short lessons with real code and instant checks.

See the whole course →