Skip to content

prepare release 0.3.1 #61

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ErwanLT merged 1 commit into from
Sep 29, 2026
Merged

prepare release 0.3.1 #61

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/project.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
release:
current-version: "0.3.0"
current-version: "0.3.1"
next-version: "999-SNAPSHOT"
2 changes: 1 addition & 1 deletion ROADMAP.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

> Chaos engineering extension for Quarkus -- inject latency, exceptions, HTTP failures, and dependency degradation into your running application.

Current status: **preview** (v0.3.0 released, v0.4.0 in development)
Current status: **preview** (v0.3.1 released, v0.4.0 in development)

---

Expand Down
14 changes: 13 additions & 1 deletion docs/modules/ROOT/pages/release-notes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,17 +9,29 @@ include::../partials/attributes.adoc[]
|===
|Version |Date

|0.3.1
|2026-09-28

|0.3.0
|2026-09-25
|===

=== 0.3.1 (unreleased)
=== 0.3.1

==== Improvements

* The auto-off is held by the engine instead of the browser: chaos switches itself off at the deadline even when the Dev UI is closed, and a pending auto-off survives a dev-mode live reload. The delay is bounded to 24 hours, and deactivating chaos (master toggle or kill switch) cancels it, while a configuration reset leaves it pending.
* New JSON-RPC methods `startAutoOff(minutes)` and `cancelAutoOff()`; `getStatus` exposes the time left in `autoOffRemainingMs`.
* A profile other than `NONE` also turns the response body assault off and resets the messages of the assaults it enables (`INTERMITTENT` answers `Internal Server Error (Goblin chaos)`). The client-side assaults and the armed layers stay untouched.

==== Bug Fixes

* An application producing an anonymous, local or non-static inner class (for example a `MeterFilter` returned by a producer method) no longer fails to start: the SERVICE layer only weaves its binding onto classes that can be CDI beans, and never onto constructors.
* `DATABASE` exceptions no longer corrupt the Agroal pool: the fault now fires before a connection is checked out, instead of from the acquire interceptor, which left the connection enlisted in the transaction while back in the pool ("Closing connection in incorrect state CHECKED_IN", ever-growing `agroal_active_count`).
* A request whose entry point sits in an `exclude-packages` package is no longer assaulted on the `SERVICE`, `DATABASE`, `MESSAGING` or `HTTP_OUT` layers: the layer used to be resolved before the targeting rules were checked.
* Once the auto-off has fired, chaos stays off across live reloads until it is switched on again, and clicking the master toggle just as the deadline elapses no longer switches chaos back on.
* A test application started by continuous testing keeps its own auto-off instead of sharing the one of the dev-mode application.
* The Dev UI dashboard survives transport errors and out-of-order status replies, and always reports an auto-disable.

=== 0.3.0

Expand Down
Loading