Skip to content

fix: update v1 release pipeline trigger branch to v1-legacy - #2698

Merged
cs-raj merged 6 commits into
v1-legacyfrom
fix/DX-10156-v1-legacy-release-trigger
Aug 12, 2026
Merged

fix: update v1 release pipeline trigger branch to v1-legacy#2698
cs-raj merged 6 commits into
v1-legacyfrom
fix/DX-10156-v1-legacy-release-trigger

Conversation

@cs-raj

@cs-rajcs-raj commented Aug 12, 2026•
edited
Loading

Copy link
Copy Markdown
Contributor

Summary

Post-release stabilization changes for the CLI v1-legacy branch ahead of CLI v2 GA. This PR ensures v1 continues to release and publish correctly once v2 takes over `main` and the `latest` npm dist-tag.

Changes

Release pipeline trigger

  • Updated `release-production-pipeline.yml` trigger branch from `main` → `v1-legacy`
  • Workflows on the `v1-legacy` branch previously fired on `push to main`. Once v2 is promoted to `main`, v1 hotfix pushes to `v1-legacy` would silently trigger nothing — this fixes that

npm dist-tag

  • Updated `release-production-core.yml` and `release-production-platform-plugins.yml` publish tag from `latest` → `v1`
  • Once v2 owns `latest`, v1 must publish under its own tag to avoid overwriting v2 as the default install
  • Users can continue installing v1 with: `npm install -g @contentstack/cli@v1`

Dependency bumps

  • `@contentstack/cli` version: `1.67.0` → `1.68.0`
  • `@contentstack/cli-launch` dependency: `^1.11.1` → `^1.11.2`
  • `picomatch` override: `^4.0.4` → `^4.0.5`

README docs URLs

  • Appended `/v1` to all Contentstack docs URLs (21 links)
  • Ensures users on v1 are directed to versioned v1 documentation after v2 docs go live

Test plan

  • Verify `release-production-pipeline.yml` triggers on `v1-legacy` not `main`
  • Verify all publish steps in core and platform-plugins workflows use `tag: v1`
  • Confirm `workflow_dispatch` is present for manual v1 releases
  • After v2 GA, validate `npm install -g @contentstack/cli@v1` installs the correct v1 version
  • Spot-check 2–3 README docs links resolve correctly with `/v1` appended

Related

🤖 Generated with Claude Code

@cs-raj@claude
fix: update release pipeline trigger branch from main to v1-legacy
3dcd055
After CLI v2 takes over main, v1 hotfix releases must be triggered from
the v1-legacy branch. This change ensures the production release pipeline
fires on push to v1-legacy rather than main.
Closes DX-10156
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@cs-raj
cs-raj requested a review from a team as a code ownerAugust 12, 2026 09:30
@snyk-io

snyk-ioBot commented Aug 12, 2026•
edited
Loading

Copy link
Copy Markdown

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

StatusScan Engine Critical High Medium LowTotal (0)
✅Open Source Security0000 0 issues
✅Licenses0000 0 issues
✅Code Security0000 0 issues

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

@github-actions

github-actionsBot commented Aug 12, 2026

Copy link
Copy Markdown

🔒 Security Scan Results

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

Check TypeCount (with fixes)Without fixesThresholdResult
🔴 Critical Severity0010✅ Passed
🟠 High Severity0025✅ Passed
🟡 Medium Severity02500✅ Passed
🔵 Low Severity001000✅ Passed

⏱️ SLA Breach Summary

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

SeverityBreaches (with fixes)Breaches (no fixes)SLA Threshold (with/no fixes)Status
🔴 Critical0015 / 30 days✅ Passed
🟠 High0030 / 120 days✅ Passed
🟡 Medium0090 / 365 days✅ Passed
🔵 Low00180 / 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: 0
  • Medium without fixes: 2
  • Low without fixes: 0

✅ BUILD PASSED - All security checks passed

@cs-raj@claude
chore: bump cli-launch to 1.11.2 and version to 1.68.0; add /v1 to do…
e9abb25
…cs URLs
- Bump @contentstack/cli from 1.67.0 to 1.68.0
- Bump @contentstack/cli-launch dependency from ^1.11.1 to ^1.11.2
- Bump picomatch override to ^4.0.5
- Append /v1 to all Contentstack docs URLs in README so links point to
the versioned v1 docs after CLI v2 is live
Closes DX-10156
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions

github-actionsBot commented Aug 12, 2026

Copy link
Copy Markdown

🔒 Security Scan Results

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

Check TypeCount (with fixes)Without fixesThresholdResult
🔴 Critical Severity0010✅ Passed
🟠 High Severity0025✅ Passed
🟡 Medium Severity02500✅ Passed
🔵 Low Severity001000✅ Passed

⏱️ SLA Breach Summary

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

SeverityBreaches (with fixes)Breaches (no fixes)SLA Threshold (with/no fixes)Status
🔴 Critical0015 / 30 days✅ Passed
🟠 High0030 / 120 days✅ Passed
🟡 Medium0090 / 365 days✅ Passed
🔵 Low00180 / 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: 0
  • Medium without fixes: 2
  • Low without fixes: 0

✅ BUILD PASSED - All security checks passed

@github-actions

github-actionsBot commented Aug 12, 2026

Copy link
Copy Markdown

🔒 Security Scan Results

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

Check TypeCount (with fixes)Without fixesThresholdResult
🔴 Critical Severity0010✅ Passed
🟠 High Severity0025✅ Passed
🟡 Medium Severity02500✅ Passed
🔵 Low Severity001000✅ Passed

⏱️ SLA Breach Summary

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

SeverityBreaches (with fixes)Breaches (no fixes)SLA Threshold (with/no fixes)Status
🔴 Critical0015 / 30 days✅ Passed
🟠 High0030 / 120 days✅ Passed
🟡 Medium0090 / 365 days✅ Passed
🔵 Low00180 / 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: 0
  • Medium without fixes: 2
  • Low without fixes: 0

✅ BUILD PASSED - All security checks passed

@cs-raj@claude
fix: use v1 npm dist-tag for v1-legacy production releases
e753b04
Once CLI v2 takes over latest, v1 releases must publish under the v1
dist-tag so they don't overwrite v2 as the default install.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions

github-actionsBot commented Aug 12, 2026

Copy link
Copy Markdown

🔒 Security Scan Results

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

Check TypeCount (with fixes)Without fixesThresholdResult
🔴 Critical Severity0010✅ Passed
🟠 High Severity0025✅ Passed
🟡 Medium Severity02500✅ Passed
🔵 Low Severity001000✅ Passed

⏱️ SLA Breach Summary

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

SeverityBreaches (with fixes)Breaches (no fixes)SLA Threshold (with/no fixes)Status
🔴 Critical0015 / 30 days✅ Passed
🟠 High0030 / 120 days✅ Passed
🟡 Medium0090 / 365 days✅ Passed
🔵 Low00180 / 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: 0
  • Medium without fixes: 2
  • Low without fixes: 0

✅ BUILD PASSED - All security checks passed

@cs-rajcs-raj mentioned this pull request Aug 12, 2026
Closed
4 tasks
harshitha-cstk
harshitha-cstk previously approved these changes Aug 12, 2026
View reviewed changes
@harshitha-cstk
harshitha-cstk dismissed stale reviews from aniket-shikhare-cstk and themself via f7cfcdaAugust 12, 2026 12:25
@github-actions

github-actionsBot commented Aug 12, 2026

Copy link
Copy Markdown

🔒 Security Scan Results

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

Check TypeCount (with fixes)Without fixesThresholdResult
🔴 Critical Severity0010✅ Passed
🟠 High Severity0025✅ Passed
🟡 Medium Severity02500✅ Passed
🔵 Low Severity001000✅ Passed

⏱️ SLA Breach Summary

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

SeverityBreaches (with fixes)Breaches (no fixes)SLA Threshold (with/no fixes)Status
🔴 Critical0015 / 30 days✅ Passed
🟠 High0030 / 120 days✅ Passed
🟡 Medium0090 / 365 days✅ Passed
🔵 Low00180 / 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: 0
  • Medium without fixes: 2
  • Low without fixes: 0

✅ BUILD PASSED - All security checks passed

@cs-raj
cs-raj merged commit 34862fc into v1-legacyAug 12, 2026
10 checks passed
@cs-raj
cs-raj deleted the fix/DX-10156-v1-legacy-release-trigger branch August 12, 2026 13:32
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@netrajpatelnetrajpatelnetrajpatel approved these changes
@harshitha-cstkharshitha-cstkharshitha-cstk approved these changes
@aniket-shikhare-cstkaniket-shikhare-cstkaniket-shikhare-cstk left review comments

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@cs-raj@netrajpatel@harshitha-cstk@aniket-shikhare-cstk