Repository navigation
chore: publish as @stackguardian/mcp-wizard - #21
Merged
Merged
Conversation
Rename the npm package from add-sg-mcp to @stackguardian/mcp-wizard and point repository links at StackGuardian/stackguardian-mcp. The add-sg-mcp command, config folder, OAuth client ID and download paths stay, so saved sign-ins and installed skills carry over. CLI hints now print the command the user actually ran: npx @stackguardian/mcp-wizard under Node, add-sg-mcp in the standalone binary. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
1 participant
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
Renames the npm package from
add-sg-mcpto@stackguardian/mcp-wizard(1.2.0). Users now runnpx @stackguardian/mcp-wizard.Changed
package.json: name, version 1.2.0,publishConfig.access: public. Repository, homepage and issues links now point toStackGuardian/stackguardian-mcp, where this code lives (npm provenance checksrepository.url).CLI_COMMANDconstant (src/sg/preset.ts):npx @stackguardian/mcp-wizardunder Node,add-sg-mcpin the standalone binary. Before, they always saidadd-sg-mcp, which isn't onPATHfor npx users.README.md,skills/README.md,docs/RELEASING.md,AGENTS.md,NOTICE,CHANGELOG.md..npmrc: dropsprovenance=true, becauserelease.ymlalready passes--provenance.Kept on purpose, so existing installs keep working:
add-sg-mcpbin.npx @stackguardian/mcp-wizardruns it, because it's the package's only bin.~/.config/add-sg-mcp/(credentials and the skills manifest). Renaming it would lose sign-ins and make the next run fail with "was not installed by add-sg-mcp"./.well-known/oauth-clients/add-sg-mcp.json, which the dashboard hosts.dl.stackguardian.io/add-sg-mcp/downloads, the install scripts, theADD_SG_MCP_*variables and the release IAM role.Before releasing
npmjs.com/package/@stackguardian/mcp-wizard/accessforStackGuardian/stackguardian-mcp+release.yml.npm deprecate add-sg-mcp "Moved to @stackguardian/mcp-wizard".Test plan
bun run build,bun run typecheck,bun run test(22/22 files)npm pack --dry-runproducesstackguardian-mcp-wizard-1.2.0.tgznode dist/index.js statusprintsRun npx @stackguardian/mcp-wizard login.add-sg-mcp …hints (covered bybinaries.ymlon release)🤖 Generated with Claude Code