enh: demote launch to an opt-in plugin (DX-9742)#2655
Merged
Conversation
Remove the inline launch command sections and TOC entries from the bundled CLI README and replace them with a note explaining that launch is provided by the opt-in @contentstack/cli-launch plugin (not bundled), including the install command and a link to the plugin's GitHub README. Scoped narrowly to the launch block per the DX-9744 decision; other opt-in-plugin docs are deferred. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
docs: mark launch as opt-in plugin in root README (DX-9744)
Demote launch to an opt-in plugin: drop @contentstack/cli-launch from both the dependencies and the oclif.plugins array in packages/contentstack/package.json, and regenerate pnpm-lock.yaml to clear its dependency subtree. Launch commands are no longer bundled or documented by default; users install them on demand via `csdx plugins:add @contentstack/cli-launch` (@oclif/plugin-plugins is already bundled). oclif.manifest.json is generated at pack time, so it picks up the removal automatically. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…-dependency build: remove @contentstack/cli-launch from bundled CLI (DX-9742)
…748) Add a migration section and troubleshooting entry to MIGRATION.md covering that launch:* commands are no longer bundled in 2.x GA and require installing @contentstack/cli-launch explicitly. Calls out that this is a change relative to the 2.x beta too (launch was bundled throughout 1.x and the beta), so running launch:* without the plugin now fails with "command not found". Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…on-doc docs: document launch opt-in requirement in 2.x migration guide (DX-9748)
🔒 Security Scan Results
⏱️ SLA Breach Summary
ℹ️ Vulnerabilities Without Available Fixes (Informational Only)The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:
✅ BUILD PASSED - All security checks passed |
Add an init hook that intercepts commands belonging to demoted (now opt-in) plugins when the plugin is not installed. For launch:* it prints a warning and the install command (csdx plugins:install @contentstack/cli-launch) instead of a generic "command not found", then exits. If the plugin is installed, the hook is a no-op and commands run normally. Driven by a DEMOTED_PLUGINS map for easy extension. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
feat: warn and suggest install for opt-in launch commands
🔒 Security Scan Results
⏱️ SLA Breach Summary
ℹ️ Vulnerabilities Without Available Fixes (Informational Only)The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:
✅ BUILD PASSED - All security checks passed |
🔒 Security Scan Results
⏱️ SLA Breach Summary
ℹ️ Vulnerabilities Without Available Fixes (Informational Only)The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:
✅ BUILD PASSED - All security checks passed |
🔒 Security Scan Results
⏱️ SLA Breach Summary
ℹ️ Vulnerabilities Without Available Fixes (Informational Only)The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:
✅ BUILD PASSED - All security checks passed |
cs-raj
approved these changes
Jul 24, 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
2 participants
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
Demotes
launchfrom a bundled CLI command to an opt-in plugin on the 2.x line. Aggregates the work merged intoenh/dx-9742-demote-launch-plugin:@contentstack/cli-launchfrom the bundled CLI (DX-9742) — dropped fromdependenciesandoclif.plugins;pnpm-lock.yamlregenerated to clear its subtree. Also removed thelaunchentry fromoclif.topics.launchcommand sections + TOC entries frompackages/contentstack/README.md, replaced with an opt-in note (csdx plugins:install @contentstack/cli-launch) and a link to the plugin repo.MIGRATION.md, calling out that this is a change relative to the 2.x beta too (launch was bundled through 1.x and the beta).Behavior after this change
launch:*commands are no longer bundled or shown incsdx --help.csdx plugins:install @contentstack/cli-launch(@oclif/plugin-pluginsis already bundled).oclif.manifest.jsonregenerates at pack time, so it picks up the removals automatically.Verification
npm run setup+node bin/dev.js):launch:*cleanly reports unavailable (no crash);app:deploy --hosting-type hosting-with-launchstill works with only@contentstack/apps-cliinstalled (apps-cli has its owncli-launchdependency).deploy.test.tshosting-with-launch coverage still passes post-demotion.Tickets: DX-9742, DX-9744, DX-9748
🤖 Generated with Claude Code