Merged
Conversation
Bump package metadata from 5.0.2 to 5.0.3 and add the matching README release-notes entry so publish docs stay in sync with the package manifest. Constraint: Repo policy requires README release-notes update in the same change when version is bumped Rejected: Bump package files only | would fail release-note consistency guard Confidence: high Scope-risk: narrow Reversibility: clean Directive: Keep package version and README release heading aligned for every publish Tested: npm test; node --check bin/multiagent-safety.js Not-tested: npm publish against registry
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.
Summary
package.jsonandpackage-lock.jsonto5.0.3README.mdrelease-notes heading forv5.0.3Verification
npm testnode --check bin/multiagent-safety.js