go/httpserver
2
0
Fork 0
Code Issues Pull Requests Packages Releases 3 Activity

chore(release): v0.9.2

Browse Source
This commit is contained in:
Claude Code
2026-03-25 00:38:43 +00:00
parent 5ab0120597
commit 1801754a9b
1 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
CHANGELOG.md
View File

@@ -5,6 +5,17 @@ All notable changes to this module will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this module adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). and this module adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [0.9.2] - 2026-03-25
### Fixed
- `OnStart` now binds the TCP listener synchronously via `net.Listen` before
launching the serve goroutine. A port-in-use (or any other bind) error is
returned immediately from `OnStart`, allowing the launcher to treat it as a
fatal startup failure and trigger a clean shutdown. Previously the error only
appeared in a log line while the application continued running without an
HTTP server.
## [0.9.1] - 2026-03-21 ## [0.9.1] - 2026-03-21
### Fixed ### Fixed
@@ -33,5 +44,6 @@ and this module adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.
- No middleware is installed by default; the full middleware stack is composed explicitly via `WithMiddleware` at construction time, keeping the stack visible and ordering unambiguous in the application source - No middleware is installed by default; the full middleware stack is composed explicitly via `WithMiddleware` at construction time, keeping the stack visible and ordering unambiguous in the application source
- chi was chosen as the underlying router because it uses stdlib `http.Handler` throughout, making it fully compatible with `httpmw` middleware and `httputil` handler adapters without any wrapper code at the boundary - chi was chosen as the underlying router because it uses stdlib `http.Handler` throughout, making it fully compatible with `httpmw` middleware and `httputil` handler adapters without any wrapper code at the boundary
[0.9.2]: https://code.nochebuena.dev/go/httpserver/releases/tag/v0.9.2
[0.9.1]: https://code.nochebuena.dev/go/httpserver/releases/tag/v0.9.1 [0.9.1]: https://code.nochebuena.dev/go/httpserver/releases/tag/v0.9.1
[0.9.0]: https://code.nochebuena.dev/go/httpserver/releases/tag/v0.9.0 [0.9.0]: https://code.nochebuena.dev/go/httpserver/releases/tag/v0.9.0