Create & reconcile a release
A release is where Reloqui produces its core answer. This guide covers the full lifecycle.
1. Create a release
Section titled “1. Create a release”Releases → New release. Set:
- Service (scope) and version (e.g.
2.0.0). - Release type (
minor,hotfix, …). - Git tag and/or release branch.
- Baseline / compareFrom (optional) — the previous published release, an explicit timestamp, or a 90-day fallback. This bounds the window of evidence considered.
POST /api/v1/releases{ "projectId": "proj_…", "scopeRef": "svc_…", "version": "2.0.0", "gitTag": "v2.0.0" }The release starts in draft.
2. Reconcile
Section titled “2. Reconcile”Open the release and click Reconcile (or POST /api/v1/releases/{id}/reconcile). The engine runs its stages (see Core concepts) and produces:
- Included evidence — PRs, issues, artifacts, builds, deployments, each with a classification and reason.
- Confidence score + tier and a component breakdown.
- Counts — prs, issues, artifacts, deployments, orphans, exceptions, rollbacks, notable.
- Exceptions — orphans, uncertain items, force-pushes.
The release moves to ready, ready_with_exceptions, or blocked_by_policy.
3. Explore the evidence
Section titled “3. Explore the evidence”Release 360 shows the full evidence graph. Filter the evidence explorer by bucket (pr, issue, artifact, deployment, infra), classification, or notability. Each item exposes its evidenceId, reason code, and — for heuristic matches — the rule that placed it.
4. Curate (human-in-the-loop)
Section titled “4. Curate (human-in-the-loop)”The engine is deterministic-first, but you stay in control:
- Manual link — pull a specific event into the release with a required reason (even if it’s outside the window).
- Manual unlink — exclude an item with a reason.
Both survive future recomputes (they’re re-applied by stable evidence id) and are recorded in the revision trail.
5. Notable changes
Section titled “5. Notable changes”Reloqui classifies notable items — breaking, security, deprecation, feature, fix — from conventional-commit and marker patterns. They lead every audience’s release notes and are filterable in the evidence explorer.
6. Recompute options
Section titled “6. Recompute options”- Full reconcile — re-collect and re-attribute (use after new evidence arrives).
- Scoring-only recompute — recompute confidence without re-collecting (
POST /reconcile {"scope":"scoring"}). - Rescore action — the same via the self-service actions catalog.
7. Compare & dependencies
Section titled “7. Compare & dependencies”- Compare two releases:
POST /api/v1/releases/compare { "fromReleaseId": …, "toReleaseId": … }— added/removed evidence and confidence delta. - Dependency changes:
GET /api/v1/releases/{id}/changes/dependencies— manifest diffs (package.json, requirements.txt, go.mod, pyproject.toml) between baseline and release.
8. Publish
Section titled “8. Publish”When the release is ready/approved and passes policy, click Publish. Reloqui:
- freezes an immutable snapshot (release, evidence, gate results, notes, approvals),
- supersedes any prior published release on the same scope,
- emits
release.published, fanning out to your notification channels.
9. Edit & roll back
Section titled “9. Edit & roll back”- Edit metadata pre-publish:
PATCH /api/v1/releases/{id}(version, tag, branch). Published releases are immutable. - Roll back a published release with a reason — see Rollbacks & incidents.