Publish Sage app SDK through trusted npm CI - #834
Merged
Merged
Conversation
Publish the flat-named SDK through trusted CI while keeping workspace package imports consistent.
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 3 potential issues.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 46b2b7f. Configure here.
Ensure package type generation can compile its Rust dependencies on clean npm workflow runners.
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.

Summary
sage-app-sdkfor public npm distribution with package metadata, documentation, and complete exportsTest plan
pnpm build:packagespnpm prettier:checkpnpm lintnpm pack --dry-runinpackages/sage-app-sdkNote
Medium Risk
Wide import and package-name churn can break builds or external consumers still on
@sage-app/*scopes; tag-triggered npm publish affects public package availability.Overview
Prepares
sage-app-sdkfor public npm release (Apache-2.0 LICENSE, README, registry metadata,publishConfig.access: public,prepackbuild, and abridge-runtime-coretsup entry) and wires trusted publishing via a new.github/workflows/npm.ymlthat runs prettier, lint, andnpm pack --dry-runon PRs/main andnpm publishfrompackages/sage-app-sdkon any tag (environment: npm, OIDCid-token: write).Renames workspace packages from scoped names to
sage-app-sdk,sage-app-ui, andsage-system-app-sdk, updating root/builtin-apppackage.jsonscripts, pnpm-lock, TS path aliases, CSS theme imports, and docs so the monorepo resolves the new names consistently.Reviewed by Cursor Bugbot for commit c1d7976. Bugbot is set up for automated code reviews on this repo. Configure here.