v0.130.0 #11238
steven-sheehy
started this conversation in
Releases
v0.130.0
#11238
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
After previously migrating the repository to Hiero, this release focuses on migrating the code base to use Hiero in place of Hedera. The top-level folders were all renamed to remove the
hedera-mirror-
prefix in favor of a simpler module name likeimporter
. All Java packages were migrated fromcom.hedera.mirror
toorg.hiero.mirror
. Properties were converted fromhedera.mirror
tohiero.mirror
with a migration path for operators (see Breaking Changes). Finally, Prometheus metrics were also renamed to change Hedera to Hiero and standardized to include the module name.HIP-1046 gRPC web proxy endpoints support is now available. Support for persisting the new gRPC proxy endpoints on the node create and update transactions was implemented. Additionally, a new
grpc_proxy_endpoint
was added to each node entry in the/api/v1/network/nodes
REST API.The mirror node now sets an implicit
ContractID{shard, realm, num}
key on contract creation for contracts without a key. Additionally, we migrated existing contracts without a key to populate aContractID
key.An updated minimal and full database snapshot is now available for download and can be used to bootstrap new mirror nodes. The updated snapshots were taken with the 0.125.0 schema and reflect the database as of early March 2025. The minimal and full are identical except the minimal excludes our largest HCS topic and reduces the snapshot size by 90%.
Breaking Changes
All
hedera.mirror.*
properties were renamed tohiero.mirror.*
. This includes both environment variables (e.g.HEDERA_MIRROR
) and yaml properties. To mitigate the impact of this breaking change, a property migrator was added that automatically converts any Hedera property to Hiero. When any mirror node component starts up, it will log a warning that it converted legacy Hedera properties. It's recommended that operators note these warnings and transition their configuration to use the new Hiero prefixed properties. In the future, we might remove this migration logic after customers have had time to migrate their configuration.All
hedera_mirror
prometheus metrics were renamed tohiero_mirror
. Any alerts or dashboards that referenced these metrics were also updated to use the new hiero metric. An operator using these metrics outside these areas should update to use the renamed metrics.With the exception of the protobuf package, all packages were renamed from
com.hedera.mirror
toorg.hiero.mirror
. Since the mirror node does not publish a library that packages its code, this should not be user impacting. Any operator who's running a forked version of the code would need to update its folders and packages to reflect the new Hiero naming.Enhancements
Bug Fixes
NullPointerException
on FractionalFee getMaximumAmount() #11138Dependency Upgrades
@hashgraph
/proto from 2.16.0 to 2.17.0 in /rest #11131@aws-sdk
/client-s3 from 3.804.0 to 3.806.0 in /rest #11129@aws-sdk
/client-s3 from 3.802.0 to 3.804.0 in /hedera-mirror-rest #11113@testcontainers
/postgresql from 10.24.2 to 10.25.0 in /hedera-mirror-rest #11099@testcontainers
/redis from 10.24.2 to 10.25.0 in /hedera-mirror-rest #11097@aws-sdk
/client-s3 from 3.797.0 to 3.802.0 in /hedera-mirror-rest #11096@hashgraph
/proto from 2.16.0 to 2.17.0 in /hedera-mirror-rest/check-state-proof #11093Deployments
Contributors
Thank you to all the contributors who worked on this release:
@bilyana-gospodinova
@filev94
@jnels124
@mgoelswirlds
@nickeynikolovv
@nirbosl
@sdimitrov9
@steven-sheehy
@xin-hedera
This discussion was created from the release v0.130.0.
Beta Was this translation helpful? Give feedback.
All reactions