Action version references

Pin the automation you depend on

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

A workflow depends on action code as well as application dependencies.

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…

  • Recognize another code dependency
  • Distinguish a tag from a commit

The idea

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

01Recognize another code dependency

An action runs code in the workflow environment. Its identity and update process deserve review alongside the application dependency lockfile.

02Distinguish a tag from a commit

A tag can move. Pinning a verified full commit SHA ties a reference to a specific revision, while updates must still be reviewed and maintained.

03Keep examples distinct from real revisions

The repeated-a value is only a lab fixture for recognizing a full SHA reference. A production workflow needs a real verified revision from the action publisher.

Your turn

Create verify with checkout pinned to the example full commit SHA aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa, followed by npm test. This all-a SHA is an illustrative fixture, not a real action revision to copy into production.

What the checks look for

  • Uses a full SHA reference
  • Still performs the application check
Try it in the editor →

Take this with you

Review the source and identity of automation dependencies.

Go a little further

Find how the official publisher documents recommended action pinning.

Learn CI/CD & Release Engineering for free

20 short lessons with real code and instant checks.

See the whole course →