Apply the rulings, and stop a groupsign swallowing a whole run #694
owjs3901publish.yml
on: pull_request_target
Matrix: Test
Matrix: dotnet-test
Matrix: ruby-test
Matrix: jvm-test
Matrix: go-test
Deploy Landing
Matrix: jvm-native-build
Matrix: c-build
Matrix: dotnet-build
Matrix: go-build
Matrix: node-build
Matrix: python-build
Matrix: ruby-build
Matrix: upload-assets
C Publish
0s
.NET Publish
0s
Go Publish
0s
Node Publish
0s
Python Publish
0s
Ruby Publish
0s
Matrix: jvm-consumer-test
JVM Publish to Maven Central
0s
Annotations
98 warnings and 8 notices
|
Workflow execution policy warning (evaluate mode):
.github/workflows/publish.yml#L1
On November 2, 2026, GitHub will restrict `pull_request_target` on public repositories by default. To continue allowing the event trigger, configure an Actions policy. Learn more: https://gh.io/securely-using-pull_request_target#default-policy-for-pull_request_target
|
|
JVM Test - linux-aarch64
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: gradle/actions/setup-gradle@v4, gradle/actions/wrapper-validation@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
JVM Test - macos-aarch64
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: gradle/actions/setup-gradle@v4, gradle/actions/wrapper-validation@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Go Test - linux-arm64
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/setup-go@v5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Go Test - linux-arm64
Restore cache failed: Dependencies file is not found in /home/runner/work/braillify/braillify. Supported file pattern: go.sum
|
|
Go Test - linux-amd64
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/setup-go@v5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Go Test - linux-amd64
Restore cache failed: Dependencies file is not found in /home/runner/work/braillify/braillify. Supported file pattern: go.sum
|
|
Go Test - darwin-arm64
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/setup-go@v5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Go Test - darwin-arm64
Restore cache failed: Dependencies file is not found in /Users/runner/work/braillify/braillify. Supported file pattern: go.sum
|
|
JVM Test - linux-x86_64
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: gradle/actions/setup-gradle@v4, gradle/actions/wrapper-validation@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
JVM Test - windows-x86_64
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: gradle/actions/setup-gradle@v4, gradle/actions/wrapper-validation@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Ruby Test - macos-latest
Failed to save: Unable to reserve cache with key v0__2026090148a2__arm64-darwin23__bfbff0df054e274a902efd2b37db29ed6ceb9d5f9b5271d6eaec4671f88a76f4__29f3ec7149e5d230a74d61da04f6a130812e6b887cde942e27508c35f3dd3e58. More details: cache write denied: token has no writable scopes
|
|
Ruby Test - macos-latest
Failed to save: Unable to reserve cache with key cr20260920. More details: cache write denied: token has no writable scopes
|
|
Ruby Test - ubuntu-latest
Failed to save: Unable to reserve cache with key v0__2026090148a2__x86_64-linux__bfbff0df054e274a902efd2b37db29ed6ceb9d5f9b5271d6eaec4671f88a76f4__29f3ec7149e5d230a74d61da04f6a130812e6b887cde942e27508c35f3dd3e58. More details: cache write denied: token has no writable scopes
|
|
Ruby Test - ubuntu-latest
Failed to save: Unable to reserve cache with key cr20260920. More details: cache write denied: token has no writable scopes
|
|
Go Test - windows-amd64
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/setup-go@v5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Go Test - windows-amd64
Restore cache failed: Dependencies file is not found in D:\a\braillify\braillify. Supported file pattern: go.sum
|
|
Ruby Test - windows-latest
Failed to save: Unable to reserve cache with key v0__2026090148a2__x64-mingw-ucrt__7084ca74d4361f555a5ec97fa3d679ee55b4123bbca912456ed598880216c0cd__f5f7739789aebaef4a6e8f39014f83e415ea499c633c38aae057bf302a34f452. More details: cache write denied: token has no writable scopes
|
|
Ruby Test - windows-latest
Failed to save: Unable to reserve cache with key cr20260920. More details: cache write denied: token has no writable scopes
|
|
Go Test - darwin-amd64
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/setup-go@v5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Go Test - darwin-amd64
Restore cache failed: Dependencies file is not found in /Users/runner/work/braillify/braillify. Supported file pattern: go.sum
|
|
JVM Test - macos-x86_64
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: gradle/actions/setup-gradle@v4, gradle/actions/wrapper-validation@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
jsx-a11y(prefer-tag-over-role):
apps/landing/src/components/Footer/index.tsx#L25
apps/landing/src/components/Footer/index.tsx:25:11: Prefer `img` over `role` attribute `img`.
|
|
jsx-a11y(prefer-tag-over-role):
apps/landing/src/components/Footer/index.tsx#L16
apps/landing/src/components/Footer/index.tsx:16:7: Prefer `footer` over `role` attribute `contentinfo`.
|
|
react(set-state-in-effect):
apps/landing/src/components/Header/Pages.tsx#L15
apps/landing/src/components/Header/Pages.tsx:15:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
apps/landing/src/components/Header/MobileMenu.tsx#L25
apps/landing/src/components/Header/MobileMenu.tsx:25:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
apps/landing/src/components/home/HomePopup.tsx#L17
apps/landing/src/components/home/HomePopup.tsx:17:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
apps/landing/src/components/test-case/TestCaseResults.tsx#L56
apps/landing/src/components/test-case/TestCaseResults.tsx:56:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
jsx-a11y(prefer-tag-over-role):
apps/landing/src/components/Footer/index.tsx#L25
apps/landing/src/components/Footer/index.tsx:25:11: Prefer `img` over `role` attribute `img`.
|
|
jsx-a11y(prefer-tag-over-role):
apps/landing/src/components/Footer/index.tsx#L16
apps/landing/src/components/Footer/index.tsx:16:7: Prefer `footer` over `role` attribute `contentinfo`.
|
|
react(set-state-in-effect):
apps/landing/src/components/Header/Pages.tsx#L15
apps/landing/src/components/Header/Pages.tsx:15:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
apps/landing/src/components/Header/MobileMenu.tsx#L25
apps/landing/src/components/Header/MobileMenu.tsx:25:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
apps/landing/src/components/home/HomePopup.tsx#L17
apps/landing/src/components/home/HomePopup.tsx:17:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
apps/landing/src/components/test-case/TestCaseResults.tsx#L56
apps/landing/src/components/test-case/TestCaseResults.tsx:56:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
apps/landing/src/components/Header/Pages.tsx#L15
apps/landing/src/components/Header/Pages.tsx:15:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
jsx-a11y(prefer-tag-over-role):
apps/landing/src/components/Footer/index.tsx#L25
apps/landing/src/components/Footer/index.tsx:25:11: Prefer `img` over `role` attribute `img`.
|
|
jsx-a11y(prefer-tag-over-role):
apps/landing/src/components/Footer/index.tsx#L16
apps/landing/src/components/Footer/index.tsx:16:7: Prefer `footer` over `role` attribute `contentinfo`.
|
|
react(set-state-in-effect):
apps/landing/src/components/Header/MobileMenu.tsx#L25
apps/landing/src/components/Header/MobileMenu.tsx:25:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
apps/landing/src/components/home/HomePopup.tsx#L17
apps/landing/src/components/home/HomePopup.tsx:17:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
apps/landing/src/components/test-case/TestCaseResults.tsx#L56
apps/landing/src/components/test-case/TestCaseResults.tsx:56:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
apps/landing/src/components/home/HomePopup.tsx#L17
apps/landing/src/components/home/HomePopup.tsx:17:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
jsx-a11y(prefer-tag-over-role):
apps/landing/src/components/Footer/index.tsx#L25
apps/landing/src/components/Footer/index.tsx:25:11: Prefer `img` over `role` attribute `img`.
|
|
jsx-a11y(prefer-tag-over-role):
apps/landing/src/components/Footer/index.tsx#L16
apps/landing/src/components/Footer/index.tsx:16:7: Prefer `footer` over `role` attribute `contentinfo`.
|
|
react(set-state-in-effect):
apps/landing/src/components/Header/Pages.tsx#L15
apps/landing/src/components/Header/Pages.tsx:15:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
apps/landing/src/components/test-case/TestCaseResults.tsx#L56
apps/landing/src/components/test-case/TestCaseResults.tsx:56:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
apps/landing/src/components/Header/MobileMenu.tsx#L25
apps/landing/src/components/Header/MobileMenu.tsx:25:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
apps/landing/src/components/Header/Pages.tsx#L15
apps/landing/src/components/Header/Pages.tsx:15:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
jsx-a11y(prefer-tag-over-role):
apps/landing/src/components/Footer/index.tsx#L25
apps/landing/src/components/Footer/index.tsx:25:11: Prefer `img` over `role` attribute `img`.
|
|
jsx-a11y(prefer-tag-over-role):
apps/landing/src/components/Footer/index.tsx#L16
apps/landing/src/components/Footer/index.tsx:16:7: Prefer `footer` over `role` attribute `contentinfo`.
|
|
react(set-state-in-effect):
apps/landing/src/components/Header/MobileMenu.tsx#L25
apps/landing/src/components/Header/MobileMenu.tsx:25:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
apps/landing/src/components/home/HomePopup.tsx#L17
apps/landing/src/components/home/HomePopup.tsx:17:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
apps/landing/src/components/test-case/TestCaseResults.tsx#L56
apps/landing/src/components/test-case/TestCaseResults.tsx:56:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
apps/landing/src/components/home/HomePopup.tsx#L17
apps/landing/src/components/home/HomePopup.tsx:17:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
jsx-a11y(prefer-tag-over-role):
apps/landing/src/components/Footer/index.tsx#L25
apps/landing/src/components/Footer/index.tsx:25:11: Prefer `img` over `role` attribute `img`.
|
|
jsx-a11y(prefer-tag-over-role):
apps/landing/src/components/Footer/index.tsx#L16
apps/landing/src/components/Footer/index.tsx:16:7: Prefer `footer` over `role` attribute `contentinfo`.
|
|
react(set-state-in-effect):
apps/landing/src/components/Header/Pages.tsx#L15
apps/landing/src/components/Header/Pages.tsx:15:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
apps/landing/src/components/test-case/TestCaseResults.tsx#L56
apps/landing/src/components/test-case/TestCaseResults.tsx:56:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
apps/landing/src/components/Header/MobileMenu.tsx#L25
apps/landing/src/components/Header/MobileMenu.tsx:25:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
apps/landing/src/components/home/HomePopup.tsx#L17
apps/landing/src/components/home/HomePopup.tsx:17:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
apps/landing/src/components/Header/Pages.tsx#L15
apps/landing/src/components/Header/Pages.tsx:15:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
jsx-a11y(prefer-tag-over-role):
apps/landing/src/components/Footer/index.tsx#L25
apps/landing/src/components/Footer/index.tsx:25:11: Prefer `img` over `role` attribute `img`.
|
|
jsx-a11y(prefer-tag-over-role):
apps/landing/src/components/Footer/index.tsx#L16
apps/landing/src/components/Footer/index.tsx:16:7: Prefer `footer` over `role` attribute `contentinfo`.
|
|
react(set-state-in-effect):
apps/landing/src/components/test-case/TestCaseResults.tsx#L56
apps/landing/src/components/test-case/TestCaseResults.tsx:56:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
apps/landing/src/components/Header/MobileMenu.tsx#L25
apps/landing/src/components/Header/MobileMenu.tsx:25:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
Test (3.14, windows-latest)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: ilammy/msvc-dev-cmd@v1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
jsx-a11y(prefer-tag-over-role):
apps/landing/src/components/Footer/index.tsx#L25
apps/landing/src/components/Footer/index.tsx:25:11: Prefer `img` over `role` attribute `img`.
|
|
jsx-a11y(prefer-tag-over-role):
apps/landing/src/components/Footer/index.tsx#L16
apps/landing/src/components/Footer/index.tsx:16:7: Prefer `footer` over `role` attribute `contentinfo`.
|
|
react(set-state-in-effect):
apps/landing/src/components/Header/Pages.tsx#L15
apps/landing/src/components/Header/Pages.tsx:15:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
apps/landing/src/components/Header/MobileMenu.tsx#L25
apps/landing/src/components/Header/MobileMenu.tsx:25:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
apps/landing/src/components/home/HomePopup.tsx#L17
apps/landing/src/components/home/HomePopup.tsx:17:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
apps/landing/src/components/test-case/TestCaseResults.tsx#L56
apps/landing/src/components/test-case/TestCaseResults.tsx:56:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
apps/landing/src/components/Header/MobileMenu.tsx#L25
apps/landing/src/components/Header/MobileMenu.tsx:25:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
apps/landing/src/components/home/HomePopup.tsx#L17
apps/landing/src/components/home/HomePopup.tsx:17:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
jsx-a11y(prefer-tag-over-role):
apps/landing/src/components/Footer/index.tsx#L25
apps/landing/src/components/Footer/index.tsx:25:11: Prefer `img` over `role` attribute `img`.
|
|
jsx-a11y(prefer-tag-over-role):
apps/landing/src/components/Footer/index.tsx#L16
apps/landing/src/components/Footer/index.tsx:16:7: Prefer `footer` over `role` attribute `contentinfo`.
|
|
react(set-state-in-effect):
apps/landing/src/components/Header/Pages.tsx#L15
apps/landing/src/components/Header/Pages.tsx:15:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
apps/landing/src/components/test-case/TestCaseResults.tsx#L56
apps/landing/src/components/test-case/TestCaseResults.tsx:56:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
Test (3.13, windows-latest)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: ilammy/msvc-dev-cmd@v1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
react(set-state-in-effect):
apps/landing/src/components/Header/Pages.tsx#L15
apps/landing/src/components/Header/Pages.tsx:15:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
jsx-a11y(prefer-tag-over-role):
apps/landing/src/components/Footer/index.tsx#L25
apps/landing/src/components/Footer/index.tsx:25:11: Prefer `img` over `role` attribute `img`.
|
|
jsx-a11y(prefer-tag-over-role):
apps/landing/src/components/Footer/index.tsx#L16
apps/landing/src/components/Footer/index.tsx:16:7: Prefer `footer` over `role` attribute `contentinfo`.
|
|
react(set-state-in-effect):
apps/landing/src/components/Header/MobileMenu.tsx#L25
apps/landing/src/components/Header/MobileMenu.tsx:25:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
apps/landing/src/components/home/HomePopup.tsx#L17
apps/landing/src/components/home/HomePopup.tsx:17:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
apps/landing/src/components/test-case/TestCaseResults.tsx#L56
apps/landing/src/components/test-case/TestCaseResults.tsx:56:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
Test (3.11, windows-latest)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: ilammy/msvc-dev-cmd@v1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
jsx-a11y(prefer-tag-over-role):
apps/landing/src/components/Footer/index.tsx#L25
apps/landing/src/components/Footer/index.tsx:25:11: Prefer `img` over `role` attribute `img`.
|
|
jsx-a11y(prefer-tag-over-role):
apps/landing/src/components/Footer/index.tsx#L16
apps/landing/src/components/Footer/index.tsx:16:7: Prefer `footer` over `role` attribute `contentinfo`.
|
|
react(set-state-in-effect):
apps/landing/src/components/Header/Pages.tsx#L15
apps/landing/src/components/Header/Pages.tsx:15:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
apps/landing/src/components/Header/MobileMenu.tsx#L25
apps/landing/src/components/Header/MobileMenu.tsx:25:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
apps/landing/src/components/home/HomePopup.tsx#L17
apps/landing/src/components/home/HomePopup.tsx:17:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
apps/landing/src/components/test-case/TestCaseResults.tsx#L56
apps/landing/src/components/test-case/TestCaseResults.tsx:56:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
Test (3.12, windows-latest)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: ilammy/msvc-dev-cmd@v1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
react(set-state-in-effect):
apps/landing/src/components/Header/Pages.tsx#L15
apps/landing/src/components/Header/Pages.tsx:15:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
jsx-a11y(prefer-tag-over-role):
apps/landing/src/components/Footer/index.tsx#L25
apps/landing/src/components/Footer/index.tsx:25:11: Prefer `img` over `role` attribute `img`.
|
|
jsx-a11y(prefer-tag-over-role):
apps/landing/src/components/Footer/index.tsx#L16
apps/landing/src/components/Footer/index.tsx:16:7: Prefer `footer` over `role` attribute `contentinfo`.
|
|
react(set-state-in-effect):
apps/landing/src/components/Header/MobileMenu.tsx#L25
apps/landing/src/components/Header/MobileMenu.tsx:25:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
apps/landing/src/components/home/HomePopup.tsx#L17
apps/landing/src/components/home/HomePopup.tsx:17:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
apps/landing/src/components/test-case/TestCaseResults.tsx#L56
apps/landing/src/components/test-case/TestCaseResults.tsx:56:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
Go Test - linux-amd64
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
|
|
.NET Test - linux-x64
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
|
|
Ruby Test - ubuntu-latest
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
|
|
Test (3.14, ubuntu-latest)
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
|
|
Test (3.13, ubuntu-latest)
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
|
|
Test (3.11, ubuntu-latest)
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
|
|
Test (3.12, ubuntu-latest)
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
|
|
changepacks
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
|