Repository navigation
Release version 1.8.0 - #221
Merged
Merged
Conversation
AGENT-1371: release the reconnect options and ngrok 0.19.1, whose capped, jittered reconnect waits replace waits that grew to hours. A minor version, since this adds SessionBuilder methods and removes nothing.
wesnel
marked this pull request as ready for review
November 13, 2026 01:02
wesnel
requested review from
andrew-harris-at-ngrok,
grant-higgins-0,
joshbottelberghe,
kevin-ngrok and
sajethm
and
a balanced review from Copilot
November 13, 2026 01:03
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues block the 1.8.0 release preparation.
No open issues 🎉
What changed in this PR
Prepares @ngrok/ngrok 1.8.0 for publication, covering the reconnect options and improved retry defaults from #216.
Changes:
- Aligns the npm package, Rust crate, and Cargo lockfile versions at 1.8.0.
- Renames the changelog’s
Unreleasedheading to1.8.0, preserving its entries.
| File | Description |
|---|---|
package.json |
Bumps the npm package version to 1.8.0. |
CHANGELOG.md |
Finalizes the 1.8.0 release heading. |
Cargo.toml |
Bumps the Rust crate version to 1.8.0. |
Cargo.lock |
Synchronizes the root crate’s locked version to 1.8.0. |
Review effort: Balanced
andrew-harris-at-ngrok
approved these changes
Nov 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of AGENT-1371. Stacked on #216.
Releases
@ngrok/ngrok1.8.0, as the 1.7.0 release (#201) was made: the version inCargo.toml,Cargo.lockandpackage.json, and the changelog'sUnreleasedheading renamed to1.8.0with its entries kept.1.8.0 holds #216: the reconnect options, and ngrok 0.19.1, with which a session that loses its connection retries at most every 30 s, jittered, instead of waiting hours.
Once #218, #215, #216 and this merge, run the Publish workflow on
main. It runs CI, publishes 1.8.0 to npm and pushes thev1.8.0tag.Validation
yarn buildwith 1.8.0 changes no file but these four;index.jsandindex.d.tscome out the same.npm/*platform packages keep the version they have (1.6.0):napi prepublish, whichnpm publishruns, sets their versions and the root'soptionalDependenciesfrom the rootpackage.json, read in@napi-rs/cli'sPrePublishCommand. The 1.7.0 release left them the same way.Weak spots, assumptions and decisions
SessionBuildermethods and removes nothing. The alternatives were 1.7.1 and 2.0.0.main, so no pull request runs deps: bump ngrok to 0.19.0 #215's change to the Docker build step for them. Their first run is the push tomainafter deps: bump ngrok to 0.19.0 #215 merges; Publish runs the same CI before publishing, so a failure there stops the release.Reverting
Two-way door until Publish runs: reverting returns the version to 1.7.0 and the heading to
Unreleased. Once 1.8.0 is on npm, that version cannot be published again; a fix ships as 1.8.1.