Repository navigation
v0.1.2 beta
Changes
- Add optional
core-refto select a reviewed full lowercase 40-character Behavior Diff core commit SHA. Omit it to retain the release's default core v0.4.6 pin. - Freeze the selected core revision during preparation. Run and publish inherit it, reject conflicting overrides, and reject evidence from another revision. Core code is fetched only from
spacedock-dev/behavior-diff. - Record the selected core SHA in published results. A core override selects executable code with access to model credentials; review that commit before using it.
- Introduce the moving
v0.1tag. Each publishedv0.1.xrelease, including beta prereleases, must advance this alias to the same reviewed commit. Exact patch tags remain fixed. The release guide now includes the required update, race-safe push and verification steps. - Update the README and complete workflow example.
Upgrade
Use the same Action version in prepare, run and publish. Selection schema 2 includes the frozen core revision; old selections are rejected. Prepare a new selection rather than mixing Action versions across jobs.
# Follow beta patch releases:
uses: spacedock-dev/behavior-diff-action@v0.1
# Or select this exact release:
uses: spacedock-dev/behavior-diff-action@v0.1.2For an immutable pin, use spacedock-dev/behavior-diff-action@32f1bc3bf8c8a2588a0cca5aca44d9cee4de7b93.
Complete workflow · Core override configuration
Beta limitations
Live model authentication, real GitHub artifact upload/download and PR comment updates remain unverified. HTML reports are uploaded without ZIP wrapping; inline browser rendering from artifact links has not been verified. Read SECURITY.md and review code, credentials, disclosure and provider spending limits before enabling the Action.
Full changelog: v0.1.1...v0.1.2