Adjust bundle-amend behavior to support explicit resolve and no-resolve options#2669
Merged
Adjust bundle-amend behavior to support explicit resolve and no-resolve options#2669
Conversation
lcawl
approved these changes
Feb 9, 2026
Contributor
lcawl
left a comment
lcawl
left a comment
There was a problem hiding this comment.
I tested against elastic/elasticsearch#140795 and the amended bundles are now successfully resolved, thanks!
I shifted some of the details from changelog.md to changelog-bundle-amend.md since IMO the latter should be higher-level summary of the workflow. Hope that's okay!
🔍 Preview links for changed docs |
Mpdreamz
approved these changes
Feb 11, 2026
# Conflicts: # docs/cli/release/changelog-bundle-amend.md # src/tooling/docs-builder/Commands/ChangelogCommand.cs
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
3 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.
Fixes #419
Summary
Previously,
changelog bundle-amendalways produced unresolved amend files (file references only), regardless of whether the original bundle was resolved. This meant amend files couldn't be copied to another repo (e.g. for Cloud Serverless release notes) because they lacked the inline changelog data that the resolved parent bundle had - the consuming repo would need access to the original changelog files to render them.Changes
--no-resolveflag (mirroring bundle) so users can explicitly override the inferred behaviour.--resolve/--no-resolve/ neither now maps to the three-state logic: force on, force off, or infer from bundle.