Skip to content

Code Tribunal 1.0.0-rc.1

Pre-release
Pre-release

Choose a tag to compare

View all tags
@seanleecoder seanleecoder released this 21 Jul 21:10
· 230 commits to main since this release
v1.0.0-rc.1
d0f6adc
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Code Tribunal 1.0.0-rc.1

This release candidate publishes the 1.0 container/template distribution for
operator validation before the final v1.0.0 tag.

Release identity

  • Runtime source R: 15d424feea730a04338ed423bf93b8797d807bbc
  • Release-candidate evidence branch commit: recorded in the v1.0.0-rc.1 tag
  • Base image:
    ghcr.io/seanleecoder/code-tribunal/ai-review-base:1.0-15d424feea730a04338ed423bf93b8797d807bbc@sha256:28ddb7ed1c4e0986606011793c31955751df61ce2d25a0def0f47e1eecf97eee
  • Reviewer image:
    ghcr.io/seanleecoder/code-tribunal/ai-review-reviewer:1.0-15d424feea730a04338ed423bf93b8797d807bbc@sha256:cba20164abaaad10a37ec6d27f17bf55662b70d32339830fba3092117dbe7a8d
  • Release inputs: release/release-inputs.json, active for 1.0.0
  • Publication run: 29845398524
  • CI validation run: 29845398459

Scope

  • Supported distribution is the digest-pinned container images plus the GitHub
    Actions and GitLab CI templates.
  • Python source imports remain an unsupported contributor/testing mechanism.
  • Release-input validation, supply-chain pin checks, documentation checks,
    mypy, unit/integration tests, and compilation passed on the RC evidence
    branch before publication.
  • GitHub and GitLab exact-value secret audits were completed by the operator on
    2026-07-21 without recording secret values in the repository.

RC known gaps

These gaps are accepted for 1.0.0-rc.1 and must be completed or explicitly
waived before final v1.0.0:

  • GitHub oversized raw-diff HTTP 406 has not been exercised live. Unit coverage
    verifies the fail-closed message and no-bundle behavior.
  • GitHub manifest-finalization head movement has not been hit live. Two
    recorded live attempts missed the short finalization window and completed
    successfully; unit coverage verifies the three-read stale-head path.
  • Some GitHub and GitLab lifecycle variants remain partial, including positive
    changed-body in-place update and unrelated line movement behavior.
  • GitLab hostile-MR override/forgery variants remain partial, though protected
    credential withholding, forwarding isolation, and symlink containment passed
    against P0.

Upgrade

Pin CI templates to this tag and keep image references digest-pinned. Do not use
mutable image tags as the release identity.

GitHub users should require the gate check on protected branches if blocking
review findings must prevent merge. GitLab users should keep "Pipelines must
succeed" enabled for merge blocking.

Rollback

Rollback means restoring the previous immutable v0.4.0 template/image set, not
pulling a mutable tag:

  • Template/tag commit: v0.4.0 at
    203d22158b806cdb1288ebc55497c7e982777885
  • Base image:
    ghcr.io/seanleecoder/code-tribunal/ai-review-base:1.0-203d22158b806cdb1288ebc55497c7e982777885@sha256:5fb42d0f8a0397602411fca84e1d918850f3c84ea6392493b9a24197fa3fe181
  • Reviewer image:
    ghcr.io/seanleecoder/code-tribunal/ai-review-reviewer:1.0-203d22158b806cdb1288ebc55497c7e982777885@sha256:47d98f6b195408716e137b12a3118a2eee1d7042904f4c606d49f9316e5fb573

After rollback, rerun one representative GitHub or GitLab review flow and verify
the platform's merge gate behavior before treating the rollback as complete.

Verification

Run:

make PYTHON=.venv/bin/python quality
python scripts/check_release_inputs.py

The final release-manifest.json is intentionally reserved for the final
v1.0.0 tag because the manifest tooling validates the final release tag
coordinate.

Assets 2
Loading