Fix coordinated releases with multiple unnamed artifacts - #667
Merged
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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
1 participant
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.
Coordinated module releases no longer fail merely because more than one generated artifact omits
-ID.Checkpoint identity now uses the artifact type, optional ID, and exact output filename. Existing wrappers with distinct
PackedandUnpackedoutputs therefore remain resumable without extra configuration. When two outputs still produce the same identity, PowerForge rejects the ambiguity and tells the maintainer to assign explicit unique IDs.Explicit IDs remain supported and are still useful when a publish destination needs to select a particular artifact.