Inspiration
Generating code is only part of shipping software. Teams still need to identify regressions, run the right tests, understand CI evidence and prevent unsafe releases. ReleaseProof makes that post-code decision inspectable and reproducible.
What it does
ReleaseProof is a release-readiness system for merge requests. A custom GitLab Duo agent, ReleaseProof Impact Analyst, reviews a bounded merge-request diff context and proposes affected business behaviours and approved checks. ReleaseProof's deterministic policy then uses actual CI job results, evidence and the exact source SHA to decide whether a release is BLOCK, INCONCLUSIVE, STALE or READY FOR APPROVAL. The agent does not override release policy or deploy code.
An ordering-system demonstration exposes real regressions such as incorrect money calculations and quantity handling. The local demo creates broken and corrected revisions with test evidence. The real GitLab integration assessed MR !2 (SHA 9c15d8f1adb635d224f44321464c399b7f445f50) and returned BLOCK, linked to pipeline 2986316547.
How it was built
TypeScript/Node.js services and test suites implement approved check selection, evidence ingestion, release policy and reporting. GitLab CI/CD supplies source-revision-specific test jobs and pipeline artifacts. A private, tool-free GitLab Duo custom agent is configured to analyse a reviewed JSON MR packet and return structured check suggestions. The live integration imports an invocation envelope from the operator's Duo Chat interaction; it is a manual Assisted workflow, not an autonomous MR trigger.
Challenges and learning
Separating AI suggestions from enforceable release policy helps avoid allowing model output to approve deployments. The evidence pipeline distinguishes failing, missing and outdated checks and binds assessments to Git commit SHAs. Deliberately broken and corrected scenarios test these distinctions.
What's next
Complete and publish the video demonstration, retain verifiable screenshots/transcripts of the custom GitLab Duo invocation, and extend the integrated workflow while retaining explicit human approval for deployment.
Repository and evidence
The source repository must contain the complete project and MIT license for judging.
Built With
- gitlab
- gitlab-ci/cd
- gitlab-duo-agent-platform
- node.js
- playwright
- typescript
- vitest
