Repository navigation
Validate release identity and packaged SDK examples - #76
Merged
Merged
Conversation
Pitot coding-agent E2EIntelligence Flow is the verification source; Pitot's public README carries the latest
Runtime capabilities
Source commit: |
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.
Change contract
When: A maintainer releases Pitot, or a developer generates an SDK project with the released CLI.
Before: SDK versions were rewritten after the binary build while generated dependencies stayed at 0.1.0. The Rust consumer referenced a nonexistent field, and obsolete test paths skipped its build. Publication could start before all packages built.
After: Release admission requires a clean checkout at a matching stable tag and matching SDK source versions. Generated dependencies pin the CLI release. Python, npm and Rust artifacts are checked before upload; npm/Python publish those checked files. Rust projects use the repository's release tag and all three generated templates are built and exercised.
Boundaries preserved
Evidence
Failure and recovery
One Pi Windows installation attempt hit the existing five-minute timeout before its test ran; one retry at the unchanged commit passed.
Build or identity failures stop before authentication and upload. Cross-registry publication remains non-atomic: inspect any already-published version before retrying a failed upload. Future release tags require an explicit version bump in all SDK manifests and the development fallback.
Remaining limits
Production registry authentication and delivery are not exercised. Windows runtime readiness, obsolete integration cleanup, and the final documentation cleanup remain separate follow-ups.