All notable changes to this project are documented here.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
1.0.1 - 2026-09-30
VERSIONfile,CHANGELOG.md, andCONTRIBUTING.mdestablishing the Git Flow, semantic versioning, changelog, and documentation policy for this repository.developintegration branch. Feature work now branches fromdevelopand reachesmainthrough arelease/*branch.
- Release tagging is now two-tier: an immutable
vX.Y.Ztag per release plus the floatingv1major tag that workflow consumers pin to. - README now documents the
config-pathinput and adds an Outputs table. - README states plainly that
fail-onis not implemented yet and that the declared outputs are never populated, so nobody relies on either as a merge gate or in a later step. - The "Full scan with LLM docstrings" example now actually sets
scan-mode: full, and README explains how to pass provider credentials throughenv:from secrets.
1.0.0 - 2026-06-11
- Initial release of the OpSentry composite GitHub Action.
- Three scan types selectable via
scan-type:security,code-health,governance, orall. scan-modeinput to scan only PR-changed files (changed) or the whole tree (full).fail-onseverity threshold input (critical,high,medium,low,none).auto-fixinput that applies safe fixes and commits them to the PR branch.post-commentinput that publishes scan results as a PR comment.llm-providerinput for docstring generation (bedrock,anthropic,openai,local,none).- Outputs:
findings-count,critical-count,high-count,report-path.