Skip to content

chore: GA version bumps — promote all packages from beta to 2.0.0 and update third-party deps - #2688

Open
cs-raj wants to merge 3 commits into
v2-devfrom
chore/ga-version-bumps
Open

chore: GA version bumps — promote all packages from beta to 2.0.0 and update third-party deps#2688
cs-raj wants to merge 3 commits into
v2-devfrom
chore/ga-version-bumps

Conversation

@cs-raj

@cs-raj cs-raj commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Overview

This PR prepares all packages in the `cli` monorepo for the General Availability (GA) release of CLI v2. It does two things:

  1. Promotes every `@contentstack/*` package version from `-beta.X` to its stable GA version (all cross-repo internal dependency references updated to match).
  2. Bumps third-party devDependencies to their latest minor/patch versions (no major version jumps; strictly minor and patch).

Package Version Promotions (self-versions)

Package Old Version New Version
`@contentstack/cli` `2.0.0-beta.30` `2.0.0`
`@contentstack/cli-auth` `2.0.0-beta.17` `2.0.0`
`@contentstack/cli-command` `2.0.0-beta.11` `2.0.0`
`@contentstack/cli-config` `2.0.0-beta.15` `2.0.0`
`@contentstack/cli-utilities` `2.0.0-beta.12` `2.0.0`

Internal `@contentstack/*` Dependency Updates

All internal dependencies in `packages/contentstack/package.json` are updated from their individual beta pins to stable `2.0.0` / `1.0.0`:

Dependency Old New
`@contentstack/cli-audit` `~2.0.0-beta.16` `~2.0.0`
`@contentstack/cli-cm-export` `~2.0.0-beta.25` `~2.0.0`
`@contentstack/cli-cm-import` `~2.0.0-beta.25` `~2.0.0`
`@contentstack/cli-auth` `~2.0.0-beta.17` `~2.0.0`
`@contentstack/cli-bulk-operations` `^2.0.0-beta.5` `^2.0.0`
`@contentstack/cli-cm-bootstrap` `~2.0.0-beta.25` `~2.0.0`
`@contentstack/cli-cm-branches` `~2.0.0-beta.11` `~2.0.0`
`@contentstack/cli-cm-clone` `~2.0.0-beta.26` `~2.0.0`
`@contentstack/cli-cm-export-to-csv` `~2.0.0-beta.12` `~2.0.0`
`@contentstack/cli-cm-import-setup` `~2.0.0-beta.19` `~2.0.0`
`@contentstack/cli-cm-seed` `~2.0.0-beta.25` `~2.0.0`
`@contentstack/cli-command` `~2.0.0-beta.11` `~2.0.0`
`@contentstack/cli-config` `~2.0.0-beta.15` `~2.0.0`
`@contentstack/cli-migration` `~2.0.0-beta.17` `~2.0.0`
`@contentstack/cli-utilities` `~2.0.0-beta.12` `~2.0.0`
`@contentstack/cli-variants` `~2.0.0-beta.20` `~2.0.0`

Cross-package internal refs in `cli-auth` and `cli-config` are updated similarly (e.g. `cli-command`, `cli-utilities` from `~2.0.0-beta.11/12` → `~2.0.0`).


Third-Party Dependency Bumps (minor/patch only)

`@oclif/*` ecosystem

Package Old New Scope
`@oclif/core` `^4.11.4` `^4.11.14` deps / devDeps
`@oclif/test` `^4.1.18` `^4.1.20` devDeps
`oclif` (CLI tool) `^4.23.0` – `^4.23.8` `^4.23.27` devDeps

ESLint ecosystem

Package Old New Affected packages
`eslint` `^10.5.0` `^10.6.0` all packages
`eslint-config-oclif` `^6.0.15` – `^6.0.166` `^6.0.175` all packages (unified)

Runtime dependencies (`cli-utilities`)

Package Old New
`papaparse` `^5.5.3` `^5.5.4`
`uuid` `^14.0.0` `^14.0.1`

Type definitions

Package Old New Affected packages
`@types/inquirer` `^9.0.9` `^9.0.10` `cli-utilities`
`@types/sinon` `^21.0.0` `^21.0.1` `cli-utilities`, `contentstack` (main)

README Updates

  • `packages/contentstack/README.md` — major structural cleanup: removed stale generated content (1100+ lines), leaving a lean, accurate reference. This was part of the `chore/readme-cleanup-v2` merge that landed on this branch.
  • `cli-auth`, `cli-config` — auto-regenerated by `oclif readme`: version strings updated from `2.0.0-beta.X` → `2.0.0`, Node version updated to `v22.21.1`.

What Was NOT Changed

  • No major version bumps — all third-party bumps are strictly minor or patch.
  • `@contentstack/management` and `@contentstack/utils` (1.x) — left untouched as per team convention.
  • `sinon` — stays at current version; jump to `^21.x` in some packages is a major version change.
  • `recheck` / `recheck-linux-x64` — pinned for GLIBC 2.31 compatibility on Linux x64 CI; not touched.
  • `@typescript-eslint/*` — alpha targets only; skipped.

Test Plan

  • `pnpm install` succeeds with new lockfile
  • `pnpm build` succeeds across all packages
  • `pnpm test` passes across all packages
  • `csdx --version` reports `2.0.0` (no beta suffix)

🤖 Generated with Claude Code

…minor

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@cs-raj
cs-raj requested a review from a team as a code owner August 5, 2026 12:05
@snyk-io

snyk-io Bot commented Aug 5, 2026

Copy link
Copy Markdown

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues
Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@github-actions

github-actions Bot commented Aug 5, 2026

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 0 0 25 ✅ Passed
🟡 Medium Severity 0 0 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

✅ BUILD PASSED - All security checks passed

@github-actions

github-actions Bot commented Aug 5, 2026

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 0 0 25 ✅ Passed
🟡 Medium Severity 0 0 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

✅ BUILD PASSED - All security checks passed

GitHub Actions workflow pins pnpm@10.28.0 via action-setup; bumping
packageManager to 10.34.4 caused ERR_PNPM_BAD_PM_VERSION in CI.
Keep packageManager aligned with the workflow config.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Aug 5, 2026

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 0 0 25 ✅ Passed
🟡 Medium Severity 0 0 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

✅ BUILD PASSED - All security checks passed

@aniket-shikhare-cstk aniket-shikhare-cstk left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed against v2-dev — clean, well-scoped version bump. LGTM pending the lockfile.

Verified

  • 5 core packages promoted beta → 2.0.0 (cli-auth, cli-command, cli-config, cli-utilities, @contentstack/cli).
  • All internal @contentstack/cli-* ranges moved to ~2.0.0 consistently — no broken ranges, and the cross-repo deps on the plugin packages line up with cli-plugins#338.
  • Third-party bumps are minor/patch only (@oclif/core 4.11.4→4.11.14, eslint 10.5→10.6, oclif, papaparse, uuid) — no majors.
  • README --version strings updated to 2.0.0 / node-v22.

Before merge

  • Regenerate pnpm-lock.yaml. It wasn't touched here, so it still carries 2.0.0-beta.* specifiers that no longer match the bumped package.json. CI uses --no-frozen-lockfile so it won't fail, but we shouldn't tag GA on a stale lock. pnpm install + commit.

Release ordering: @contentstack/cli@2.0.0 depends on the plugin packages at ~2.0.0, so cli-plugins#338 must publish at 2.0.0 before/with this one.

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.

2 participants