Repository navigation
fix(release): fail closed on skipped publication - #26
Conversation
|
Important Review skippedNo new commits to review since the last review. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
📝 WalkthroughWalkthroughThe release workflow now requires successful resolution and packaging before release execution. An always-running ChangesRelease convergence
Estimated code review effort: 3 (Moderate) | ~20 minutes Sequence Diagram(s)sequenceDiagram
participant Resolve
participant Package
participant Release
participant Converge
Resolve->>Release: successful result
Package->>Release: successful result
Release->>Converge: terminal job result
Resolve->>Converge: terminal job result
Package->>Converge: terminal job result
Converge->>Converge: validate operation result matrix
Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
|
@codex review |
|
@coderabbitai review |
|
|
Codex Review: Didn't find any major issues. Chef's kiss. 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". |
|
@codex-gate approve 04e7c70 5229865157 |
|
To use Codex here, create an environment for this repo. |
Summary
This completes the historical-release repair path started in #24 and #25. The exact-main repair run proved the package successfully, but GitHub Actions still skipped publication because an intentionally skipped compatibility job propagated through the dependency chain; the workflow then reported a false green.
Publication now evaluates after skipped ancestors and still requires successful package proof. A single terminal convergence job checks the exact maintenance, publish, or repair result shape, so a skipped, failed, or cancelled requested operation makes the workflow fail with every job result in the diagnostic.
The repository validator now bounds the publish job before the terminal job. The regression table also evaluates the real workflow script with exact GitHub result bindings and no inherited environment.
Validation
bun test: 530 passed, 3 named manual/hosted qualification checks skipped, 0 failed.actionlint .github/workflows/release.yml: passed.bun run release:validate -- --json: passed.Post-Deploy Monitoring & Validation
repairforv0.1.1withreplace_mismatched_assets=falseon the merged main commit.autorelease: tagged, noautorelease: pending, and the existingv0.1.1assets remain unchanged.maintenance; healthy maintenance has only the maintenance job and convergence succeed.Summary by CodeRabbit
Bug Fixes
Tests