- Hedera issues regular software updates to keep its platform secure and efficient.
- Monthly upgrades are the standard schedule, with exceptions for urgent security fixes.
- Frequent updates help improve code quality, reduce release risk, and speed up customer feedback.
- Feature testing and release are managed through a process that includes feature flags and staged rollouts across networks.
- Larger, infrequent updates can lead to complexity, higher risks, and slower delivery of new features.
Hedera maintains a regular release cycle for its public blockchain network, updating its software monthly to improve security and keep pace with modern standards. The organization also issues out-of-cycle updates for critical fixes when immediate action is required.
The company organizes releases to minimize risks by avoiding sudden changes and prioritizing clear communication with users. Each update to the public network and supporting components—like mirror nodes—remains backwards compatible, following industry best practices for incremental upgrades.
Smaller, consistent changes are easier to check and test, according to Hedera. Automated testing and continuous integration pipelines allow developers to find and fix problems early. “Frequent, incremental releases allow for smaller changes to be deployed. This minimizes complexity, making it easier to test and maintain high code quality,” the company stated.
By releasing more often, Hedera can quickly provide new features and bug fixes. This approach improves customer satisfaction, makes problem resolution faster, and encourages open feedback loops. Research and operational models from other software engineering teams, as outlined by Hedera, support these methods.
Releases use feature flags—a system that can turn features on or off—so updates can be tested on preview or test networks before broader rollout. According to Hedera, “New features can be disabled using feature flags, which are set up in the network’s deployment configuration.” Community members are invited to share input on improvement proposals or request longer testing periods through the company’s technical steering processes. For more details, readers can refer to Ledger/hiero-improvement-proposals” rel=”noopener ugc nofollow”>Hiero Improvement Proposals.
Delaying updates comes with greater risks. Larger, infrequent releases tend to be more complex, make bugs harder to find, and slow down delivery of new features. Hedera notes that these challenges can also limit innovation, as developers become more cautious about introducing new changes.
The company stresses that monthly upgrades do not mean new features are rushed; some features are developed and tested for months before they go live. Additional quality checks are carried out before code moves from development to public release. More information on these processes is available in How Hedera Ensures Quality in Hiero Consensus Node Releases.
Critical issues outside the planned schedule are rare, but when they arise, Hedera acts immediately to protect the network. This strategy supports the stability and adaptability of the infrastructure while maintaining user trust.
Additional technical documentation, upgrade process details, and network status can be found on Hedera’s official blog and related resources.
✅ Follow BITNEWSBOT on Telegram, Facebook, LinkedIn, X.com, and Google News for instant updates.
Previous Articles:
- Cøbra: Bitcoin Knots Could Replace Core as Reference Client
- Everything Blockchain Adopts Flare’s XRPFi for Treasury Yield
- Hyperliquid XPL Futures Manipulated, Trader Nets $15M, Others Lose
- Axiom Sell Button Failure Triggers Panic, Losses for Memecoin Traders
- Pudgy Penguins Launch Web3 Party Game With Mythical Games
