Repository navigation
Releases: coisa/error-handler
Release list
v2.5.5
Fixed
-
Require optional Whoops
^2.18.7for development HTML, adopting its upstream fix
for native STDIN andphp -rsource inspection. Reject older Whoops versions
through Composer without making the optional package mandatory. Preserve original exception
frames, one original report, legitimate application warnings and the existing
2.x response and lifecycle policies. Align installation guidance and the bundled
consumer skill, with bounded native source regressions alongside the renderer's
unit tests.(#121)
v2.5.4
Changed
-
Install the Changelog agent skill through the development-only
llm/skills
Composer plugin and the committed skill-source configuration. Keep generated
agent instructions out of Git and Composer distributions instead of maintaining
a versioned copy of the upstream skill.
Also synchronize the Container and Config skills from their installed Composer
packages.(#119)
v2.5.3
Changed
-
Replace Changesets with the Fast Forward Changelog lifecycle for independent
release notes, PR validation and comments, Dependabot notes and reviewed version
PRs, preserving Git-tag-based Composer releases without Node release tooling.
Normalize the complete changelog to Keep a Changelog categories, verified release
publication dates and version comparisons; retain historical descriptions,
correct the original delivery references for stacked contributions and record
the existing policy that omits automatic author acknowledgements.
Include the upstream release-tooling skill in the project with its native
installation receipt.(#115)
v2.5.2
Patch Changes
-
#114
e00b98c- Preserve caller-owned output buffers when a capture reporter closes the factory's buffer and returns normally. Use the existing diagnostic fallback without consuming caller bytes or invoking their output callbacks; retain empty-output and"0"fallback behavior. -
#116
f5e985f- Document security support for the latest stable release and the existing private reporting channel. Include the security policy in Composer distributions and link it from the README and consumer skill.
v2.5.1
v2.5.0
Minor Changes
-
#92
fb418fb- Add an opt-in pure JSON throwable response factory with generic public output, integer HTTP 400–599 status preservation and an explicit development mode with metadata-only traces and no-store caching. Add a separate report-before-render response decorator for the existing 2.x middleware and independent Interop providers for explicit legacy or JSON composition with fresh HTTP scopes. Applications select the JSON provider before the base provider and supply PSR-17 factories and a private reporter; the FastForward integration requires PHP 8.3+ and an application runtime dependency, while the core retains PHP 7.4 and existing container/output-capture defaults. Debug alone needs the optional JSON extension on PHP 7.4. -
#92
fae2d58- Add an optional Whoops HTML response renderer with application-controlled development activation and page configuration. Provide an independent opt-in Interop profile using the application's PSR-17 factories and private reporter, with a lazy configurable PrettyPageHandler service. Applications compose the base and Whoops maps in one aggregate and obtain fresh middleware scopes through FastForward on PHP 8.3+. Sequential rendering preserves page configuration and replaces diagnostic state, with a fresh Run, response and stream. Reuse explicit reporting composition without changing existing middleware, capture defaults or HTTP negotiation; service resolution and fallback remain the container's policy. Bundle focused HTML guidance and executable consumer programs in the canonical skill, with installed-API availability checks. Require optional Whoops ^2.18.4 or later within 2.x, including the upstream PHP 8.5 fix to avoid its additional PHP deprecation report during rendering. Core PHP 7.4 and ordinary production installations still do not require Whoops or FastForward.
Patch Changes
v2.4.4
v2.4.3
v2.4.2
Patch Changes
-
#93
e39b363- Preserve the original failure when wrapping container exceptions with string codes such as PDO SQLSTATE. Integer codes remain unchanged; string codes use zero on the wrapper and remain available on its previous throwable. -
#91
9e4876d- Use the application's PSR-17 default reason phrase when an exception message contains forbidden HTTP status-line control bytes. Preserve valid messages, the existing 400–500 status mapping, original throwable reporting and response body behavior.
v2.4.1
Patch Changes
-
#86
94055d2- Expose all existing 2.x recipes in a complete source-checked cookbook. Preserve
website excerpt validation and verify every full recipe against executable PHP,
with application setup, consumer guidance and navigation aligned. -
#87
85d8488- Permit coverage decreases while requiring an overall line-coverage minimum of
80% by default, configurable with MINIMUM_COVERAGE_THRESHOLD. Preserve authentic
baseline comparisons, per-file differences and the existing sticky PR report. -
#84
f095afe- Continue exceptional output-buffer cleanup when PHP removes a buffer before its
output callback throws. Preserve the original reporter/capture failure and
caller-owned buffers while discarding remaining reachable removable scopes. -
#83
e40dddd- Describe the released logging and best-effort adapters as available opt-in 2.x APIs across the guides, cookbook, static site and consumer skill. Retain installed-version checks and the distinction between pending Changesets and published releases.