docs: bring CURRENT_STATE up to date with 0.4.4 and today's work - #150
Merged
Conversation
Records the 0.4.4 release (firmware-update-failure, Issue #138, PR #147) and corrects the package status table. Updates the external contribution pipeline section: the third good-first-issue completing (#138 in 0.4.4, the same contributor's second), the #140 invariant landing in PR #148, the third external contributor arriving and taking #137, and the patch-not-minor convention holding on its own for 0.4.4. Adds the current rule-coverage state: two of sixteen rules still lack a scenario, and the corpus arithmetic now reads 17 plus three issues to reach the v1.0 target of 20.
sepehr-safari
added
type:docs
This was referenced Jul 30, 2026
sepehr-safari
added a commit
that referenced
this pull request
Jul 30, 2026
Records the release log automation from Issue #151 and PR #152. This is the kind of entry the automation deliberately does not write: #152 machines the release facts and leaves narrative to humans, so the story of why it exists is hand-written. Adds the structural cause of the drift (the changesets release PR never touched this file, so three releases went stale and needed catch-up PRs #146 and #150), how the fix hooks into the changeset version step, which two spots are machine-owned versus hand-written, and the test coverage. Notes in the header which parts are now automatic, so nobody hand-edits between the RELEASE-LOG markers, and books the one unproven link: the changesets action committing this file into the version PR is not exercised until the next release.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Keeps the living document current after the
0.4.4release and today's pipelinework, which reached
mainthrough the changesets release PR and throughissue-only activity, neither of which touches this file.
Releases
0.4.4(firmware-update-failure, Issue Add a new scenario: firmware-update-failure #138, PR feat(scenarios): add firmware-update-failure scenario #147), published2026-07-30.
0.4.4.External contribution pipeline
good-first-issuecompleted: Add a new scenario: firmware-update-failure #138 by the same contributor as feat(scenarios): add firmware update success scenario #133,shipped in
0.4.4. Registry is at 17.the same PR.
MayurK-cmd) arrived and took Add a new scenario: heartbeat-timeout #137; Add a new scenario: repeated-boot-notification #139 held next.0.4.4, sov0.5.0stays reserved for OCPP 2.0.1.(
TIMEOUT_NO_HEARTBEAT,REPEATED_BOOT_NOTIFICATION), and the corpusarithmetic to the v1.0 target now reads 17 plus Add a new scenario: meter-value-zero #108, Add a new scenario: heartbeat-timeout #137 and Add a new scenario: repeated-boot-notification #139.
Verification
pnpm format:checkandpnpm lintpass. Every version, count and issue state inthe diff was checked against npm and GitHub. Documentation only, no changeset:
the file is not in the package
fileslist.