chore: core version bump

[cs-raj]

No description provided.

[snyk-io]

✅ 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]

🔒 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	76	25	✅ Passed
🟡 Medium Severity	0	42	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	0	30 / 120 days	✅ Passed
🟡 Medium	0	1	90 / 365 days	⚠️ Warning
🔵 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: 76
• Medium without fixes: 42
• Low without fixes: 0

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

Consider reviewing these vulnerabilities when fixes become available.

[Copilot]

🔵 Needs a closer look

Correct .talismanrc by retaining the existing entries and updating only the lockfile checksum.

Pull request overview

Bumps the core CLI to 2.0.1 and refreshes related dependencies and configuration.

Changes:

• Updates CLI and plugin dependency versions.
• Refreshes lockfile resolutions and integrity data.
• Updates Talisman configuration.

File summaries

File	Summary
pnpm-lock.yaml	Refreshes locked dependency versions and integrity data.
packages/contentstack/package.json	Bumps the core CLI and dependency versions.
.talismanrc	Updates the checksum but removes an existing ignore entry and metadata; retain those entries.

Review details

Files not reviewed (1)

• pnpm-lock.yaml: Generated file

Suppressed comments (1)

.talismanrc:3

• This update removes the existing Talisman ignore entry for .github/workflows/release-production-pipeline.yml and also drops the version: '1.0' metadata from the remaining entry. That changes secret-scan behavior for an unrelated workflow and leaves the config inconsistent with its existing generated format; retain both entries and update only the lockfile checksum.

- filename: pnpm-lock.yaml
  checksum: 06cb74068888fe29d2ca0c4092dfea03c8eca2a547fe970ce09b614941b49ff7

• Files reviewed: 2/3 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[github-actions]

🔒 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	40	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	0	30 / 120 days	✅ Passed
🟡 Medium	0	1	90 / 365 days	⚠️ Warning
🔵 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: 0
• Medium without fixes: 40
• Low without fixes: 0

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

Consider reviewing these vulnerabilities when fixes become available.

[amit-kanswal-cs]

LGTM

[Copilot]

🟡 Changes recommended

Restore the required Talisman configuration entries before approval.

Get a fresh assessment by requesting another Copilot review.

Review details

Files not reviewed (1)

• pnpm-lock.yaml: Generated file

Suppressed comments (1)

.talismanrc:3

• Please retain the ignore entry for .github/workflows/release-production-pipeline.yml. This workflow is unchanged in this PR, but removing its existing Talisman exemption makes the pre-commit hook scan it (see .husky/pre-commit:31-40), so any previously suppressed finding in that file can now block commits. Restore the filename/checksum/version block, or update its checksum only if the workflow is intentionally changed.

- filename: pnpm-lock.yaml
  checksum: cbcd291500cd619f18736fe4b1d2e5c98cc3699bc28feae851f054833e99ead9

• Files reviewed: 3/4 changed files
• Comments generated: 1
• Review effort level: Lite