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.1187.0 to 1.1188.0 #281

Merged
merged 2 commits into from
Aug 3, 2023

Conversation

tuanicom
Copy link
Owner

@tuanicom tuanicom commented Aug 2, 2023

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade @snyk/protect from 1.1187.0 to 1.1188.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 1 version ahead of your current version.
  • The recommended version was released 21 days ago, on 2023-07-12.
Release notes
Package name: @snyk/protect from @snyk/protect GitHub release notes

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:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@codecov
Copy link

codecov bot commented Aug 2, 2023

Codecov Report

Merging #281 (5b52d65) into master (540524f) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master      #281   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           29        29           
  Lines          260       260           
  Branches         3         3           
=========================================
  Hits           260       260           

@tuanicom tuanicom force-pushed the snyk-upgrade-c5ec65db9f9360598aacd2273ca6a3e4 branch from 2ac3fe5 to dac681a Compare August 2, 2023 23:27
@coveralls
Copy link
Collaborator

coveralls commented Aug 2, 2023

Pull Request Test Coverage Report for Build 445

  • 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 444: 0.0%
Covered Lines: 260
Relevant Lines: 260

💛 - Coveralls

@codacy-production
Copy link

codacy-production bot commented Aug 2, 2023

Coverage summary from Codacy

Merging #281 (5b52d65) into master (540524f) - See PR on Codacy

Coverage variation Diff coverage
+0.00%
Coverage variation details
Coverable lines Covered lines Coverage
Common ancestor commit (540524f) 260 260 100.00%
Head commit (5b52d65) 260 (+0) 260 (+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 (#281) 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

@sonarcloud
Copy link

sonarcloud bot commented Aug 3, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@tuanicom tuanicom merged commit e07f513 into master Aug 3, 2023
19 checks passed
@tuanicom tuanicom deleted the snyk-upgrade-c5ec65db9f9360598aacd2273ca6a3e4 branch August 3, 2023 10:40
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