chore(deps): update actions/setup-java action to v5 - autoclosed #1294
renovate[bot]Annotations
171 errors and 34 notices
|
build (11, 1.1, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (8, 1.1, windows-latest)
The strategy configuration was canceled because "build._11_1_1_ubuntu-latest" failed
|
|
build (8, 1.2, ubuntu-latest)
The strategy configuration was canceled because "build._11_1_1_ubuntu-latest" failed
|
|
build (8, 7, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 1.3, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (8, 1.3, ubuntu-latest)
The strategy configuration was canceled because "build._11_1_1_ubuntu-latest" failed
|
|
build (8, 1.1, ubuntu-latest)
The strategy configuration was canceled because "build._11_1_1_ubuntu-latest" failed
|
|
build (8, 1.2, windows-latest)
The strategy configuration was canceled because "build._11_1_1_ubuntu-latest" failed
|
|
build (8, 5, ubuntu-latest)
The strategy configuration was canceled because "build._11_1_1_ubuntu-latest" failed
|
|
build (8, 1.4, windows-latest)
The strategy configuration was canceled because "build._11_1_1_ubuntu-latest" failed
|
|
build (8, 1.4, ubuntu-latest)
The strategy configuration was canceled because "build._11_1_1_ubuntu-latest" failed
|
|
build (8, 5, windows-latest)
The strategy configuration was canceled because "build._11_1_1_ubuntu-latest" failed
|
|
build (8, 1.3, windows-latest)
The strategy configuration was canceled because "build._11_1_1_ubuntu-latest" failed
|
|
build (8, 6, windows-latest)
The strategy configuration was canceled because "build._11_1_1_ubuntu-latest" failed
|
|
build (8, 10, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (8, 6, ubuntu-latest)
The strategy configuration was canceled because "build._11_1_1_ubuntu-latest" failed
|
|
build (8, 6, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 9, macos-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (8, 9, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 1.2, macos-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (8, 8, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (8, 8, ubuntu-latest)
The strategy configuration was canceled because "build._11_1_1_ubuntu-latest" failed
|
|
build (8, 7, windows-latest)
The strategy configuration was canceled because "build._11_1_1_ubuntu-latest" failed
|
|
build (8, 10, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (8, 11, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (8, 15, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 1.3, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 10, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 1.2, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (8, 12, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (8, 9, ubuntu-latest)
The strategy configuration was canceled because "build._11_1_1_ubuntu-latest" failed
|
|
build (8, 11, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (8, 15, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (8, 17, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 10, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (8, 13, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 10, macos-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 1.1, macos-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (8, 12, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (8, 14, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 1.2, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 6, macos-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 7, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (8, 16, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 9, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 1.4, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 5, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 7, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 1.4, macos-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (8, 17, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 5, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (8, 14, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (8, 13, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 1.4, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 1.1, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 8, macos-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 5, macos-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (8, 16, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 6, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 8, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 6, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 9, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 1.1, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 1.3, macos-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (16, 1.1, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 7, macos-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 8, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 16, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (16, 6, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 14, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 17, macos-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (16, 5, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 13, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (16, 6, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 15, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (16, 1.2, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (16, 17, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 17, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (16, 12, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (16, 1.4, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (16, 11, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 10, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (16, 13, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 14, macos-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 1.4, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 11, macos-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 12, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (16, 7, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (16, 8, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 13, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (16, 12, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 11, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (16, 9, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (16, 9, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 14, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (16, 14, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 15, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (16, 1.4, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 1.2, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (16, 1.3, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 16, macos-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 11, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 16, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (16, 13, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (16, 16, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 17, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (16, 5, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (16, 1.1, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 1.3, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (16, 16, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (16, 10, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (16, 7, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 13, macos-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (16, 15, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (16, 8, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 1.3, macos-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 12, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (16, 11, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (16, 14, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (16, 1.2, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 1.1, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 1.3, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 1.1, macos-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 12, macos-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (16, 1.3, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (16, 10, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 15, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 14, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 5, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (16, 15, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 8, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (16, 17, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 17, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 7, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 12, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 1.2, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 5, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 6, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 16, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 13, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 7, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 1.4, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 8, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 15, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 14, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 1.2, macos-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 9, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 12, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 9, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 11, ubuntu-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 11, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 16, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 10, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 6, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 17, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 13, windows-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 17, macos-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 6, macos-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 15, macos-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 16, macos-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 5, macos-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 7, macos-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 12, macos-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 13, macos-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 15, macos-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 9, macos-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 8, macos-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 11, macos-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 10, macos-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 1.4, macos-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (17, 14, macos-latest)
The actions actions/checkout@v4.3.0, actions/setup-java@v5.4.0, and codecov/codecov-action@v5.4.3 are not allowed in ASSERT-KTH/flacoco because all actions must be pinned to a full-length commit SHA.
|
|
build (11, 9, macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|
|
build (11, 1.2, macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|
|
build (11, 10, macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|
|
build (11, 1.1, macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|
|
build (11, 6, macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|
|
build (11, 1.4, macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|
|
build (11, 8, macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|
|
build (11, 5, macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|
|
build (11, 1.3, macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|
|
build (11, 7, macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|
|
build (11, 17, macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|
|
build (11, 14, macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|
|
build (11, 11, macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|
|
build (11, 16, macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|
|
build (11, 13, macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|
|
build (17, 1.3, macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|
|
build (17, 1.1, macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|
|
build (11, 12, macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|
|
build (17, 1.2, macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|
|
build (17, 17, macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|
|
build (17, 6, macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|
|
build (11, 15, macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|
|
build (17, 16, macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|
|
build (17, 5, macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|
|
build (17, 7, macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|
|
build (17, 12, macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|
|
build (17, 13, macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|
|
build (17, 15, macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|
|
build (17, 9, macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|
|
build (17, 8, macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|
|
build (17, 11, macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|
|
build (17, 10, macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|
|
build (17, 1.4, macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|
|
build (17, 14, macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|