Skip to content

Dev - #1141

Merged
vikrantraut-cstk merged 5 commits into
pre-stagefrom
dev
Aug 11, 2026
Merged

Dev#1141
vikrantraut-cstk merged 5 commits into
pre-stagefrom
dev

Conversation

@vikrantraut-cstk

Copy link
Copy Markdown
Contributor

🔗 Jira Ticket

Replace with your ticket link — required before requesting review.

MIGRATION-XXXX


📋 PR Type

  • ✨ Feature
  • 🐛 Bug Fix
  • 🔥 Hotfix
  • ♻️ Refactor
  • 🧹 Chore / Dependency Update
  • 📝 Documentation

📝 Description

What changed?

Why?


🧩 Affected Areas

  • api — Node.js backend
  • ui — React frontend
  • upload-api — Upload API server
  • docker / docker-compose
  • CI / GitHub Actions workflows
  • Environment variables / config
  • Other:

🧪 How to Test

Expected result:


📸 Screenshots / Recordings

Before After

🔗 Related PRs / Dependencies


✅ Author Checklist

Complete this before moving the PR out of Draft.

  • Branch follows naming convention: feature/, bugfix/, or hotfix/ + 5–30 lowercase chars
  • Jira ticket linked above
  • Self-reviewed the diff — no debug logs, commented-out code, or TODOs left in
  • .env / example.env updated if new environment variables were added
  • No sensitive credentials or secrets committed
  • Existing tests pass locally (npm test)
  • New tests written (or not applicable — explain why)
  • README.md / docs updated if behaviour changed
  • Talisman pre-push scan passes (no secrets flagged)

👀 Reviewer Notes


Migration v2 · Docs · Issues

chetan-contentstack and others added 3 commits August 7, 2026 12:19
Surfaces CLI import/localization failures instead of silently marking
the run complete, and stops a single entry's update error from aborting
every other entry queued behind it. Also fixes a Save-button layout
clip on the Map Entry step.
- Test-migration failures now surface (LogScreen/index.tsx recognizes
  the new "Test Migration Process Failed" marker).
- runCli.service.ts writes the completion marker only after every
  post-import side effect succeeds, so a run can no longer end up with
  both a Completed and a Failed marker; also dropped the dead
  loggerPath param on writeFailureMarker.
- entry-update-script.cjs tracks a per-entry failure count and throws
  once after the loop instead of never failing, so
  recordDeltaMigratedLocales can no longer mark a locale migrated when
  every entry actually failed. Propagated through updateEntryCli
  (rethrows instead of swallowing) and migration.service.ts (skips
  recordDeltaMigratedLocales and writes "Entry Update Process Failed"
  on failure); MigrationLogViewer.tsx recognizes that marker too.
- entryAssetMapper's ResizeObserver now watches document.body instead
  of the box it sets the height of, so it actually reacts to chrome
  height changes above it.
…continue

fix(CMG-1100): migration failure no longer stalls the whole run
@vikrantraut-cstk
vikrantraut-cstk requested a review from a team as a code owner August 10, 2026 05:24
@github-actions

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 16 378 25 ✅ Passed
🟡 Medium Severity 19 11 500 ✅ Passed
🔵 Low Severity 2 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 2 371 30 / 120 days ❌ Failed / ⚠️ Warning
🟡 Medium 0 0 90 / 365 days ✅ Passed
🔵 Low 0 0 180 / 365 days ✅ Passed

🟠 High Severity - SLA Breached Issues (with fixes)

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

  1. Inefficient Algorithmic Complexity

    • ID: SNYK-JS-IMMUTABLE-17900558
    • Package: immutable@5.1.5
    • Published: 31 days ago (SLA: 30 days)
    • CVSS Score: 8.7
    • CVE: CVE-2026-59880
  2. Integer Overflow or Wraparound

    • ID: SNYK-JS-IMMUTABLE-17900573
    • Package: immutable@5.1.5
    • Published: 31 days ago (SLA: 30 days)
    • CVSS Score: 8.7
    • CVE: CVE-2026-59879

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

❌ BUILD FAILED - Security checks failed

Please review and fix the security vulnerabilities before merging.

chetan-contentstack and others added 2 commits August 10, 2026 11:15
immutable@5.1.5 (transitive via sass) has two high-severity CVEs
(CVE-2026-59880, CVE-2026-59879) with fixes available since 5.1.6.
Bumps the ui override floor to >=5.1.9 (latest).
…snyk

chore(deps): bump immutable to clear Snyk SLA breach
@snyk-io

snyk-io Bot commented Aug 11, 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

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 14 378 25 ✅ Passed
🟡 Medium Severity 19 11 500 ✅ Passed
🔵 Low Severity 2 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 371 30 / 120 days ⚠️ Warning
🟡 Medium 0 0 90 / 365 days ✅ Passed
🔵 Low 0 0 180 / 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: 378
  • Medium without fixes: 11
  • Low without fixes: 0

⚠️ BUILD PASSED WITH WARNINGS - SLA breaches detected for issues without available fixes

Consider reviewing these vulnerabilities when fixes become available.

@vikrantraut-cstk
vikrantraut-cstk merged commit 26d68b3 into pre-stage Aug 11, 2026
13 checks passed
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.

1 participant