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

fix: bump versions of hedera, json rpc relay, and mirror node #1147

Merged
merged 1 commit into from
Jan 13, 2025

Conversation

jeromy-cannon
Copy link
Contributor

Description

This pull request changes the following:

  • bump versions of hedera, json rpc relay, and mirror node

Related Issues

  • Closes #

@jeromy-cannon jeromy-cannon self-assigned this Jan 13, 2025
Copy link
Contributor

Unit Test Results - Linux

  1 files  ±0   58 suites  ±0   3s ⏱️ ±0s
227 tests ±0  227 ✅ ±0  0 💤 ±0  0 ❌ ±0 
232 runs  ±0  232 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit f142fcc. ± Comparison against base commit 8753723.

Copy link
Contributor

Unit Test Results - Windows

  1 files  ±0   58 suites  ±0   11s ⏱️ -3s
227 tests ±0  227 ✅ ±0  0 💤 ±0  0 ❌ ±0 
232 runs  ±0  232 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit f142fcc. ± Comparison against base commit 8753723.

Copy link
Contributor

E2E Test Report

 16 files  ±0  121 suites  ±0   1h 23m 6s ⏱️ -55s
258 tests ±0  258 ✅ ±0  0 💤 ±0  0 ❌ ±0 
261 runs  ±0  261 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit f142fcc. ± Comparison against base commit 8753723.

This pull request removes 118 and adds 118 tests. Note that renamed tests count towards both.
Account creation should succeed ‑ E2E Test Suite for 'node-cmd-e2e-pem-kill' node-cmd-e2e-pem-kill NodeCommand [testName node-cmd-e2e-pem-kill, mode kill, release v0.58.1] Node should have started successfully [mode kill, release v0.58.1] Account creation should succeed
Account creation should succeed ‑ E2E Test Suite for 'node-cmd-e2e-pem-kill' node-cmd-e2e-pem-kill NodeCommand [testName node-cmd-e2e-pem-kill, mode kill, release v0.58.1] Node should refresh successfully [mode kill, release v0.58.1] Account creation should succeed
Account creation should succeed ‑ E2E Test Suite for 'node-cmd-e2e-pem-stop' node-cmd-e2e-pem-stop NodeCommand [testName node-cmd-e2e-pem-stop, mode stop, release v0.58.1] Node should have started successfully [mode stop, release v0.58.1] Account creation should succeed
Account creation should succeed ‑ E2E Test Suite for 'node-cmd-e2e-pem-stop' node-cmd-e2e-pem-stop NodeCommand [testName node-cmd-e2e-pem-stop, mode stop, release v0.58.1] Node should refresh successfully [mode stop, release v0.58.1] Account creation should succeed
Balance query should succeed ‑ E2E Test Suite for 'node-cmd-e2e-pem-kill' node-cmd-e2e-pem-kill NodeCommand [testName node-cmd-e2e-pem-kill, mode kill, release v0.58.1] Node should have started successfully [mode kill, release v0.58.1] Balance query should succeed
Balance query should succeed ‑ E2E Test Suite for 'node-cmd-e2e-pem-kill' node-cmd-e2e-pem-kill NodeCommand [testName node-cmd-e2e-pem-kill, mode kill, release v0.58.1] Node should refresh successfully [mode kill, release v0.58.1] Balance query should succeed
Balance query should succeed ‑ E2E Test Suite for 'node-cmd-e2e-pem-stop' node-cmd-e2e-pem-stop NodeCommand [testName node-cmd-e2e-pem-stop, mode stop, release v0.58.1] Node should have started successfully [mode stop, release v0.58.1] Balance query should succeed
Balance query should succeed ‑ E2E Test Suite for 'node-cmd-e2e-pem-stop' node-cmd-e2e-pem-stop NodeCommand [testName node-cmd-e2e-pem-stop, mode stop, release v0.58.1] Node should refresh successfully [mode stop, release v0.58.1] Balance query should succeed
Node Proxy should be UP [mode kill, release v0.58.1 ‑ E2E Test Suite for 'node-cmd-e2e-pem-kill' node-cmd-e2e-pem-kill NodeCommand [testName node-cmd-e2e-pem-kill, mode kill, release v0.58.1] Node should have started successfully [mode kill, release v0.58.1] Node Proxy should be UP [mode kill, release v0.58.1
Node Proxy should be UP [mode stop, release v0.58.1 ‑ E2E Test Suite for 'node-cmd-e2e-pem-stop' node-cmd-e2e-pem-stop NodeCommand [testName node-cmd-e2e-pem-stop, mode stop, release v0.58.1] Node should have started successfully [mode stop, release v0.58.1] Node Proxy should be UP [mode stop, release v0.58.1
…
Account creation should succeed ‑ E2E Test Suite for 'node-cmd-e2e-pem-kill' node-cmd-e2e-pem-kill NodeCommand [testName node-cmd-e2e-pem-kill, mode kill, release v0.58.3] Node should have started successfully [mode kill, release v0.58.3] Account creation should succeed
Account creation should succeed ‑ E2E Test Suite for 'node-cmd-e2e-pem-kill' node-cmd-e2e-pem-kill NodeCommand [testName node-cmd-e2e-pem-kill, mode kill, release v0.58.3] Node should refresh successfully [mode kill, release v0.58.3] Account creation should succeed
Account creation should succeed ‑ E2E Test Suite for 'node-cmd-e2e-pem-stop' node-cmd-e2e-pem-stop NodeCommand [testName node-cmd-e2e-pem-stop, mode stop, release v0.58.3] Node should have started successfully [mode stop, release v0.58.3] Account creation should succeed
Account creation should succeed ‑ E2E Test Suite for 'node-cmd-e2e-pem-stop' node-cmd-e2e-pem-stop NodeCommand [testName node-cmd-e2e-pem-stop, mode stop, release v0.58.3] Node should refresh successfully [mode stop, release v0.58.3] Account creation should succeed
Balance query should succeed ‑ E2E Test Suite for 'node-cmd-e2e-pem-kill' node-cmd-e2e-pem-kill NodeCommand [testName node-cmd-e2e-pem-kill, mode kill, release v0.58.3] Node should have started successfully [mode kill, release v0.58.3] Balance query should succeed
Balance query should succeed ‑ E2E Test Suite for 'node-cmd-e2e-pem-kill' node-cmd-e2e-pem-kill NodeCommand [testName node-cmd-e2e-pem-kill, mode kill, release v0.58.3] Node should refresh successfully [mode kill, release v0.58.3] Balance query should succeed
Balance query should succeed ‑ E2E Test Suite for 'node-cmd-e2e-pem-stop' node-cmd-e2e-pem-stop NodeCommand [testName node-cmd-e2e-pem-stop, mode stop, release v0.58.3] Node should have started successfully [mode stop, release v0.58.3] Balance query should succeed
Balance query should succeed ‑ E2E Test Suite for 'node-cmd-e2e-pem-stop' node-cmd-e2e-pem-stop NodeCommand [testName node-cmd-e2e-pem-stop, mode stop, release v0.58.3] Node should refresh successfully [mode stop, release v0.58.3] Balance query should succeed
Node Proxy should be UP [mode kill, release v0.58.3 ‑ E2E Test Suite for 'node-cmd-e2e-pem-kill' node-cmd-e2e-pem-kill NodeCommand [testName node-cmd-e2e-pem-kill, mode kill, release v0.58.3] Node should have started successfully [mode kill, release v0.58.3] Node Proxy should be UP [mode kill, release v0.58.3
Node Proxy should be UP [mode stop, release v0.58.3 ‑ E2E Test Suite for 'node-cmd-e2e-pem-stop' node-cmd-e2e-pem-stop NodeCommand [testName node-cmd-e2e-pem-stop, mode stop, release v0.58.3] Node should have started successfully [mode stop, release v0.58.3] Node Proxy should be UP [mode stop, release v0.58.3
…

Copy link
Contributor

E2E Test Report

 16 files  ±0  121 suites  ±0   1h 23m 6s ⏱️ -55s
258 tests ±0  258 ✅ ±0  0 💤 ±0  0 ❌ ±0 
261 runs  ±0  261 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit f142fcc. ± Comparison against base commit 8753723.

This pull request removes 118 and adds 118 tests. Note that renamed tests count towards both.
Account creation should succeed ‑ E2E Test Suite for 'node-cmd-e2e-pem-kill' node-cmd-e2e-pem-kill NodeCommand [testName node-cmd-e2e-pem-kill, mode kill, release v0.58.1] Node should have started successfully [mode kill, release v0.58.1] Account creation should succeed
Account creation should succeed ‑ E2E Test Suite for 'node-cmd-e2e-pem-kill' node-cmd-e2e-pem-kill NodeCommand [testName node-cmd-e2e-pem-kill, mode kill, release v0.58.1] Node should refresh successfully [mode kill, release v0.58.1] Account creation should succeed
Account creation should succeed ‑ E2E Test Suite for 'node-cmd-e2e-pem-stop' node-cmd-e2e-pem-stop NodeCommand [testName node-cmd-e2e-pem-stop, mode stop, release v0.58.1] Node should have started successfully [mode stop, release v0.58.1] Account creation should succeed
Account creation should succeed ‑ E2E Test Suite for 'node-cmd-e2e-pem-stop' node-cmd-e2e-pem-stop NodeCommand [testName node-cmd-e2e-pem-stop, mode stop, release v0.58.1] Node should refresh successfully [mode stop, release v0.58.1] Account creation should succeed
Balance query should succeed ‑ E2E Test Suite for 'node-cmd-e2e-pem-kill' node-cmd-e2e-pem-kill NodeCommand [testName node-cmd-e2e-pem-kill, mode kill, release v0.58.1] Node should have started successfully [mode kill, release v0.58.1] Balance query should succeed
Balance query should succeed ‑ E2E Test Suite for 'node-cmd-e2e-pem-kill' node-cmd-e2e-pem-kill NodeCommand [testName node-cmd-e2e-pem-kill, mode kill, release v0.58.1] Node should refresh successfully [mode kill, release v0.58.1] Balance query should succeed
Balance query should succeed ‑ E2E Test Suite for 'node-cmd-e2e-pem-stop' node-cmd-e2e-pem-stop NodeCommand [testName node-cmd-e2e-pem-stop, mode stop, release v0.58.1] Node should have started successfully [mode stop, release v0.58.1] Balance query should succeed
Balance query should succeed ‑ E2E Test Suite for 'node-cmd-e2e-pem-stop' node-cmd-e2e-pem-stop NodeCommand [testName node-cmd-e2e-pem-stop, mode stop, release v0.58.1] Node should refresh successfully [mode stop, release v0.58.1] Balance query should succeed
Node Proxy should be UP [mode kill, release v0.58.1 ‑ E2E Test Suite for 'node-cmd-e2e-pem-kill' node-cmd-e2e-pem-kill NodeCommand [testName node-cmd-e2e-pem-kill, mode kill, release v0.58.1] Node should have started successfully [mode kill, release v0.58.1] Node Proxy should be UP [mode kill, release v0.58.1
Node Proxy should be UP [mode stop, release v0.58.1 ‑ E2E Test Suite for 'node-cmd-e2e-pem-stop' node-cmd-e2e-pem-stop NodeCommand [testName node-cmd-e2e-pem-stop, mode stop, release v0.58.1] Node should have started successfully [mode stop, release v0.58.1] Node Proxy should be UP [mode stop, release v0.58.1
…
Account creation should succeed ‑ E2E Test Suite for 'node-cmd-e2e-pem-kill' node-cmd-e2e-pem-kill NodeCommand [testName node-cmd-e2e-pem-kill, mode kill, release v0.58.3] Node should have started successfully [mode kill, release v0.58.3] Account creation should succeed
Account creation should succeed ‑ E2E Test Suite for 'node-cmd-e2e-pem-kill' node-cmd-e2e-pem-kill NodeCommand [testName node-cmd-e2e-pem-kill, mode kill, release v0.58.3] Node should refresh successfully [mode kill, release v0.58.3] Account creation should succeed
Account creation should succeed ‑ E2E Test Suite for 'node-cmd-e2e-pem-stop' node-cmd-e2e-pem-stop NodeCommand [testName node-cmd-e2e-pem-stop, mode stop, release v0.58.3] Node should have started successfully [mode stop, release v0.58.3] Account creation should succeed
Account creation should succeed ‑ E2E Test Suite for 'node-cmd-e2e-pem-stop' node-cmd-e2e-pem-stop NodeCommand [testName node-cmd-e2e-pem-stop, mode stop, release v0.58.3] Node should refresh successfully [mode stop, release v0.58.3] Account creation should succeed
Balance query should succeed ‑ E2E Test Suite for 'node-cmd-e2e-pem-kill' node-cmd-e2e-pem-kill NodeCommand [testName node-cmd-e2e-pem-kill, mode kill, release v0.58.3] Node should have started successfully [mode kill, release v0.58.3] Balance query should succeed
Balance query should succeed ‑ E2E Test Suite for 'node-cmd-e2e-pem-kill' node-cmd-e2e-pem-kill NodeCommand [testName node-cmd-e2e-pem-kill, mode kill, release v0.58.3] Node should refresh successfully [mode kill, release v0.58.3] Balance query should succeed
Balance query should succeed ‑ E2E Test Suite for 'node-cmd-e2e-pem-stop' node-cmd-e2e-pem-stop NodeCommand [testName node-cmd-e2e-pem-stop, mode stop, release v0.58.3] Node should have started successfully [mode stop, release v0.58.3] Balance query should succeed
Balance query should succeed ‑ E2E Test Suite for 'node-cmd-e2e-pem-stop' node-cmd-e2e-pem-stop NodeCommand [testName node-cmd-e2e-pem-stop, mode stop, release v0.58.3] Node should refresh successfully [mode stop, release v0.58.3] Balance query should succeed
Node Proxy should be UP [mode kill, release v0.58.3 ‑ E2E Test Suite for 'node-cmd-e2e-pem-kill' node-cmd-e2e-pem-kill NodeCommand [testName node-cmd-e2e-pem-kill, mode kill, release v0.58.3] Node should have started successfully [mode kill, release v0.58.3] Node Proxy should be UP [mode kill, release v0.58.3
Node Proxy should be UP [mode stop, release v0.58.3 ‑ E2E Test Suite for 'node-cmd-e2e-pem-stop' node-cmd-e2e-pem-stop NodeCommand [testName node-cmd-e2e-pem-stop, mode stop, release v0.58.3] Node should have started successfully [mode stop, release v0.58.3] Node Proxy should be UP [mode stop, release v0.58.3
…

Copy link

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation Diff coverage
+0.02% (target: -1.00%) 100.00%
Coverage variation details
Coverable lines Covered lines Coverage
Common ancestor commit (8753723) 20782 17490 84.16%
Head commit (f142fcc) 20809 (+27) 17517 (+27) 84.18% (+0.02%)

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 (#1147) 3 3 100.00%

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 Jan 13, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.39%. Comparing base (8753723) to head (f142fcc).
Report is 25 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #1147      +/-   ##
==========================================
- Coverage   83.40%   83.39%   -0.01%     
==========================================
  Files          77       77              
  Lines       20809    20809              
  Branches     1410     1772     +362     
==========================================
- Hits        17356    17354       -2     
+ Misses       3411     3346      -65     
- Partials       42      109      +67     
Files with missing lines Coverage Δ
version.ts 100.00% <100.00%> (ø)

... and 35 files with indirect coverage changes

Impacted file tree graph

@jeromy-cannon jeromy-cannon marked this pull request as ready for review January 13, 2025 19:19
@jeromy-cannon jeromy-cannon requested review from a team as code owners January 13, 2025 19:19
@jeromy-cannon jeromy-cannon merged commit 0784b46 into main Jan 13, 2025
40 of 43 checks passed
@jeromy-cannon jeromy-cannon deleted the bump-versions branch January 13, 2025 19:34
swirlds-automation added a commit that referenced this pull request Jan 13, 2025
## [0.33.0](v0.32.0...v0.33.0) (2025-01-13)

### Features

* add support for genesis throttle configuration ([#1026](#1026)) ([d8903a8](d8903a8))
* enable Blockstreams and uploader ([#1109](#1109)) ([ed6527b](ed6527b))
* inspect existing cluster resources during cluster setup ([#1094](#1094)) ([808516c](808516c))
* production readiness pass custom mirror node postgresql credentials and server address ([#1128](#1128)) ([f8b7e41](f8b7e41))
* support using GCS for backup uploader ([#1130](#1130)) ([5fe2f4e](5fe2f4e))
* update genesis-network.json to add roster entries and more ([#1122](#1122)) ([c27d1d6](c27d1d6))
* Updating solo to leverage changes after moving acme-cluster-issuer and haproxy-ingress out of mirror-node-explorer ([#1079](#1079)) ([7965894](7965894))
* use gcs for stream file storage ([#994](#994)) ([04d5806](04d5806))

### Bug Fixes

* add missing images, fix debug page images ([#1092](#1092)) ([4073d31](4073d31))
* Bug when running `solo cluster connect` after fresh install ([#1123](#1123)) ([1cd0e28](1cd0e28))
* bump solo-charts to 0.42.2 to pull in blockStreams fix ([#1138](#1138)) ([c482895](c482895))
* bump versions of hedera, json rpc relay, and mirror node ([#1147](#1147)) ([0784b46](0784b46))
* clarify how to use nvm ([#1125](#1125)) ([bdc1873](bdc1873))
* commit message of auto update ([#1106](#1106)) ([a3231f9](a3231f9))
* external link rendering ([#1118](#1118)) ([28af1fe](28af1fe))
* file size empty error when throttle file is provided on command line ([#1140](#1140)) ([5180a76](5180a76))
* fixed release artifact version issue and updated readme link ([#1090](#1090)) ([84e6611](84e6611))
* **lease:** reworks the previous fix addressing renewal issues ([#1105](#1105)) ([5edb9c9](5edb9c9))
* should run `npm install` before build ([#1117](#1117)) ([3398875](3398875))
* solo deployment create should use email address in local config if it is already there instead of prompting the user for it ([#1112](#1112)) ([362df60](362df60))
* started adding a yachli example and taskfile ([#1132](#1132)) ([8753723](8753723))
* update to AccountManager._getNodeClient() to parallel node connection setup ([#1091](#1091)) ([4959a12](4959a12))
@swirlds-automation
Copy link
Contributor

🎉 This PR is included in version 0.33.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@swirlds-automation
Copy link
Contributor

🎉 This PR is included in version 0.33.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants