Repository navigation
Keep application upload output stable across waiting modes - #6
Merged
Merged
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
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.
Application upload and update currently move accepted resource IDs between flat and nested JSON fields when
--no-waitchanges. Both modes now expose the samedata.application,data.operation, anddata.packpaths, preserving flat accepted fields andsha256as compatibility aliases.data.operationis null when no status was observed; waiting returns the completed operation. No-wait remains nonblocking and does not poll. The README documents the result and explains that accepted responses do not carry an application revision.Validation: public boundary, vendor snapshots and source drift, typecheck, lint, mock smoke, and package dry run passed. Focused output/CLI/revision tests passed 140/140. Full suite: 528 passed, 6 failed, 1 skipped; five missing-Liberation-Serif compose failures reproduce on the unchanged base, and an unrelated randomized request-ID assertion passed on rerun. Live-server/plugin/player tests were not run.