Repository navigation
fix(release): validate without publishing-token authority - #739
Merged
imran-siddique merged 1 commit intoOct 8, 2026
Merged
Conversation
Signed-off-by: Srinivasa Dinakar <dinakarjs@gmail.com>
Contributor
|
🟡 Contributor Check: MEDIUM
Automated check by AgenTrust Contributor Check. |
github-actions
Bot
added
the
needs-review:MEDIUM
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
imran-siddique
approved these changes
Oct 8, 2026
imran-siddique
marked this pull request as ready for review
October 8, 2026 19:46
imran-siddique
requested review from
a team,
carloshvp,
qubeena07,
rajnisht7 and
zohebk8s
as code owners
October 8, 2026 19:46
2 of 7 tasks
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
3 participants
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 release validation job added in #722 and its called CI test job both have id-token: write for Codecov. This repeats the issue identified in the cA2A review: tests can mint release-context OIDC tokens before the publishing job, while source alone cannot establish PyPI environment protections.
Use a credential-free mirror of CI for release validation, including manual build-only rehearsals. Preserve every CI job/step except coverage upload and its OIDC grant; an exact parity regression test prevents drift. Ordinary CI keeps authenticated coverage reporting, with release contexts excluded. Only the publish job retains release OIDC authority. The artifact handoff, explicit manual publication choice, exact version-tag guard and post-publication governance remain in place.
Follow-up to the AgenTrust release audit scope in .github#54 and the requested review change at agentrust-io/ca2a#235 (review). Draft for maintainer review of applying that ruling to cMCP.
Validation on main 9deea16, Linux/Python 3.12: 2,434 passed, 29 skipped, 89.78% coverage across the normal CI directories. The focused permission/parity test and Ruff across src/tests pass. Remote CI (including its Linux/Windows Python matrix), CodeQL, Workflow lint and Confinement reference checks now pass on ae88b37. Actual release artifact execution remains untested on this revision. No publishing workflow was dispatched.