Repository navigation
fix(supply-chain): restore v8 app publisher compatibility - #5215
Conversation
Retain the previous maintained publisher while accepting the reviewed v8 immutable revision across the generic app boundaries. Exercise the actual identity predicates with the new producer and rejection controls; reproduce the starter failure before the change. Refs #5213
Validation and user evaluation at
Hosted exact-head CI and review are still required before promotion. #5213 remains open for protected delivery, deployed acceptance and a fresh starter Validate Scaffold run; these local results do not establish production recovery. |
The tenant RGD now accepts the v8 publisher identity, so its rendered authorization fingerprint, ledger entry and static-scan content and ociRepository cause hashes change. Values are the ones CI rendered at 08a8cb2; the main merge does not touch any RGD input. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Repair at
|
@coderabbitai review |
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📜 Recent review details
📝 Walkthrough
Priority: ➖ Normal Severity of issue fixed: Medium Merge Risk: ⚪ Minimal · up to
|
| Check name | Status | Explanation |
|---|---|---|
| Title check |  |
The title clearly and concisely identifies the supply-chain fix and its purpose: restoring compatibility with the v8 application publisher. |
| Description check | |
The description directly explains why the v8 publisher requires approval and what the change does while preserving the previous publisher during transition. |
| Docstring Coverage | |
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 2… |
| Linked Issues check | |
Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | |
Check skipped because no linked issues were found for this pull request. |
Full details: Docstring Coverage
-
Explanation
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 2 files. (4 skipped: 4 unsupported.)
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Comment @coderabbitai help to get the list of available commands.
@codex review |
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. |
|
Codex Review: Didn't find any major issues. What shall we delve into next? Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
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". |
Readiness at |
…t-5213-a6bc # Conflicts: # scripts/rgd-template-static-scan-baseline.tsv
@coderabbitai review |
✅ Action performedReview finished.
|
Why
The platform tenant starter’s main check fails because its updated publisher is newer than the revisions Platform accepts. New applications need the two sides to agree before their signed releases can be consumed.
What
Approve the reviewed v8 publisher across application verification while retaining the previous release during the transition. Existing applications keep their separate approval records.
Part of #5213