Repository navigation
Add alternative shared changelog fragment workflow - #22
Merged
Merged
Conversation
This was referenced Oct 2, 2026
tconley1428
marked this pull request as ready for review
October 5, 2026 16:43
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.
Add
changelog-fragments.ymlas an alternative reusable checkpoint for SDKs adopting per-PR notes in category folders. It invokes the caller's pinned sdk-rust tool, requires an added fragment, validates pending fragments, and retains current-label lookup and theskip-changelogoverride.Callers supply
sdk-rust-pathand optionallyfragments-directory. The existingchangelog.ymlremains unchanged while repositories migrate.Validation: actionlint passed. Python's companion PR exercises this workflow pinned to this branch's commit and sdk-rust's shared-tooling commit.
Companion PRs: