Skip to content

[Snyk] Upgrade @contentstack/delivery-sdk from 5.2.1 to 5.2.2#190

Open
Aravind-Kumar-cstk wants to merge 1 commit into
mainfrom
snyk-upgrade-5ba77b8aa68c4dd7e10cb6a40b8a02e1
Open

[Snyk] Upgrade @contentstack/delivery-sdk from 5.2.1 to 5.2.2#190
Aravind-Kumar-cstk wants to merge 1 commit into
mainfrom
snyk-upgrade-5ba77b8aa68c4dd7e10cb6a40b8a02e1

Conversation

@Aravind-Kumar-cstk

Copy link
Copy Markdown
Contributor

snyk-top-banner

Snyk has created this PR to upgrade @contentstack/delivery-sdk from 5.2.1 to 5.2.2.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.

  • The recommended version was released 22 days ago.

Breaking Change Risk

Merge Risk: Low

Notice: This assessment is enhanced by AI.


Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade @contentstack/delivery-sdk from 5.2.1 to 5.2.2.

See this package in npm:
@contentstack/delivery-sdk

See this project in Snyk:
https://app.snyk.io/org/contentstack-devex/project/7bfde73b-0e04-4a5f-85a0-ebd699b4da10?utm_source=github&utm_medium=referral&page=upgrade-pr
@Aravind-Kumar-cstk

Copy link
Copy Markdown
Contributor Author

Merge Risk: Low

This is a patch version upgrade from v5.2.1 to v5.2.2. Patch releases are typically for bug fixes and minor enhancements and are not expected to contain breaking changes.

While specific release notes for version 5.2.2 were not found during the search, the nature of a patch update indicates a very low risk of introducing breaking changes.

Source: Package documentation

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

@Aravind-Kumar-cstk
Aravind-Kumar-cstk requested a review from a team as a code owner July 21, 2026 00:17
@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 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

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