Run Code Linter

Merge branch 'main' into feat/new_widget_adapter_system #1558

Sign in to view logs

Triggered via push November 16, 2024 13:44

andycall

feat/new_widget_adapter_system

Status Success

Total duration 1m 16s

Artifacts –

code_linter.yml

on: push

Find merge conflicts

reformat-bridge

Annotations

1 error and 5 warnings

Process completed with exit code 1.

Find merge conflicts

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

reformat-bridge

The following actions uses node12 which is deprecated and will be forced to run on node16: EndBug/add-and-commit@v4. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

reformat-bridge

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, EndBug/add-and-commit@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

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.