Skip to content

Build(deps): Bump cross-spawn from 7.0.3 to 7.0.6 in /browser-gui in the npm_and_yarn group across 1 directory #623

Build(deps): Bump cross-spawn from 7.0.3 to 7.0.6 in /browser-gui in the npm_and_yarn group across 1 directory

Build(deps): Bump cross-spawn from 7.0.3 to 7.0.6 in /browser-gui in the npm_and_yarn group across 1 directory #623

Status Success
Total duration 14m 26s
Artifacts

main.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

21 warnings
build (macos-13, Xcode_15.2)
The following may be certifi configuration files and have not been removed! If desired, remove them manually with `rm -rf`: /usr/local/etc/ca-certificates
build (macos-13, Xcode_15.2)
[email protected] 3.13.0_1 is already installed and up-to-date. To reinstall 3.13.0_1, run: brew reinstall [email protected]
build (macos-13, Xcode_15.2)
libtool 2.5.3 is already installed and up-to-date. To reinstall 2.5.3, run: brew reinstall libtool
build (macos-13, Xcode_15.2)
pkg-config 0.29.2_3 is already installed and up-to-date. To reinstall 0.29.2_3, run: brew reinstall pkg-config
build (macos-13, Xcode_14.3.1)
The following may be certifi configuration files and have not been removed! If desired, remove them manually with `rm -rf`: /usr/local/etc/ca-certificates
build (macos-13, Xcode_14.3.1)
[email protected] 3.13.0_1 is already installed and up-to-date. To reinstall 3.13.0_1, run: brew reinstall [email protected]
build (macos-14, Xcode_16.0)
The following may be certifi configuration files and have not been removed! If desired, remove them manually with `rm -rf`: /opt/homebrew/etc/ca-certificates
build (macos-13, Xcode_14.3.1)
libtool 2.5.3 is already installed and up-to-date. To reinstall 2.5.3, run: brew reinstall libtool
build (macos-14, Xcode_16.0)
[email protected] 3.13.0_1 is already installed and up-to-date. To reinstall 3.13.0_1, run: brew reinstall [email protected]
build (macos-13, Xcode_14.3.1)
pkg-config 0.29.2_3 is already installed and up-to-date. To reinstall 0.29.2_3, run: brew reinstall pkg-config
build (macos-14, Xcode_16.0)
pkg-config 0.29.2_3 is already installed and up-to-date. To reinstall 0.29.2_3, run: brew reinstall pkg-config
build (macos-15, Xcode_16.0)
The following may be certifi configuration files and have not been removed! If desired, remove them manually with `rm -rf`: /opt/homebrew/etc/ca-certificates
build (macos-15, Xcode_16.0)
[email protected] 3.13.0_1 is already installed and up-to-date. To reinstall 3.13.0_1, run: brew reinstall [email protected]
build (macos-15, Xcode_16.0)
pkg-config 0.29.2_3 is already installed and up-to-date. To reinstall 0.29.2_3, run: brew reinstall pkg-config
build (macos-12, Xcode_14.2)
A brownout will take place on November 25, 14:00 UTC - November 26, 00:00 UTC to raise awareness of the upcoming macOS-12 environment removal. For more details, see https://github.com/actions/runner-images/issues/10721
build (macos-12, Xcode_14.2)
[email protected] 3.12.6 is already installed and up-to-date. To reinstall 3.12.6, run: brew reinstall [email protected]
build (macos-12, Xcode_14.2)
automake 1.17 is already installed and up-to-date. To reinstall 1.17, run: brew reinstall automake
build (macos-12, Xcode_14.2)
libsndfile 1.2.2 is already installed and up-to-date. To reinstall 1.2.2, run: brew reinstall libsndfile
build (macos-12, Xcode_14.2)
libtool 2.4.7 is already installed and up-to-date. To reinstall 2.4.7, run: brew reinstall libtool
build (macos-12, Xcode_14.2)
pkg-config 0.29.2_3 is already installed and up-to-date. To reinstall 0.29.2_3, run: brew reinstall pkg-config
build (macos-12, Xcode_14.2)
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.