Repository navigation
release: 0.85.0 — CI integrity - #266
Merged
Merged
Conversation
Bumps 0.84.1 -> 0.85.0 and syncs all 5 distribution manifests.
WHAT THIS RELEASE IS
CR-CI-001 and the release-gate work. The headline is that CI's green signal
now means something: the suppression ceiling drops 37 -> 5 with a ratcheting
guard, and roughly 206 previously hidden tests execute.
- ceiling 37 -> 5, MAX ratchets DOWN and any PR raising the count fails CI
- the release gate fails CLOSED: a provider timeout or internal error
returned WARN at confidence 0.0, so a gate that could not evaluate let the
release through. Both now BLOCK.
- release-gate failures are diagnosable: handlers logged only
type(exc).__name__, so every failure read as a bare class name with no
message and no traceback.
- hypothesis declared in dev extras; CliRunner.isolated_filesystem replaced
with pytest tmp_path (removed in newer click, and typer is unpinned).
NO NEW DAG-2026 DISCLOSURE
The Decision Assurance Gate foundation shipped in 0.84.1. This release adds
nothing to it. Verified in the built wheel: RESEARCH.md absent, reason-code
registry seed still empty, zero "0.85.0" strings in reason_codes.py, and none
of the withheld identifiers present.
CHANGELOG
The 0.84.1 entry was still headed "Unreleased" and disclosed 37 suppression
flags. Both are now stale, so it is marked shipped with its date and the 0.85.0
entry states that the 37 figure is superseded.
VERIFICATION
manifests all 5 at 0.85.0 (--check)
ceiling guard count=5 MAX=5 PASS
trade-secret gate PASS (real wheel)
monetisation gate PASS
TS scan on diff 0 hits
built wheel 0.85.0 - mcp-name marker present - RESEARCH.md absent -
0 seed entries - 0 id leaks - Verdict.BLOCK fallback
shipped - logger.exception x2, type(exc).__name__ x0
Public CI green on ace49ac before tagging. Deploy Lambda is red there and has
been on every master commit since 2026-07-27 (invalid AWS credentials); it
deploys cognigraph-api and never touches the PyPI artifact.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
🛡️ GraQle PR Guardian💥 Blast Radius: 8 modules affected
Total blast radius: 8 🏛️ Governance Verdict
|
| Metric | Value |
|---|---|
| Blast Radius | 8 |
| Files Analyzed | 8 |
| Blocked | 0 |
| SHACL Violations | 0 |
| Verdict | WARN |
🔬 Powered by GraQle PR Guardian v0.1.0 · Scan completed 2026-09-27T07:48:07.739432+00:00
harishquantamix
approved these changes
Sep 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release 0.85.0 — CI integrity
Bumps 0.84.1 → 0.85.0 and syncs all 5 distribution manifests.
What this release is
CR-CI-001 and the release-gate work. The headline: CI's green signal now means something.
MAXonly moves down; any PR raising the count fails CI)WARNat confidence 0.0, so a gate that could not evaluate let the release through. Both nowBLOCK.type(exc).__name__, so every failure read as a bare class name with no message and no tracebackAlso fixed:
hypothesisundeclared in dev extras, andCliRunner.isolated_filesystem(removed in newer click, whiletyper[all]>=0.9is unpinned — CI resolved a version without it while local installs still had it).No new DAG-2026 disclosure
The Decision Assurance Gate foundation shipped in 0.84.1. This release adds nothing to it.
Verified in the built wheel, not the source tree:
GRAQLE_DAG_ENABLEDremainsfalseby default.CHANGELOG correction
The 0.84.1 entry was still headed "Unreleased" and disclosed 37 suppression flags. Both are now stale — it's marked shipped with its date, and the 0.85.0 entry states plainly that the 37 figure is superseded rather than leaving two conflicting numbers in the file.
Verification
--check)count=5 MAX=5PASStrade-secret-wheel-gatemcp-namemarker present ·Verdict.BLOCKfallback shipped ·logger.exception×2,type(exc).__name__×0Public CI was green on
ace49acfbefore this branch was cut.Deploy Lambdais red there and has been on every master commit since 2026-07-27 (invalid AWS credentials). It deployscognigraph-apiand never touches the PyPI artifact — pre-existing, not a release blocker, but real breakage worth its own fix.After merge
Tag
v0.85.0→ PyPI publish → MCP Registry. The registry publish succeeded on 0.84.1 after theREADME_PYPI.mdmarker fix, and the marker is confirmed present in this wheel's METADATA.🤖 Generated with Claude Code