Skip to content

CodexBot v0.1.0-beta.2 — GitHub-qualified App approvals

Pre-release
Pre-release

Choose a tag to compare

@AppSolves AppSolves released this 15 Nov 13:18
Immutable release. Only release title and notes can be modified.
c56e94a

Fix GitHub App review qualification without weakening repository protections.

  • GitHub Required approvals stays at 1 or your stronger configured count. CodexBot no longer turns that count, CODEOWNER or last-push rules into an extra human minimum. It requires GitHub's actual APPROVED decision when approvals are required and still uses the native exact-head merge with all required CI/protection checks.
  • minimum_human_approvals: 0 means no additional CodexBot-required humans. Explicit Human-in-the-Loop minimums still require distinct, current-head, write-capable non-author humans.
  • Manual-only reviews and explicit-only --merge behavior remain unchanged. Unknown/unmet approval evidence, incomplete AI analysis, findings, stale heads and failed checks never authorize a merge.
  • Add “Copyright © 2026 Kaan Gönüldinc” to the shared website footer.

Implementation PR #36 merged as 17608a5. Pin PR #37 merged as c56e94a. All active Worker/backend/caller pins use the actual source revision 17608a5. Disabled callers were not reactivated.

Validation: 199 tests, typecheck, lint and build passed. Full source and pin CI passed, including clean checkout, Workers/D1, synthetic browser, pinned Docker/Codex sandbox, Actionlint and security checks. The production Worker version, deployment, canonical health endpoint and rendered footer were verified. No dependency, credential, repository-protection or D1 schema changes.

Production version: 27391a59-c875-4306-8828-997847169c5d. Deployment: 4f350016-e70a-46c8-832b-71d83362acd6. CLI ChatGPT and merge deployment authorization remain enabled; browser OAuth and hosted website inference remain disabled.

Acceptance limitation: the operator explicitly waived new disposable live GitHub/inference tests for this patch; none were performed. App qualification under a particular review/last-push configuration is not claimed as newly live-proven. GitHub remains authoritative and may require another qualifying reviewer, especially when the App itself made the latest reviewable push. No fallback or protection bypass was introduced.