Skip to content

[Snyk] Upgrade org.jetbrains:annotations from 26.0.2 to 26.1.0#279

Open
harshithad0703 wants to merge 1 commit intomasterfrom
snyk-upgrade-be281cd45791140e99f0038a52b780e7
Open

[Snyk] Upgrade org.jetbrains:annotations from 26.0.2 to 26.1.0#279
harshithad0703 wants to merge 1 commit intomasterfrom
snyk-upgrade-be281cd45791140e99f0038a52b780e7

Conversation

@harshithad0703
Copy link
Contributor

snyk-top-banner

Snyk has created this PR to upgrade org.jetbrains:annotations from 26.0.2 to 26.1.0.

ℹ️ 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 2 versions ahead of your current version.

  • The recommended version was released 22 days ago.


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 org.jetbrains:annotations from 26.0.2 to 26.1.0.

See this package in maven:
org.jetbrains:annotations

See this project in Snyk:
https://app.snyk.io/org/contentstack-devex/project/9d1a0a2e-7e56-4c3c-b7a9-b62d7b208d90?utm_source=github&utm_medium=referral&page=upgrade-pr
@harshithad0703 harshithad0703 requested a review from a team as a code owner March 12, 2026 07:48
@github-actions
Copy link

We regret to inform you that you are currently not able to merge your changes into the master branch due to restrictions applied by our SRE team. To proceed with merging your changes, we kindly request that you create a pull request from the staging branch. Our team will then review the changes and work with you to ensure a successful merge into the master branch.

@github-actions
Copy link

🔒 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 1 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
Copy link

Coverage Summary

  • 📘 Instruction Coverage: 93%
  • 🌿 Branch Coverage: 80%

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