From 23c648817e5101ec0eee1353abacfaf4a4e36b24 Mon Sep 17 00:00:00 2001 From: NagyVikt Date: Mon, 13 Apr 2026 23:52:07 +0200 Subject: [PATCH] Keep release notes focused on user-facing changes before versioning Replace the placeholder v5.0.7 bump-only entry with an unreleased generated-draft section so upcoming notes can be prepared before assigning a version number. Constraint: User requested changelog text that reflects added behavior instead of patch-bump-only wording Rejected: Keep v5.0.7 bump-only line | does not describe real feature additions Confidence: high Scope-risk: narrow Reversibility: clean Directive: Add real Added/Changed/Fixed items in Unreleased first, then cut a version heading at publish time Tested: npm test (fails on pre-existing syntax error in bin/multiagent-safety.js:1306 unrelated to README change) Not-tested: publish/tag flow --- README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index fc0d781..48c316e 100644 --- a/README.md +++ b/README.md @@ -245,9 +245,10 @@ npm pack --dry-run ## Release notes -### v5.0.7 +### Unreleased (generated draft, not versioned yet) -- Bumped package version from `5.0.6` to `5.0.7` to stay one patch ahead for the next npm publish. +- Add the user-facing changes for the next release here before assigning a version number. +- Keep this section focused on behavior changes (`Added`, `Changed`, `Fixed`) rather than version-bump-only notes. ### v5.0.6