Skip to content

ci: check that LLVM branch corresponds to semver before releasing #892

ci: check that LLVM branch corresponds to semver before releasing

ci: check that LLVM branch corresponds to semver before releasing #892

Triggered via pull request November 15, 2024 11:17
Status Success
Total duration 32m 15s
Artifacts

test.yaml

on: pull_request
Matrix: build-and-test
pr-checks
2s
pr-checks
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
cargo-checks
Unexpected input(s) 'save-if', valid inputs are ['entryPoint', 'args', 'command', 'arguments', 'command-arguments', 'manifest-path', 'log-level', 'rust-version', 'credentials']
cargo-checks
1 warnings found!
cargo-checks
The following actions use a deprecated Node.js version and will be forced to run on node20: rustsec/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
MacOS x86
ninja 1.12.1 is already installed and up-to-date. To reinstall 1.12.1, run: brew reinstall ninja
MacOS x86
You are using macOS 12. We (and Apple) do not provide support for this old version. It is expected behaviour that some formulae will fail to build in this old version. It is expected behaviour that Homebrew will be buggy and slow. Do not create any issues about this on Homebrew's GitHub repositories. Do not create any issues even if you think this message is unrelated. Any opened issues will be immediately closed without response. Do not ask for help from Homebrew or its maintainers on social media. You may ask for help in Homebrew's discussions but are unlikely to receive a response. Try to figure out the problem yourself and submit a fix as a pull request. We will review it but may or may not accept it.