Skip to content

@W-21197996 Unregister placeholder tools and update readme#202

Merged
yhsieh1 merged 5 commits intomainfrom
t/commerce/release-prep
Feb 25, 2026
Merged

@W-21197996 Unregister placeholder tools and update readme#202
yhsieh1 merged 5 commits intomainfrom
t/commerce/release-prep

Conversation

@yhsieh1
Copy link
Contributor

@yhsieh1 yhsieh1 commented Feb 24, 2026

Summary

Unregister placeholder tools and update README for preview release

  • Remove placeholder tools (PWA Kit, Storefront Next) so users only see implemented tools at startup
  • Update README: preview release wording, accurate tool tables, credential notes, example prompts
  • Fix package license to Apache-2.0

Testing

  • When start MCP server with all tools, should only see implemented tools
Screenshot 2026-02-24 at 2 10 14 PM

How was this tested?

Dependencies

  • No net-new third-party dependencies were added
  • If net-new third-party dependencies were added, rationale/discussion is included and 3pl-approved is set by a maintainer

  • Tests pass (pnpm test)
  • Code is formatted (pnpm run format)

Copy link
Contributor

@patricksullivansf patricksullivansf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice. Now that #172 is merged you'll probably need to strip the placeholders from the MCP docs too.

"version": "0.4.2",
"author": "Salesforce",
"license": "MIT",
"license": "Apache-2.0",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Two Qs:

  • is it a problem to have multiple licenses in one mono-repo?
  • do we need a LICENSE file similar to packages/b2c-vs-extension/LICENSE

Copy link
Contributor Author

@yhsieh1 yhsieh1 Feb 25, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • I do not see a problem to have multiple licenses on mono-repo. Each package can have its own license and we all use Apache-2.0 in this repo.
  • Since all package has the same license and we have root license.txt there is no need for separated LICENSE file for each package. package.json is enough for npm – The "license" field in package.json is what npm uses. A separate LICENSE file is not required for publishing.

@yhsieh1 yhsieh1 merged commit 917c230 into main Feb 25, 2026
4 checks passed
@yhsieh1 yhsieh1 deleted the t/commerce/release-prep branch February 25, 2026 19:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants