v2.26.0
Latest
Added
- Compliance evaluations can now be scoped to a single ruleset, rule, or batch of rules, re-evaluating only what you specify while carrying forward prior results for everything else.
- Triggering an evaluation against a specific branch, tag, or commit now evaluates that exact commit, rather than always using the current checkout.
- Evaluation and workspace API responses now include more context: a direct link to the results page, whether each rule is enabled or disabled, and a way to resolve workspace context directly from a repository URL.
Improved
- Evaluation and workspace APIs now correctly scope results to the requested branch, ruleset, or workspace type, fixing several cases where they mixed in unrelated data.
Fixed
- Fixed several issues where triggering or checking a compliance evaluation could return a stale or incorrect evaluation (from before the trigger, for the wrong ruleset or rule, or for an outdated commit) instead of the current one.
- Fixed a bug where evaluation results could be incorrectly reused after the active rules in the ruleset had changed.
- Workspaces can no longer be attached to a ruleset that has been disabled at the enterprise level, closing a way to bypass governance.