From 20be539917a34ea1919458dcfd5beec27bbe388b Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Mon, 10 Aug 2026 12:45:53 +0000 Subject: [PATCH] chore: version packages --- .changeset/brave-pandas-count.md | 5 ----- .changeset/repeated-boot-notification-scenario.md | 5 ----- CURRENT_STATE.md | 3 ++- packages/toolkit/CHANGELOG.md | 7 +++++++ packages/toolkit/package.json | 2 +- 5 files changed, 10 insertions(+), 12 deletions(-) delete mode 100644 .changeset/brave-pandas-count.md delete mode 100644 .changeset/repeated-boot-notification-scenario.md diff --git a/.changeset/brave-pandas-count.md b/.changeset/brave-pandas-count.md deleted file mode 100644 index 27007df..0000000 --- a/.changeset/brave-pandas-count.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@ocpp-debugkit/toolkit': patch ---- - -Add a meter-value-zero scenario to ensure a flat zero meter register does not report a failure. diff --git a/.changeset/repeated-boot-notification-scenario.md b/.changeset/repeated-boot-notification-scenario.md deleted file mode 100644 index ef94c21..0000000 --- a/.changeset/repeated-boot-notification-scenario.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@ocpp-debugkit/toolkit': patch ---- - -Add `repeated-boot-notification` scenario covering the `REPEATED_BOOT_NOTIFICATION` detection rule. The synthetic trace reboots a station three times in three minutes (one `BootNotification` per minute) followed by a single `Heartbeat`, exercising the 5 minute window used by the rule. diff --git a/CURRENT_STATE.md b/CURRENT_STATE.md index cfc7aad..3110ba6 100644 --- a/CURRENT_STATE.md +++ b/CURRENT_STATE.md @@ -25,6 +25,7 @@ step). Do not edit between the markers by hand. Full history lives in sections further down. +- `0.4.7` (2026-08-10): Add a meter-value-zero scenario to ensure a flat zero meter register does not report a failure.; Add `repeated-boot-notification` scenario covering the `REPEATED_BOOT_NOTIFICATION` detection rule. The synthetic trace reboots a station three times in three minutes (one `BootNotification` per minute) followed by a single `Heartbeat`, exercising the 5 minute window used by the rule. - `0.4.6` (2026-08-08): Add `heartbeat-timeout` scenario covering the `TIMEOUT_NO_HEARTBEAT` detection rule. The synthetic trace boots a station with `interval=300`, then sends a `StatusNotification` past the 2× interval threshold (`06:12:00.000Z`) with no `Heartbeat` anywhere in the trace. - `0.4.5` (2026-07-30): Report every refusing `AuthorizationStatus` in `FAILED_AUTHORIZATION`, not just `Invalid` (#156). The OCPP 1.6 enumeration (edition 2, section 7.2) has five values and only `Accepted` permits charging, so `Blocked`, `Expired` and `ConcurrentTx` end a driver's session exactly as `Invalid` does. The rule fired on `Invalid` alone, which meant a blocked or expired token produced a clean report, and silence from a detector reads as "this is not the problem". All four refusals now report under the existing code, with the status named in the description, and the suggested steps mention the `ConcurrentTx` case. Adds a `refused-authorization` scenario covering the three newly reported statuses, bringing the corpus to 18.; Match `FIRMWARE_UPDATE_FAILURE` to the OCPP 1.6 `FirmwareStatus` enumeration (#154, edition 2 section 7.25). The rule matched `DownloadPaused`, `InstallFailed` and `InstallRebootingFailed`, none of which are 1.6 status values, and did not match `InstallationFailed`, which is one of the two failure values the enumeration defines. A conformant station reporting a failed installation, the more consequential of the two firmware outcomes, went undetected. The rule now matches exactly `DownloadFailed` and `InstallationFailed`, and the `firmware-update-failure` scenario reports `InstallationFailed` instead of the non-spec `InstallFailed` it used before.; Transcribe the `STATUS_TRANSITION_VIOLATION` matrix from the OCPP 1.6 status transition table (#155, edition 2 section 4.9). The matrix disagreed with the table in both directions: it flagged 22 transitions the table permits and permitted 2 it does not list. The false positives were concentrated in the recovery rows, where the table allows a connector to return from `Faulted` to any pre-fault state and from `Unavailable` straight into an operative state, so any station that faulted mid-session and resumed charging, or that took a scheduled availability change during a session (`Charging -> Unavailable` and its siblings), produced a spurious warning. `Preparing -> Unavailable` and `Finishing -> Reserved` are absent from the table and are now flagged. The rule's matrix is now the table cell by cell, with the spec's own cell labels alongside it, and a test transcribes the table independently so the two have to agree. - `0.4.4` (2026-07-30): feat(scenarios): add firmware-update-failure scenario @@ -518,7 +519,7 @@ stabilization, the docs overhaul and release hardening. | Package | Status | Version | |---------|--------|---------| -| `@ocpp-debugkit/toolkit` | published | 0.4.6 | +| `@ocpp-debugkit/toolkit` | published | 0.4.7 | | `@ocpp-debugkit/core` | deprecated | 0.1.1 | | `@ocpp-debugkit/scenarios` | deprecated | 0.1.1 | | `@ocpp-debugkit/reporter` | deprecated | 0.1.1 | diff --git a/packages/toolkit/CHANGELOG.md b/packages/toolkit/CHANGELOG.md index 3e8be4e..f9837a0 100644 --- a/packages/toolkit/CHANGELOG.md +++ b/packages/toolkit/CHANGELOG.md @@ -1,5 +1,12 @@ # @ocpp-debugkit/toolkit +## 0.4.7 + +### Patch Changes + +- ca2bb0e: Add a meter-value-zero scenario to ensure a flat zero meter register does not report a failure. +- 49bc07e: Add `repeated-boot-notification` scenario covering the `REPEATED_BOOT_NOTIFICATION` detection rule. The synthetic trace reboots a station three times in three minutes (one `BootNotification` per minute) followed by a single `Heartbeat`, exercising the 5 minute window used by the rule. + ## 0.4.6 ### Patch Changes diff --git a/packages/toolkit/package.json b/packages/toolkit/package.json index c62b46d..caa6cd0 100644 --- a/packages/toolkit/package.json +++ b/packages/toolkit/package.json @@ -1,6 +1,6 @@ { "name": "@ocpp-debugkit/toolkit", - "version": "0.4.6", + "version": "0.4.7", "description": "Open-source DevTools for debugging OCPP charging sessions — parser, normalizer, timeline, failure detection, scenarios, replay, reports, CLI, and React components.", "license": "Apache-2.0", "type": "module",