Skip to content

enh: demote launch to an opt-in plugin (DX-9742)#2655

Open
harshitha-cstk wants to merge 7 commits into
v2-devfrom
enh/dx-9742-demote-launch-plugin
Open

enh: demote launch to an opt-in plugin (DX-9742)#2655
harshitha-cstk wants to merge 7 commits into
v2-devfrom
enh/dx-9742-demote-launch-plugin

Conversation

@harshitha-cstk

Copy link
Copy Markdown
Contributor

Summary

Demotes launch from a bundled CLI command to an opt-in plugin on the 2.x line. Aggregates the work merged into enh/dx-9742-demote-launch-plugin:

  • build: remove @contentstack/cli-launch from the bundled CLI (DX-9742) — dropped from dependencies and oclif.plugins; pnpm-lock.yaml regenerated to clear its subtree. Also removed the launch entry from oclif.topics.
  • docs: README launch opt-in (DX-9744) — removed the inline launch command sections + TOC entries from packages/contentstack/README.md, replaced with an opt-in note (csdx plugins:install @contentstack/cli-launch) and a link to the plugin repo.
  • docs: 2.x migration/upgrade notes (DX-9748) — added a "Launch Plugin Now Opt-In" section + troubleshooting entry to 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 in csdx --help.
  • Users opt in via csdx plugins:install @contentstack/cli-launch (@oclif/plugin-plugins is already bundled).
  • oclif.manifest.json regenerates at pack time, so it picks up the removals automatically.

Verification

  • Manual verification done against the local dev build (npm run setup + node bin/dev.js): launch:* cleanly reports unavailable (no crash); app:deploy --hosting-type hosting-with-launch still works with only @contentstack/apps-cli installed (apps-cli has its own cli-launch dependency).
  • apps-cli deploy.test.ts hosting-with-launch coverage still passes post-demotion.
  • 6 E2E scenarios handed to QA (DX-9749).

Tickets: DX-9742, DX-9744, DX-9748

🤖 Generated with Claude Code

harshitha-cstk and others added 7 commits July 23, 2026 12:02
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)
@harshitha-cstk
harshitha-cstk requested a review from a team as a code owner July 23, 2026 12:17
@github-actions

Copy link
Copy Markdown

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type Count (with fixes) Without fixes Threshold Result
🔴 Critical Severity 0 0 10 ✅ Passed
🟠 High Severity 1 37 25 ✅ Passed
🟡 Medium Severity 0 2 500 ✅ Passed
🔵 Low Severity 0 0 1000 ✅ Passed

⏱️ SLA Breach Summary

✅ No SLA breaches detected. All vulnerabilities are within acceptable time thresholds.

Severity Breaches (with fixes) Breaches (no fixes) SLA Threshold (with/no fixes) Status
🔴 Critical 0 0 15 / 30 days ✅ Passed
🟠 High 0 0 30 / 120 days ✅ Passed
🟡 Medium 0 0 90 / 365 days ✅ Passed
🔵 Low 0 0 180 / 365 days ✅ Passed

ℹ️ 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:

  • Critical without fixes: 0
  • High without fixes: 37
  • Medium without fixes: 2
  • Low without fixes: 0

✅ BUILD PASSED - All security checks passed

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.

1 participant