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 @hashgraph/sdk from 2.42.0 to 2.48.1 #431

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

swirlds-automation
Copy link
Contributor

snyk-top-banner

Snyk has created this PR to upgrade @hashgraph/sdk from 2.42.0 to 2.48.1.

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

  • The recommended version was released on 2 months ago.

Release notes
Package name: @hashgraph/sdk from @hashgraph/sdk 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 @hashgraph/sdk from 2.42.0 to 2.48.1.

See this package in npm:
@hashgraph/sdk

See this project in Snyk:
https://app.snyk.io/org/hedera-services/project/1b0ee30a-a893-4fc8-992a-f89ac810873b?utm_source=github&utm_medium=referral&page=upgrade-pr
@swirlds-automation swirlds-automation requested a review from a team as a code owner August 22, 2024 06:06
Copy link

Unit Test Results

35 tests  ±0   35 ✅ ±0   16m 3s ⏱️ +16s
21 suites ±0    0 💤 ±0 
 1 files   ±0    0 ❌ ±0 

Results for commit 3b5af2a. ± Comparison against base commit 7c22efe.

Copy link

E2E Test Results

4 tests  ±0   4 ✅ ±0   47s ⏱️ ±0s
1 suites ±0   0 💤 ±0 
1 files   ±0   0 ❌ ±0 

Results for commit 3b5af2a. ± Comparison against base commit 7c22efe.

Copy link

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation Diff coverage
+0.00% (target: -1.00%)
Coverage variation details
Coverable lines Covered lines Coverage
Common ancestor commit (7c22efe) 1636 1085 66.32%
Head commit (3b5af2a) 1636 (+0) 1085 (+0) 66.32% (+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 (#431) 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

Copy link

codecov bot commented Aug 22, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 66.09%. Comparing base (4fbb824) to head (3b5af2a).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #431   +/-   ##
=======================================
  Coverage   66.09%   66.09%           
=======================================
  Files          60       60           
  Lines        1879     1879           
  Branches      280      280           
=======================================
  Hits         1242     1242           
- Misses        602      636   +34     
+ Partials       35        1   -34     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

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