Repository navigation
ci: add PR CI, SHA256SUMS and immutable tag releases - #11
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.
Gives the repo CloudHypervisor-style release handling without a second branch.
build.yaml(reusable): both arches through the builder image, which runs--self-test; su1000; patched scrcpy-server; assemblesdistwithbuild-info.jsonandSHA256SUMS.ci.yaml: runsbuild.yamlon every pull request; publishes nothing.master-release.yaml: pushes to master update the rollingmasterprerelease (same name and URL as today, now withSHA256SUMS) and the ghcr:masterimage.release.yaml: pushing a tagmaster-<9-char sha>publishes a non-prerelease with the same assets once (overwrite_files: false) and the ghcr image tagged with it. The rolling tagmasterhas no hyphen, so it does not match.Downstream images should pin a
master-<sha9>release and itsSHA256SUMS, not the rollingmasterrelease: its assets are rebuilt on every merge andscrcpy-server-secure.jaris not bit-for-bit reproducible.