Versions and pinning

Your workflow references the action with a uses: ref, almost always the moving major tag pullfrog/pullfrog@v0. That ref pins less than it appears to.

How the action is versioned

The published action is a thin bootstrap. The code behind both of its steps, the agent and the post-run cleanup that saves rotated credentials, comes from npm at ^<version>, so a run's behavior tracks the latest release in the current version line.

The uses: ref fixes two things:

  • The input and output contract, read from the action's action.yml.
  • The npm range the bootstrap resolves: ^<version> as of the pinned revision.

The pullfrog/pullfrog@v0 tag tracks the latest v0.x release. The console writes this ref, and it is the recommended one.

Pinning to a commit SHA

GitHub's security hardening guide recommends pinning third-party actions to a full commit SHA, because tags can move. Dependabot, StepSecurity and pin-github-action do this for you and keep the version as a comment:

.github/workflows/pullfrog.yml
uses: pullfrog/pullfrog@abc123… # v0

A pinned SHA takes both steps from npm the same way the tag does, so the agent and the cleanup step still receive patch releases. Updating the pin is what picks up a new minor version. Dependabot bumps the SHA and the # v0 comment together:

.github/dependabot.yml
version: 2
updates:
  - package-ecosystem: github-actions
    directory: /
    schedule:
      interval: weekly

Freezing the code

A pinned SHA still installs the newest patch from npm. To run exactly the code at the pinned commit, set PULLFROG_FORCE_LOCAL_CLI in the step's env::

.github/workflows/pullfrog.yml
- uses: pullfrog/pullfrog@abc123… # v0.1.137
  env:
    PULLFROG_FORCE_LOCAL_CLI: "1"

The run then uses that commit's source and the dependency versions its lockfile pins. A frozen workflow gets no fixes, security fixes included, until the pin moves, so keep Dependabot bumping the SHA and merge its updates promptly.

Choosing a ref

You wantUse
The simplest setup that stays currentpullfrog/pullfrog@v0
SHA pinning for a security policyA commit SHA, with Dependabot to pick up new minor versions
Code that changes only when you move the pinA commit SHA with PULLFROG_FORCE_LOCAL_CLI: "1"

OpenCode version

Runs on OpenCode are moving to OpenCode V2, and a run with no pin can use either version during the rollout. A repo stays on V1 when its checkout has code only V1 can load.

Written for V1Runs on
A plugin or custom tool in .opencode/plugin(s) or .opencode/tool(s)V1 only
A plugin list in opencode.jsonV1 only
Agents, commands, skills, MCP servers and permissionsV2, as they are

To choose a version yourself, set PULLFROG_OPENCODE_VERSION to 1 or 2 in the env: of your workflow:

.github/workflows/pullfrog.yml
env:
  PULLFROG_OPENCODE_VERSION: "1"

Each run logs its choice, for example » opencode: V2 (default).

© 2026 Pullfrog, Inc.

On this page