ci: guard publish artifact verification for partial manifests#847
Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
537c20c to
03203b8
Compare
Summary
Verification
Merge Readiness
Tracking issue: not needed; no baseline exception requested.
Scoped checks run: publish artifact verification failure was reproduced with the downloaded run artifact and targeted script/test checks were run.
Why full baseline is not required: CI fix is limited to publish artifact verification script behavior and its publishWorkflow unit coverage.
Self Review
Self-review workflow: Focused self-review of the CI failure path, manifest-gated smoke behavior, and dependency rebinding behavior.
Self-review result: No unresolved blockers; downloaded failing artifact now verifies successfully with the updated script.
Concept-review workflow: Concept boundary check classified this as technical-support CI verification work with no business-bearing artifact changes.
Concept-review result: No ConceptSpec or ztd-cli runtime-free boundary violation; change only affects publish artifact verification mechanics.
CLI Surface Migration
No-migration rationale: No CLI command, generated user surface, or documented workflow changes.
Upgrade note: No user action required.
Deprecation/removal plan or issue: No deprecation or removal.
Docs/help/examples updated: Not needed; internal CI verification script only.
Release/changeset wording: No changeset needed; publish CI verification fix only.
Scaffold Contract Proof
No-proof rationale: This does not change scaffold generation contracts; it only makes publish artifact verification avoid local-source dependency leakage.
Non-edit assertion: No generated scaffold templates were edited.
Fail-fast input-contract proof: publishWorkflow unit test asserts manifest-gated rawsql-ts smoke and dependency rebinding behavior.
Generated-output viability proof: Downloaded failed publish artifact manifest was re-run through verify-published-package-mode successfully.