- ngrok Agent
Versioning
ngrok follows Semantic Versioning, and limits breaking changes to major upgrades.Cadence
Typical minor releases happen at least quarterly while typical patch releases are at least monthly. Critical bug fixes may cause a more immediate release outside of the normal cadence. ngrok also aims not to make releases during major US holiday periods.Support period
In accordance with the release cadence, ngrok supports a minor release for 14 months. Support includes:- Patches
- Critical security fixes
- The two-month upgrade cycle begins.
During the last two months of a support period, the following applies:
- No more patches or critical security fixes occur.
- ngrok attempts to notify users through the following channels:
- Via email
- Via social media
- Status Page
- Documentation Page
- That release’s agent banner
- The Agent version enters end-of-life.
- On the free plan, ngrok raises the minimum agent version on or after the end-of-life date.
From then on, an agent on an end-of-life version can no longer connect to ngrok’s cloud network: a new session fails with
ERR_NGROK_121and the agent exits at startup. An agent that is already connected stays up until it reconnects, then keeps retrying and logging the error while its endpoints stay offline. See Deprecation Notices if you received the email. - On a paid plan, the agent still connects and shows a generic deprecation warning.
- On the free plan, ngrok raises the minimum agent version on or after the end-of-life date.
From then on, an agent on an end-of-life version can no longer connect to ngrok’s cloud network: a new session fails with