fix(attest): export install path so verify steps can find cimon#121
Merged
Conversation
PR #114 scoped the action's install directory to $RUNNER_TEMP/cimon-<run_id>-<run_attempt>-<job>/ as a security fix, but the docs + customer-facing demo workflow still hardcode the pre-#114 path of $RUNNER_TEMP/cimon/. A naive `cimon.exe attest verify` step following the action now fails with "cimon.exe not found". Surface the install path three ways so workflows can pick whichever fits their pattern without ever reconstructing the per-job tmpdir layout: 1. core.addPath(dir) — `cimon` / `cimon.exe` resolves on PATH for plain `run:` steps in the same job. 2. CIMON_PATH env var — absolute path, for callers that bypass PATH (locked-down self-hosted runners). 3. step output cimon-path — chains cleanly into other jobs via ${{ steps.<id>.outputs.cimon-path }}. Applies to all three install branches (Windows release-zip, Linux install.sh, and the release-path input override). After this lands, the docs example collapses from $exe = Join-Path $env:RUNNER_TEMP 'cimon\cimon.exe' & $exe attest verify ... to just cimon.exe attest verify ... — which is also what every other Marketplace action does. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
RoniCycode
approved these changes
May 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
#114 scoped the action's install directory to
\$RUNNER_TEMP/cimon-<run_id>-<run_attempt>-<job>/as a security fix, but the docs and the customer-facing demo workflow still hardcode the pre-#114 path\$RUNNER_TEMP/cimon/. A naivecimon.exe attest verifystep following the action now fails withcimon.exe not found.Fix: expose the install path three ways so workflows never reconstruct the per-job tmpdir layout:
core.addPath(dir)—cimon/cimon.exeresolves on PATH in the same job.CIMON_PATHenv var — absolute path, for callers that bypass PATH (locked-down self-hosted runners).cimon-path— chains cleanly into other jobs via\${{ steps.<id>.outputs.cimon-path }}.Applies to all three install branches (Windows release-zip, Linux
install.sh, and therelease-pathinput override).After this lands
The docs verify step in docs/provenance/3-integrations/9-windows-ghes.md and the demo workflow collapse from:
pwsh \$exe = Join-Path \$env:RUNNER_TEMP 'cimon\cimon.exe' & \$exe attest verify ...to just:
pwsh cimon.exe attest verify ...Test plan
attest/dist/index.jssucceedsverify-attest-windowsjob in this PR's CI passes (and now exercises the new behavior end-to-end onwindows-latest)@v1, then update demo + docs to drop the path construction🤖 Generated with Claude Code