Document semver policy for dependencies #377
Closed
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.
The PR #376 introduced a mixed semver approach (tilde for build tools, caret for linters) which triggered an automated review suggesting standardization. User rejected the suggestion with rationale, but the policy was undocumented.
After analyzing the comment thread, no code changes are needed. The current
package.jsonalready implements the intended policy:~(patch updates only) - affects output^(minor updates) - dev-onlyThe comment was a rejection of the bot's suggestion, not a request for changes. The existing implementation is correct per user intent.
Status: No changes required. Closing as the current state matches the desired policy.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.