Repository navigation
ci: keep the release AAR as a workflow artifact - #69
Merged
Merged
Conversation
Releases in this repo are immutable once published, so attaching the
AAR after publishing fails with HTTP 422 ("Cannot upload assets to an
immutable release"), as on v1.4.0. Upload it as a workflow artifact
again, as before #62, and drop the write permission it needed. The
tag check, tests and build stay.
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.
The v1.4.0 release workflow passed every check but failed at the last step:
HTTP 422: Cannot upload assets to an immutable release. Releases in this repo are immutable once published, so nothing can be attached afterwards.contents: writepermission the attach step needed.v1.4.0 itself is fine: JitPack built it (status ok), which is what users install.