Changelog
What shipped, and what it decided.
Every entry below was verified before it was published: a person confirmed each decision the code made, and the release note was written from those confirmations rather than from commit messages.
Releap 2.4
Suppression rules can be scoped per workspace, with a required written reason. Security-classified decisions cannot be suppressed at all — a rule learned in one workspace leaking into another was a finding in our SOC 2 audit.
Releap 2.3
Knowledge articles inherit code bindings from their folder, which removes most of the setup work behind staleness detection.
SOC 2 Type 1
Proga Digital has completed its SOC 2® Type 1 examination for the Security, Confidentiality and Availability Trust Services Criteria, performed by Prescient Assurance. Type 2 observation period now underway.
Releap 2.2
Azure DevOps Repos and Boards are now peers to GitHub and Jira rather than a secondary path.
This page is a product demonstration
These entries come out of the same loop we sell: Verify records what each merge decided, somebody confirms it, and Comms drafts the customer-facing note from those confirmations for the Customers audience. Unconfirmed changes are held back rather than described wrongly.