Repository navigation
feat: add Claude Code marketplace @slack that installs each release - #205
Conversation
mwbrooks
added
enhancement
🦋 Changeset detectedLatest commit: 76c7b38 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
| write_version(CLAUDE_PLUGIN_PATH, version) | ||
| write_version(CURSOR_PLUGIN_PATH, version) | ||
| write_version(CODEX_PLUGIN_PATH, version) | ||
| write_marketplace_ref(CLAUDE_MARKETPLACE_PATH, version) |
There was a problem hiding this comment.
note: write_version sets a top-level version, but the marketplace pins a release with the nested source.ref, which takes the tag (v1.7.0). Pinning to the tag means new installs get the latest release, never unreleased commits on main.
| /plugin install slack@claude-plugins-official | ||
| ``` | ||
|
|
||
| To get each release as soon as it ships, install from the plugin's own marketplace in its [GitHub repository](https://github.com/slackapi/slack-skills-plugin) instead: |
There was a problem hiding this comment.
question: @lukegalbraithrussell Should this second Claude Code install path sit in a collapsed <details> section? It would keep the official one-line install as the obvious path, and the node-slack-sdk pages already use <details> on docs.slack.dev (e.g. "Initializing without a token" in docs/english/web-api.md). The tradeoff is that skimmers are less likely to spot it. Happy to go either way!
There was a problem hiding this comment.
I say keep it outside a <details>!
There was a problem hiding this comment.
Sounds good, keeping it expanded. Thanks @lukegalbraithrussell!
Co-authored-by: Luke Russell <31357343+lukegalbraithrussell@users.noreply.github.com>
lukegalbraithrussell
left a comment
lukegalbraithrussell
left a comment
There was a problem hiding this comment.
docs are good-to-go
zimeg
added
the
area:claude
|
Thanks @zimeg for the review and @lukegalbraithrussell for the docs suggestion! 🙇 |
Summary
This pull request gives Claude Code developers an install path that tracks our releases, so they can get each new version as soon as it ships. Today the only path is the official directory listing, which picks up a new version on its own schedule.
The
slackmarketplace in.claude-plugin/marketplace.jsoninstalls the plugin from the latest release tag, not frommain, so nobody installs unreleased commits. The release PR moves the tag throughscripts/sync_versions.py, beside the manifest versions it already syncs. The docs page adds this path under the Claude Code install, with the Enable auto-update step and a note to install from one marketplace only.Testing
claude plugin validate ./passes on Claude Code 2.1.309, with only the existingiconandprivacyPolicyUrldirectory warnings.CLAUDE_CONFIG_DIR,claude plugin marketplace add slackapi/slack-skills-plugin#mwbrooks-claude-marketplacethenclaude plugin install slack@slackinstalled 1.6.0 at9f61e54, thev1.6.0tag, with all 14 skills and the MCP server.scripts/sync_versions.pyon a copy withpackage.jsonat 1.7.0 set the entry'sreftov1.7.0, and leaves it unchanged at 1.6.0.make test-unit(28 passed) andmake lintpass.Notes
slack, which matches the Codex install (slack@slack).Requirements
make testand the tests pass. (Unit tests pass. The eval tests needGEMINI_API_KEYandSLACK_MCP_TOKEN, which weren't set.)