Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade @snyk/protect from 1.1295.2 to 1.1295.3 #553

Merged
merged 1 commit into from
Mar 10, 2025

Conversation

tuanicom
Copy link
Owner

snyk-top-banner

Snyk has created this PR to upgrade @snyk/protect from 1.1295.2 to 1.1295.3.

ℹ️ 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 a month ago.

Release notes
Package name: @snyk/protect
  • 1.1295.3 - 2025-02-11

    1.1295.3 (2025-02-11)

    The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation

    Bug Fixes

    • security: Upgrades dependencies to address CVE-2025-21614
    • language-server: Improved memory usage when executing code scans on large projects
    • language-server: Fix incorrect filtering of files when executing code scans which could fail the analysis
    • language-server: Fix random unexpected logouts when using OAuth2 authentication
  • 1.1295.2 - 2025-01-24

    1.1295.2 (2025-01-24)

    The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation

    Bug Fixes

    • general: revert dependencies upgrade which introduced a regression on a number of Linux installations
from @snyk/protect GitHub release notes

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 @snyk/protect from 1.1295.2 to 1.1295.3.

See this package in npm:
@snyk/protect

See this project in Snyk:
https://app.snyk.io/org/tuanicom/project/37045203-d79c-4568-837a-36d05a44dbb3?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation Diff coverage
+0.00%
Coverage variation details
Coverable lines Covered lines Coverage
Common ancestor commit (1bdd425) 262 262 100.00%
Head commit (288857a) 262 (+0) 262 (+0) 100.00% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details
Coverable lines Covered lines Diff coverage
Pull request (#553) 0 0 ∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more

@coveralls
Copy link
Collaborator

Pull Request Test Coverage Report for Build 1629

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 100.0%

Totals Coverage Status
Change from base Build 1626: 0.0%
Covered Lines: 262
Relevant Lines: 262

💛 - Coveralls

@tuanicom tuanicom merged commit cc709bb into master Mar 10, 2025
20 checks passed
@tuanicom tuanicom deleted the snyk-upgrade-09bc698f6c8a865b150cc8383c6578c6 branch March 10, 2025 10:06
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.

3 participants