Repository navigation
ci: pin the Rust toolchain action to its input-handling fix and check the Intel macOS build's architecture - #9
Merged
Conversation
… the Intel macOS build's architecture
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.
What changed
ci.ymltest and MSRV jobs,release.ymlbuild job):dtolnay/rust-toolchainmoves from89b1218on thestablebranch toe2a55d2on master, the merge of upstream #187 "Safely handle action inputs", as in Resourcestemplates/sign-and-publish-caller.yml. Thestablebranch is rebased onto every master commit, so a SHA pinned on it stops being reachable. Master requires atoolchaininput, so the steps that relied on the branch default now saytoolchain: stable. The MSRV step keeps its own toolchain read fromCargo.toml.release.yml):memorystick-macos-x86is cross-built on an arm64 runner and skipped by the smoke test, so it was signed with no automated check. A new step, "Check the cross-compiled artifact's architecture", runsfileon it and fails unless it reportsx86_64. The smoke test condition now usesmatrix.target != 'x86_64-apple-darwin', the same as the template.release.yml: the note thatrelease-typemust not be set, why-Ris needed on "Hold the release as a draft", why sign-and-publish is chained byneeds:, the# organisation pinlabel on the shared workflow ref (still619460ff), and thecode-signing-policynote..github/dependabot.yml): synced with Resourcestemplates/dependabot.yml. The github-actions entry now ignoresProject-Colony/Project-Colony-Resources*, so Dependabot never moves the organisation pin of the shared signing workflow for this repository alone. The cargo directory stays/src-tauriuntil the layout is flattened.Verification
yaml.safe_load).dependabot.ymlis identical to the template apart from the cargo directory.uses:inci.ymlandrelease.ymlis pinned to a 40-character SHA.filecheck as the template. The v0.1.0memorystick-macos-x86asset was already checked by hand and reports Mach-O 64-bit x86_64.