fix(pitot): make the npm and python SDK packages publishable - #247
Merged
Conversation
The v0.1.0 release run failed at the npm binding publish: the TypeScript SDK had never been built as a package and lacked node type definitions for its runner (readline/process). Add @types/node + tsconfig types pin; verify both binding builds in isolation (tsc -> dist/, python -m build -> sdist+wheel). SDK manifests also correct license metadata MIT -> Apache-2.0 to match the repository license. Disclosure-Reviewed: reviewed — public-safe only, private facet kept out of this commit
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.
The v0.1.0 release proved the binary channel (binaries + checksums live on AR, /pitot/latest serves 0.1.0) but failed at the npm binding step: the TS SDK package had never been built as a package — no @types/node for its runner's readline/process usage. Fixes: @types/node devDependency +
types: ["node"]in tsconfig; SDK license metadata MIT → Apache-2.0 (matching the repo). Both binding builds verified in isolation: tsc emits dist/,python -m buildemits the operatorstack-pitot sdist+wheel. After merge+sync: tag v0.1.1 to publish binaries+bindings in lockstep.