chore(repo): Adjust "Publishing a Release" document to include internal changes section in changelog #17374
Conversation
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
…al changes section in changelog
Lms24
requested review from
a team,
AbhiPrasad,
andreiborza and
stephanie-anderson
and removed request for
a team and
stephanie-anderson
Lms24
commented
Aug 11, 2025
andreiborza
approved these changes
Aug 11, 2025
This was referenced Sep 29, 2025
This was referenced Oct 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR updates our release publishing guide to include an "Internal Changes" block which is toggle-able as a
<details>HTML element. Cursor's release publishing rule references this document, so I don't think we need to adjust the cursor rule. Likewise, ouryarn changeloglist already includes all changes anyway, so I think this is the only place that needs updating.side-note: Given this makes changelog creation a bit more cumbersome, I think using Cursor for it is ideal.