You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 8ab1f0f
Browse filesBrowse the repository at this point in the historyBrowse files
- The `launch` plugin (`@contentstack/cli-launch`) is no longer bundled with the CLI
196
+
- All `launch:*` commands now require installing the plugin explicitly before use
197
+
- Brings `launch` in line with the opt-in, modular plugin model used elsewhere in 2.x
198
+
199
+
> ⚠️ **This is a change relative to the 2.x beta — not only relative to 1.x.**`@contentstack/cli-launch` was bundled throughout the 1.x releases **and** the entire 2.x beta period, so `launch:*` worked out of the box for beta users too. Starting with 2.x GA it becomes opt-in, so beta users who rely on `launch:*` are also affected when they upgrade.
200
+
201
+
**Before (1.x.x and 2.x.x-beta):**
202
+
-`launch:*` commands were bundled with the CLI and available by default after installation
203
+
204
+
**After (2.x.x GA):**
205
+
-`launch:*` commands are provided by a separate, opt-in plugin that must be installed explicitly
206
+
- Running any `launch:*` command without the plugin installed fails with a `command not found` error where it previously worked out of the box
After installation, launch commands will be available through the CLI:
225
+
```bash
226
+
csdx launch --help
227
+
```
228
+
229
+
**Migration Action:** If you use any `launch:*` command, install the `@contentstack/cli-launch` plugin before (or immediately after) upgrading to 2.x GA to avoid `command not found` errors. This applies to 2.x beta users as well, since `launch` was bundled during the beta.
0 commit comments