Skip to content

Build Android Release #347

Build Android Release

Build Android Release #347

Triggered via pull request review October 23, 2024 21:54
@XuNealXuNeal
submitted b12c0b3
Status Success
Total duration 28m 21s
Artifacts

build-release-android.yml

on: pull_request_review
Build Android Release
28m 10s
Build Android Release
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
Build Android Release
This job uses deprecated functionality from the 'gradle/gradle-build-action' action. Consult the Job Summary for more details.
Build Android Release
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build Android Release
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/github-script@v6, actions/checkout@v3, actions/cache@v2, android-actions/setup-android@v2, slackapi/[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/
Build Android Release
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build Android Release
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.