- The Solo project is officially moving to the Hiero namespace as part of Hedera‘s broader ecosystem transition.
- Developers have a six-month dual-publishing period until late July to migrate from the old @hashgraph/solo package to the new @hiero-Ledger/solo.
- After the transition, all future updates and fixes will be available exclusively under the new vendor-neutral namespace.
- This move reinforces a commitment to open source and community-driven governance under the Linux Foundation Decentralized Trust.
Hedera announced on February 25th that its Solo project is officially transitioning to the Hiero namespace, continuing a major ecosystem migration first announced in 2024. This shift moves projects from a Hedera-specific namespace to vendor-neutral ones managed by the Linux Foundation.
Consequently, the Solo codebase has already been migrated to its new GitHub home. However, one significant step remains for developers using the tool.
The crucial change is that the NPM package will move from @hashgraph/solo to @hiero-ledger/solo. To manage this smoothly, the team has instituted a clear dual-publishing timeline.
For six months, until the end of July, Solo will be published under both the old and new namespaces. This means both the @hashgraph/solo and @hiero-ledger/solo packages will receive updates. After this window, publishing will continue exclusively under the new @hiero-ledger/solo namespace.
The exact version marking the final cutover will be communicated later. Meanwhile, developers are urged to act promptly to avoid disruption.
In short, developers should update their dependency to @hiero-ledger/solo during the dual-publishing period. Avoiding delay is critical because future updates will only be available under the new namespace after the transition concludes.
✅ Follow BITNEWSBOT on Telegram, Facebook, LinkedIn, X.com, and Google News for instant updates.
