Repository navigation
v0.1.1 beta
Changes
- Upload HTML reports separately with
upload-artifactv7.0.2 andarchive: false. Each report has a unique run/attempt/target filename, so parallel comparisons do not collide. - Link PR summaries and the
report-urloutput to the single HTML artifact. Keep the evidence ZIP for validated summary generation and as a backup when the separate HTML artifact is unavailable. - Upgrade Behavior Diff core to v0.4.6, pinned to
5b325ed40062bb819c574e4172da04f53b53b953. - Update the README, configuration reference and example workflow for v0.1.1.
Usage
Use spacedock-dev/behavior-diff-action@v0.1.1 in all three phases, or pin the reviewed release commit:
uses: spacedock-dev/behavior-diff-action@d0ca905940bf694ad2fe6738fe10464e9a7e9628Complete workflow · Marketplace
Verification and limitations
Release commit CI passed. Local verification passed 72 deterministic tests, Python compilation, Actionlint and Action metadata validation. A smoke through the actual v0.4.6 core completed both trials and extraction with synthetic model responses; the generated Summary was projected successfully and the separate HTML file matched the bundled report byte-for-byte.
This remains a beta for controlled evaluation. Live model authentication, real artifact upload/download and PR comment updates remain unverified. Direct HTML upload removes ZIP extraction; inline browser rendering from the GitHub artifact link has not been verified. Links require GitHub sign-in and repository access and expire with artifact retention or deletion.
Agent execution is not an untrusted-code sandbox. Review SECURITY.md, approve code and disclosure, and set provider spending limits before enabling credentials.
Full changelog: v0.1.0...v0.1.1