Skip to content

Ensure version publishes always carry release notes#46

Merged
NagyVikt merged 1 commit intomainfrom
agent/codex/20260412-023437-perzeus-megkapja-hu-release-notes-policy
Apr 12, 2026
Merged

Ensure version publishes always carry release notes#46
NagyVikt merged 1 commit intomainfrom
agent/codex/20260412-023437-perzeus-megkapja-hu-release-notes-policy

Conversation

@NagyVikt
Copy link
Copy Markdown
Collaborator

Automated by scripts/agent-branch-finish.sh (PR flow).

Added a standing release-note requirement to the repository agent contract,
propagated the same rule to the install template and contributor guide,
and created missing v5 release notes in README.

A metadata test now enforces that README release notes include the
current package version heading, so future version bumps cannot skip
documenting release changes.

Constraint: Keep release-note policy lightweight and dependency-free
Rejected: Add a release-notes generator dependency | unnecessary maintenance overhead
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: When bumping package.json version, add matching README release note heading in the same change
Tested: npm test; node --check bin/multiagent-safety.js; npm pack --dry-run
Not-tested: GitHub release body automation
@NagyVikt NagyVikt force-pushed the agent/codex/20260412-023437-perzeus-megkapja-hu-release-notes-policy branch from 77edeaf to 0d1f6a7 Compare April 12, 2026 00:48
@NagyVikt NagyVikt merged commit f1465f1 into main Apr 12, 2026
7 checks passed
@NagyVikt NagyVikt deleted the agent/codex/20260412-023437-perzeus-megkapja-hu-release-notes-policy branch April 12, 2026 00:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant