Add trusted npm publishing for the DocPull SDK#119
Merged
Conversation
admin-raintree
approved these changes
Jul 23, 2026
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.
What changed
@raintree-technology/docpull-sdkWhy
The SDK is public, but future releases had no repository workflow. This keeps npm credentials out of GitHub and makes the Python and TypeScript packages release from the same version tag.
Checks
bun install --frozen-lockfilebun run --cwd sdk/js test(14 passed)bun run --cwd sdk/js typecheckbun run --cwd sdk/js buildnpm pack --dry-rungit diff --check