Prepare 1.7.9 managed Jev client release - #242
Open
Coding-Dev-Tools wants to merge 2 commits into
Open
Coding-Dev-Tools wants to merge 2 commits into
Coding-Dev-Tools wants to merge 2 commits into
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 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".
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
Open
10 of 12 tasks
This branch has not been deployed
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.
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:
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.