Skip to content

Prepare 1.7.9 managed Jev client release - #242

Open
Coding-Dev-Tools wants to merge 2 commits into
codex/dashboard-cache-readiness-20260928from
codex/prepare-release-1.7.9
Open

Coding-Dev-Tools wants to merge 2 commits into
codex/dashboard-cache-readiness-20260928from
codex/prepare-release-1.7.9

Conversation

@Coding-Dev-Tools

@Coding-Dev-Tools Coding-Dev-Tools commented Sep 29, 2026 •

Copy link
Copy Markdown
Owner

The published 1.7.8 client lacks the managed Jev transport and MCP decision tool, so a normal customer upgrade cannot use the reviewed Pro/Team integration. This prepares client 1.7.9 on top of #241, synchronizes package/plugin/commercial metadata, and documents the customer upgrade and exact-artifact publication requirements. Campaign capabilities, preparation metadata and metrics derive their version from the loaded Engraphis package.

Fresh immutable v117 offline evidence binds all 583 evaluated inputs. Fixture results match v116; historical artifacts remain unchanged. Generated charts and current evidence references identify the new bytes.

Validation:

  • All 29 automatic GitHub checks passed on latest commit 5954b5f; no unresolved review threads remain.
  • Latest commit 5954b5f: 482 campaign, packaging, evidence and documentation tests passed; one explicit skip because the pinned Docker image is not available locally. The new regression reproduced the stale version before the fix and covers capabilities, preparation metadata and metrics.
  • The release preparation base 7977dc2 passed 1,136 focused packaging, release, evidence, Jev, session and MCP tests, with 44 explicit skips (43 Linux-only release-execution cases and one optional CycloneDX tool). The subsequent change preserves the managed runtime implementation.
  • Ruff, commercial-manifest and whitespace checks passed. All 1,653 tracked inputs match the latest committed and tested source.
  • Two clean copies of 5954b5f built with the pinned release toolchain produced identical wheels and normalized source archives; distribution-content verification passed.
  • Both installed artifacts expose the managed transport and direct/Classic/Smart decision routes. Offline refusal, memory roundtrip and all three campaign version surfaces passed with zero provider calls.

This is release preparation. Exact final-source distribution/full-product qualification, owner-controlled signing/review and Cloud activation remain publication and availability gates. Existing version-specific waivers are unchanged.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 29, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-09-29T11:13:26.254313Z 5954b5f New commits
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7977dc2bea

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread pyproject.toml
Coding-Dev-Tools pushed a commit that referenced this pull request Sep 29, 2026
Both branches added offline-fixtures-v116 and v117 with different bytes
and repointed the same evidence references, so whichever merged second
would conflict. Stack these follow-ups on #242 instead: keep its v116
and v117 artifacts, keep this branch's references until the next commit
binds the merged tree, and list the follow-ups as unreleased above the
1.7.9 changelog section.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RQQDvWHB6hcGwyB8HU3bWy
Coding-Dev-Tools pushed a commit that referenced this pull request Sep 29, 2026
Rerun the public offline fixtures on the merged tree, which adds #242's
1.7.9 version surfaces and campaign adapter change, the incorporated
Anthropic client fix and the latest guard and completion fixes.
Aggregates remain identical to v115 and to #242's v117; refresh the
registry references, charts and changelog reference.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RQQDvWHB6hcGwyB8HU3bWy

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant