The version
@v1 follows the latest release, so your workflow gets fixes without editing the file.
Rename these inputs
GitHub ignores unknown inputs with only a warning, so the old names stop working without failing the run.Name a target
In v1.0 the agent could work out how to reach your app from the repository. v1.1.0 needs a target, and stops before verifying anything when it has none. Set one of:app_start_commandandapp_portfor an app that runs on the runner, usually withapp_install_commandandapp_build_commandapp_urlfor an app that is already deployed at a public URL
Choose where it runs
The newverification_mode input picks where the verification runs, and defaults to auto:
- A public repository runs on IronBee.
- A private repository with an Anthropic credential runs on your runner, as in v1.0.
- A private repository without one runs on IronBee, which needs the IronBee GitHub App on the repository.
verification_mode: local. See Platform and local verification.
An Anthropic credential is now optional. It’s needed only on your runner, or to fix findings.
What the action now does for you
- It commits the fixes. The agent only edits files. The action commits and pushes them: to the pull request branch on a pull request, otherwise to a new
ironbee/fix-<sha7>-<run_id>branch with a pull request. A fix whose re-verification fails is not pushed. - It passes or fails the job. The last step fails the job when the verification fails or ends without a verdict. If other jobs depend on this one, they now see that result.
- It writes the job summary. The report goes to the pull request comment and to the workflow run’s summary.
Changed defaults and outputs
ironbee_exclude_filesnow defaults totrue. IronBee’s generated files (.ironbee/,.claude/,.mcp.json,.gitignore) stay out of the commits the action makes.ironbee_collector_urlandironbee_console_urlare empty by default. The CLI picks the collector, and the action derives the console host from it.- The
verdictoutput can bepass,fail,not_applicableorunknown. - New outputs:
mode,job_idandjob_url.artifacts_urlis set only when the verification ran on your runner. - Every
true/falseinput also accepts1/0,yes/noandon/off. Any other value fails the run and names the input.
What changed in v1.1.1
v1.1.1 needs no change to a v1.1.0 workflow:- No duplicate report. When the repository is connected through the IronBee GitHub App, IronBee publishes a run on IronBee on the pull request itself. The action then posts no report comment, and keeps the report in the job summary. The new
platform_publishesoutput says which happened. - Your app’s telemetry.
app_start_commandandapp_restart_commandrun withIRONBEE_COLLECTOR_URLandIRONBEE_API_KEYin their environment, so an app whose OpenTelemetry exporter reads them sends its traces and logs to the verification run.
What changed in v1.2.0
v1.2.0 changes what some v1.1 workflows do. Check these against yours:- Fixing on your runner follows
verification_apply_fix. Withverification_apply_fix: false, or a comment without--fix, a run on your runner now reports what it finds and changes no file. To keep fixing there, leaveverification_apply_fixattrue, the default. - A commit holds only the fix. Only the files the fix changed are committed. On your runner, the action commits only after a verification failed and the agent verified again. With
ironbee_exclude_files: false, the setup files go in a fix commit, and a run that commits no fix commits no setup. - A scheduled run reads the repository’s visibility. With
verification_mode: auto, a schedule on a private repository with an Anthropic credential now runs on your runner, as other events do. Setverification_mode: platformto keep it on IronBee. - The reachability request sends your headers. On IronBee, the request before the run carries
app_headersandapp_secret_headers, so a bypass header gets a protected preview past it. It no longer follows a redirect: it logs where the redirect leads. See Protected deployments. - The restart after a fix rebuilds. On IronBee, the default restart stops the app with everything it started, then runs
app_build_commandandapp_start_commandagain. - A push on your runner verifies every commit in it, from the push’s
beforecommit, as on IronBee. - Comment commands are stricter. A comment that only starts with the command, such as
/ironbee-verify., runs nothing. A--fixthat the workflow doesn’t apply gets a one-line note in the report. See Verify from a pull request comment. - Local mode works in a subdirectory.
working_directorycan point below the repository’s root on your runner too. - The evidence keeps each agent’s logs. The artifact holds each session whole, with each agent’s
verdict.jsonandactions.jsonlundersessions/<id>/agents/<agentId>/.
Before and after
Next steps
Configuration
Every input and output in v1.
How it works
What happens in a run, from the plan to the report.