Releases: getmilpa/http
Release list
v0.4.0
0.4.0 (2026-09-07)
⚠ BREAKING CHANGES
- UrlReferenceType::ABSOLUTE_URL, NETWORK_PATH and RELATIVE_PATH are removed. Each needs a request context — scheme, host, base path — and nothing in this framework holds any of it: zero occurrences of a base path, SCRIPT_NAME, a request context or an app.url key across the routing, runtime and web packages. They were declared before anything could render them, so asking for an absolute URL silently returned a path. See UPGRADING.md.
Features
v0.3.0
0.3.0 (2026-09-07)
⚠ BREAKING CHANGES
- Route::$host, Route::$priority and Route::$defaults are removed from the value object and its constructor. Nothing read them — measured across the framework's 37 packages, zero reads and no call site passed one. Callers using named arguments are unaffected; a positional caller now gets a TypeError rather than a silent misbinding of $middleware into a slot that no longer exists. See UPGRADING.md.
Features
v0.2.1
Sibling constraints declare a requirement, not a history.
This manifest enumerated one minor per release of its siblings, so every minor bump anywhere in the family cost a widening pull request here. That ceiling was protecting nothing: the answer to it firing was always to widen it.
The range asserts that Milpa's 0.x minors are compatible with each other — verified by mutation, not by argument: breaking a sibling on purpose takes a consumer's suite from green to 74 errors, so the protection lives in the suites rather than in the manifest.
Released as a PATCH on purpose. Widening a constraint admits what already existed; bumping its minor builds the next ceiling by hand.
Greenhouse decisions/0034.
v0.2.0
Accepts milpa/core ^0.8 — the line where a plugin can declare the words a human would use for it.
A ceiling that is merged but unreleased does not exist for anyone installing: Packagist keeps serving the old constraint. Greenhouse evidence/0193.