Rename validate-changelog to changenotes - #4143
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
The focused rename is consistent and no stale references remain.
Review tier: Balanced
Findings: None
What changed in this PR
Renames the change-note utility and aligns its CLI help text with the new name.
Changes:
- Updates the usage message from
validate-changelog.mtstochangenotes.mts.
| File | Description |
|---|---|
pr-checks/changenotes.mts |
Updates the displayed CLI command name. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
mario-campos
approved these changes
Sep 11, 2026
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
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.
Follow-up to #4128. As @mario-campos noted there, the script will have functions other than validation in the future. This PR renames it to reflect that it offers functionality related to change notes. We already have scripts that work directly on the overall changelog (
changelog.tsand(bundle|prepare|rollback)-changelog.ts), which is distinct from the new change notes files, so thechangenote.mtsname makes sense.Risk assessment
For internal use only. Please select the risk level of this change:
Which use cases does this change impact?
Environments:
How did/will you validate this change?
.test.tsfiles).If something goes wrong after this change is released, what are the mitigation and rollback strategies?
How will you know if something goes wrong after this change is released?
Are there any special considerations for merging or releasing this change?
Merge / deployment checklist