Question

In a single job, a build step generates a version string and writes it with `echo "VERSION=1.4.2" >> "$GITHUB_ENV"`. A later step in the same job needs to reference this value, and a downstream job listed in `needs` must also consume it. The engineer sets `id: build` on the writing step. Which approach correctly makes the value available to both the later step in the same job AND the downstream job?

Accepted Answer

Keep the `$GITHUB_ENV` write for same-job steps (referenced as `${{ env.VERSION }}`), also write to `$GITHUB_OUTPUT` and declare a job-level `outputs:` mapping so the downstream job can read `needs.<job>.outputs.version`.

Answer

The `$GITHUB_ENV` write already exposes the value as `env.VERSION` to later steps in the same job and, because the step has an `id`, it is automatically available to downstream jobs via `needs.build.outputs.VERSION`.

Answer

Replace the `$GITHUB_ENV` write with `$GITHUB_OUTPUT` only; later steps in the same job read `${{ env.VERSION }}` and downstream jobs read `${{ steps.build.outputs.version }}`.

Answer

Write only to `$GITHUB_ENV`; downstream jobs inherit all environment variables set by any job they list in `needs`, so no extra configuration is required.