Repository navigation
fix(cli): publish activates a build already registered by preview or taps (4.7.2) - #66
Merged
Merged
Conversation
Mathieu2301
added a commit
that referenced
this pull request
Nov 20, 2026
…taps (4.7.2) (#66) Co-authored-by: Mathieu2301 <21021423+Mathieu2301@users.noreply.github.com>
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.
miakapp previewandmiakapp tapsregister the build they test.miakapp publishthen tried to upload the same digest again and the control plane refused it with 422invalid_artifact.publishnow reads the release first: when the digest is already registered with the same size, ABI and requirements, it activates it directly; when they differ, it says so instead of a generic 422. Regression test included.