Skip to content

fix: update v1 release plugins trigger branch to v1-legacy - #342

Closed
cs-raj wants to merge 7 commits into
v1-legacyfrom
fix/DX-10156-v1-legacy-release-trigger
Closed

fix: update v1 release plugins trigger branch to v1-legacy#342
cs-raj wants to merge 7 commits into
v1-legacyfrom
fix/DX-10156-v1-legacy-release-trigger

Conversation

@cs-raj

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

Copy link
Copy Markdown
Contributor

Summary

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

Changes

Release pipeline trigger

  • Updated `release-production-plugins.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 all 20 plugin publish steps from `tag: latest` → `tag: v1`
  • Once v2 owns `latest`, v1 plugins must publish under their own tag to avoid overwriting v2 packages as the default install
  • Users can install specific v1 plugins with e.g. `npm install -g @contentstack/cli-cm-export@v1`

Test plan

  • Verify `release-production-plugins.yml` triggers on `v1-legacy` not `main`
  • Verify all 20 plugin publish steps use `tag: v1`
  • Confirm `workflow_dispatch` is present for manual v1 releases
  • After v2 GA, validate a v1 plugin installs correctly via the `v1` dist-tag

Related

🤖 Generated with Claude Code

@cs-raj @claude
fix: update release plugins trigger branch from main to v1-legacy
9efdbca 
After CLI v2 takes over main, v1 hotfix releases must be triggered from
the v1-legacy branch. This change ensures the production plugins release
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 owner August 12, 2026 09:30
@snyk-io

snyk-io Bot commented Aug 12, 2026 •
edited
Loading

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 12, 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 12, 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 105 25 ✅ Passed
🟡 Medium Severity 2 53 500 ✅ Passed
🔵 Low Severity 0 0 1000 ✅ Passed

⏱️ SLA Breach Summary

⚠️ Warning: The following vulnerabilities have exceeded their SLA thresholds (days since publication).

Severity Breaches (with fixes) Breaches (no fixes) SLA Threshold (with/no fixes) Status
🔴 Critical 0 0 15 / 30 days ✅ Passed
🟠 High 0 1 30 / 120 days ⚠️ Warning
🟡 Medium 2 52 90 / 365 days ❌ Failed / ⚠️ Warning
🔵 Low 0 0 180 / 365 days ✅ Passed

🟡 Medium Severity - SLA Breached Issues (with fixes)

Showing 2 issue(s) that have exceeded the 90-day SLA threshold:

  1. Improper Validation of Specified Index, Position, or Offset in Input

    • ID: SNYK-JS-UUID-16133035
    • Package: uuid@8.3.2
    • Published: 111 days ago (SLA: 90 days)
    • CVSS Score: 6.3
    • CVE: CVE-2026-41907

  2. Improper Validation of Specified Index, Position, or Offset in Input

    • ID: SNYK-JS-UUID-16133035
    • Package: uuid@8.3.2
    • Published: 111 days ago (SLA: 90 days)
    • CVSS Score: 6.3
    • CVE: CVE-2026-41907

ℹ️ 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: 105
  • Medium without fixes: 53
  • Low without fixes: 0

❌ BUILD FAILED - Security checks failed

Please review and fix the security vulnerabilities before merging.

@cs-raj @claude
fix: use v1 npm dist-tag for v1-legacy production releases
521515d 
Once CLI v2 takes over latest, v1 plugin 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-actions Bot 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 Type Count (with fixes) Without fixes Threshold Result
🔴 Critical Severity 0 0 10 ✅ Passed
🟠 High Severity 0 105 25 ✅ Passed
🟡 Medium Severity 2 53 500 ✅ Passed
🔵 Low Severity 0 0 1000 ✅ Passed

⏱️ SLA Breach Summary

⚠️ Warning: The following vulnerabilities have exceeded their SLA thresholds (days since publication).

Severity Breaches (with fixes) Breaches (no fixes) SLA Threshold (with/no fixes) Status
🔴 Critical 0 0 15 / 30 days ✅ Passed
🟠 High 0 1 30 / 120 days ⚠️ Warning
🟡 Medium 2 52 90 / 365 days ❌ Failed / ⚠️ Warning
🔵 Low 0 0 180 / 365 days ✅ Passed

🟡 Medium Severity - SLA Breached Issues (with fixes)

Showing 2 issue(s) that have exceeded the 90-day SLA threshold:

  1. Improper Validation of Specified Index, Position, or Offset in Input

    • ID: SNYK-JS-UUID-16133035
    • Package: uuid@8.3.2
    • Published: 111 days ago (SLA: 90 days)
    • CVSS Score: 6.3
    • CVE: CVE-2026-41907

  2. Improper Validation of Specified Index, Position, or Offset in Input

    • ID: SNYK-JS-UUID-16133035
    • Package: uuid@8.3.2
    • Published: 111 days ago (SLA: 90 days)
    • CVSS Score: 6.3
    • CVE: CVE-2026-41907

ℹ️ 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: 105
  • Medium without fixes: 53
  • Low without fixes: 0

❌ BUILD FAILED - Security checks failed

Please review and fix the security vulnerabilities before merging.

@cs-raj cs-raj mentioned this pull request Aug 12, 2026
Merged
5 tasks
@github-actions

github-actions Bot 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 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

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 e258c55 August 12, 2026 12:32
@github-actions

github-actions Bot 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 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 12, 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

harshitha-cstk
harshitha-cstk previously approved these changes Aug 12, 2026
View reviewed changes
@github-actions

github-actions Bot commented Aug 13, 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

@cs-raj cs-raj closed this Aug 13, 2026
@cs-raj
cs-raj deleted the fix/DX-10156-v1-legacy-release-trigger branch August 13, 2026 07:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@harshitha-cstk harshitha-cstk harshitha-cstk approved these changes
@aniket-shikhare-cstk aniket-shikhare-cstk aniket-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.

3 participants

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