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
Copy file name to clipboardExpand all lines: README.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -85,7 +85,7 @@ schema-capable model is available.
85
85
```bash
86
86
docker run --rm \
87
87
-v /path/to/artifacts:/workspace/artifacts \
88
-
ghcr.io/github/gh-aw-threat-detection:v1.0.0 \
88
+
ghcr.io/github/gh-aw-threat-detection:v0.0.2 \
89
89
/workspace/artifacts
90
90
```
91
91
@@ -129,7 +129,7 @@ Replay uses the dispatching repository's `GITHUB_TOKEN`; no extra replay token i
129
129
Common dispatch examples:
130
130
131
131
- Current checkout, direct CLI replay: set `run_id`, leave `detector_source=current`, `engine=copilot`, and `use_awf=false`.
132
-
- Released detector replay: set `detector_source=release` and `detector_ref` to a release tag such as `v1.0.0`.
132
+
- Released detector replay: set `detector_source=release` and `detector_ref` to a release tag such as `v0.0.2`.
133
133
- Image detector replay: set `detector_source=image` and optionally set `detector_ref` to an image tag. The workflow extracts the `threat-detect` binary from the image and runs it on the host so the selected engine CLI can be installed there.
134
134
- Model comparison: set `model` to the engine-specific model name to pass through `--model`.
135
135
- Additional detection instructions: set `custom_prompt`; it is passed as `CUSTOM_PROMPT` and appended to the default detector prompt.
@@ -168,7 +168,7 @@ Maintainers need to configure the following before the image is consumed by `gh-
168
168
2. Ensure the package created under `ghcr.io/github/gh-aw-threat-detection` inherits repository visibility or is explicitly private.
169
169
3. Grant the consuming `github/gh-aw` repository access to the private package, or configure the organization package settings so `GITHUB_TOKEN` from `gh-aw` can pull it with `packages: read`.
170
170
4. Keep the `release-publish` and `release-promote` environments if manual approval is desired; otherwise update the environment protection rules in repository settings.
171
-
5. Tag releases with semantic versions such as `v1.0.0`. The release workflow publishes the version tag; the promote workflow tags the verified digest as `latest`.
171
+
5. Tag releases with semantic versions such as `v0.0.2`. The release workflow publishes the version tag; the promote workflow tags the verified digest as `latest`.
172
172
173
173
No additional secrets are required for unit tests, `make build`, `make test`, or the container smoke test. Engine authentication is only needed when running real AI-backed detection:
174
174
@@ -241,7 +241,7 @@ Optional Actions variables:
241
241
|----------|---------|
242
242
|`GH_AW_MODEL_AGENT_COPILOT`, `GH_AW_MODEL_AGENT_CLAUDE`, `GH_AW_MODEL_AGENT_CODEX`| Override the agent model for each smoke workflow. |
243
243
|`GH_AW_MODEL_DETECTION_COPILOT`, `GH_AW_MODEL_DETECTION_CLAUDE`, `GH_AW_MODEL_DETECTION_CODEX`| Override the detection model for each engine. |
244
-
|`GH_AW_THREAT_DETECTION_IMAGE`| Override the detector image used by the `*-container.lock.yml` siblings. Defaults to `ghcr.io/github/gh-aw-threat-detection:v1.0.0`. |
244
+
|`GH_AW_THREAT_DETECTION_IMAGE`| Override the detector image used by the `*-container.lock.yml` siblings. Defaults to `ghcr.io/github/gh-aw-threat-detection:v0.0.2`. |
245
245
246
246
### Build
247
247
@@ -290,7 +290,7 @@ After containerization, `gh-aw` references this component via:
0 commit comments