You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 2c3ec8a
Browse filesBrowse the repository at this point in the historyBrowse files
constmessage=`The setup runtime requires a workflow compiled with gh-aw ${PROVENANCE_MINIMUM_COMPILER_VERSION} or newer. Update gh-aw, run \`gh aw compile\`, and commit the regenerated workflow.`;
236
+
core.summary
237
+
.addRaw("### Incompatible compiled workflow\n\n")
238
+
.addRaw(`This workflow was compiled with \`${compiledVersion}\`, but safe-output publishing now requires execution provenance added in \`${PROVENANCE_MINIMUM_COMPILER_VERSION}\`.\n\n`)
239
+
.addRaw("**Action required:** Update `gh-aw`, run `gh aw compile`, and commit the regenerated workflow.\n");
Copy file name to clipboardExpand all lines: docs/src/content/docs/reference/releases.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -85,6 +85,8 @@ At runtime, the activation job fetches `.github/aw/compat.json` and compares the
85
85
86
86
This means that if you compiled a workflow months ago with an older version of `gh aw`, you may see a warning (or failure) asking you to recompile with a newer version. Run `gh aw upgrade` to bring all workflows up to date.
87
87
88
+
Setup action dependency upgrades can also introduce runtime requirements that older generated workflows do not meet. If activation reports that a workflow is too old for safe-output publishing, update `gh-aw`, run `gh aw compile`, and commit the regenerated workflow files. Updating only the pinned setup action is not sufficient; older workflows must pass the publishing job's check-run context for execution provenance. This requirement is enforced by the newer setup runtime and does not retroactively block workflows that remain pinned to an older runtime.
89
+
88
90
## How Lock Files Are Pinned
89
91
90
92
When `gh aw compile` generates a `.lock.yml`, it pins every GitHub Actions reference to a commit SHA:
0 commit comments