DX | 27-07-2026 | Release | CLI Beta - #2659
Conversation
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…mock The module-level cli-progress mock binds by load order and does not take effect in CI, so the reconciliation tests saw the real bar and failed. Inject a stub bar at the rendering seam instead, and drop the ticket number from the describe title. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
back merge
Adds a thin wrapper around readContentTypeSchemas specifically for global
fields, enabling callers to read per-file {uid}.json exports from the
global_fields directory with a semantically accurate function name.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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>
…e list Prevents silent data corruption when a CLI v1 export archive containing global_fields/globalfields.json is passed to readGlobalFieldSchemas — the bulk array file is now skipped instead of being parsed as a single schema element. readContentTypeSchemas is unaffected. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…-dependency build: remove @contentstack/cli-launch from bundled CLI (DX-9742)
…dContentTypeSchemas unchanged Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…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)
Cherry-picked from feat/org-plan-key-check-v1 (commit b5011fc), merged onto the v2 (2.0.0-beta) line. Preserves csAssetsUrl/cs-assets support already present here (endpoints.assetManagement is derived from it) while adding the shared region-endpoints/region-refresh self-heal, and retiring the standalone authUrl field in favor of endpoints.auth. (cherry picked from commit b5011fc)
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(utilities): add readGlobalFieldSchemas utility function
feat: warn and suggest install for opt-in launch commands
…ete-count DX-7521 | Fix invalid complete count in import progress UI
…plugin enh: demote launch to an opt-in plugin (DX-9742)
🔒 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 |
fix: version bump
🔒 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 |
corrected version bump
🔒 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 |
No description provided.