Add the polars mapping file. #74
Annotations
42 warnings and 14 notices
test (ubuntu-latest, 3.12)
No file matched to [/home/runner/work/pyref.dev/pyref.dev/**/*requirements*.txt,/home/runner/work/pyref.dev/pyref.dev/**/*requirements*.in,/home/runner/work/pyref.dev/pyref.dev/**/*constraints*.txt,/home/runner/work/pyref.dev/pyref.dev/**/*constraints*.in,/home/runner/work/pyref.dev/pyref.dev/**/pyproject.toml,/home/runner/work/pyref.dev/pyref.dev/**/uv.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
test (ubuntu-latest, 3.12)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
test (ubuntu-latest, 3.13t)
No file matched to [/home/runner/work/pyref.dev/pyref.dev/**/*requirements*.txt,/home/runner/work/pyref.dev/pyref.dev/**/*requirements*.in,/home/runner/work/pyref.dev/pyref.dev/**/*constraints*.txt,/home/runner/work/pyref.dev/pyref.dev/**/*constraints*.in,/home/runner/work/pyref.dev/pyref.dev/**/pyproject.toml,/home/runner/work/pyref.dev/pyref.dev/**/uv.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
test (ubuntu-latest, 3.13t)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
test (ubuntu-latest, 3.10)
No file matched to [/home/runner/work/pyref.dev/pyref.dev/**/*requirements*.txt,/home/runner/work/pyref.dev/pyref.dev/**/*requirements*.in,/home/runner/work/pyref.dev/pyref.dev/**/*constraints*.txt,/home/runner/work/pyref.dev/pyref.dev/**/*constraints*.in,/home/runner/work/pyref.dev/pyref.dev/**/pyproject.toml,/home/runner/work/pyref.dev/pyref.dev/**/uv.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
test (ubuntu-latest, 3.10)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
test (ubuntu-latest, 3.11)
No file matched to [/home/runner/work/pyref.dev/pyref.dev/**/*requirements*.txt,/home/runner/work/pyref.dev/pyref.dev/**/*requirements*.in,/home/runner/work/pyref.dev/pyref.dev/**/*constraints*.txt,/home/runner/work/pyref.dev/pyref.dev/**/*constraints*.in,/home/runner/work/pyref.dev/pyref.dev/**/pyproject.toml,/home/runner/work/pyref.dev/pyref.dev/**/uv.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
test (ubuntu-latest, 3.11)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
test (ubuntu-latest, 3.14)
No file matched to [/home/runner/work/pyref.dev/pyref.dev/**/*requirements*.txt,/home/runner/work/pyref.dev/pyref.dev/**/*requirements*.in,/home/runner/work/pyref.dev/pyref.dev/**/*constraints*.txt,/home/runner/work/pyref.dev/pyref.dev/**/*constraints*.in,/home/runner/work/pyref.dev/pyref.dev/**/pyproject.toml,/home/runner/work/pyref.dev/pyref.dev/**/uv.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
test (ubuntu-latest, 3.14)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
test (ubuntu-latest, 3.13)
No file matched to [/home/runner/work/pyref.dev/pyref.dev/**/*requirements*.txt,/home/runner/work/pyref.dev/pyref.dev/**/*requirements*.in,/home/runner/work/pyref.dev/pyref.dev/**/*constraints*.txt,/home/runner/work/pyref.dev/pyref.dev/**/*constraints*.in,/home/runner/work/pyref.dev/pyref.dev/**/pyproject.toml,/home/runner/work/pyref.dev/pyref.dev/**/uv.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
test (ubuntu-latest, 3.13)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
test (macos-latest, 3.12)
No file matched to [/Users/runner/work/pyref.dev/pyref.dev/**/*requirements*.txt,/Users/runner/work/pyref.dev/pyref.dev/**/*requirements*.in,/Users/runner/work/pyref.dev/pyref.dev/**/*constraints*.txt,/Users/runner/work/pyref.dev/pyref.dev/**/*constraints*.in,/Users/runner/work/pyref.dev/pyref.dev/**/pyproject.toml,/Users/runner/work/pyref.dev/pyref.dev/**/uv.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
test (macos-latest, 3.12)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
test (ubuntu-latest, 3.14t)
No file matched to [/home/runner/work/pyref.dev/pyref.dev/**/*requirements*.txt,/home/runner/work/pyref.dev/pyref.dev/**/*requirements*.in,/home/runner/work/pyref.dev/pyref.dev/**/*constraints*.txt,/home/runner/work/pyref.dev/pyref.dev/**/*constraints*.in,/home/runner/work/pyref.dev/pyref.dev/**/pyproject.toml,/home/runner/work/pyref.dev/pyref.dev/**/uv.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
test (ubuntu-latest, 3.14t)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
test (macos-latest, 3.14)
No file matched to [/Users/runner/work/pyref.dev/pyref.dev/**/*requirements*.txt,/Users/runner/work/pyref.dev/pyref.dev/**/*requirements*.in,/Users/runner/work/pyref.dev/pyref.dev/**/*constraints*.txt,/Users/runner/work/pyref.dev/pyref.dev/**/*constraints*.in,/Users/runner/work/pyref.dev/pyref.dev/**/pyproject.toml,/Users/runner/work/pyref.dev/pyref.dev/**/uv.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
test (macos-latest, 3.14)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
test (macos-latest, 3.10)
No file matched to [/Users/runner/work/pyref.dev/pyref.dev/**/*requirements*.txt,/Users/runner/work/pyref.dev/pyref.dev/**/*requirements*.in,/Users/runner/work/pyref.dev/pyref.dev/**/*constraints*.txt,/Users/runner/work/pyref.dev/pyref.dev/**/*constraints*.in,/Users/runner/work/pyref.dev/pyref.dev/**/pyproject.toml,/Users/runner/work/pyref.dev/pyref.dev/**/uv.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
test (macos-latest, 3.10)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
test (macos-latest, 3.13)
No file matched to [/Users/runner/work/pyref.dev/pyref.dev/**/*requirements*.txt,/Users/runner/work/pyref.dev/pyref.dev/**/*requirements*.in,/Users/runner/work/pyref.dev/pyref.dev/**/*constraints*.txt,/Users/runner/work/pyref.dev/pyref.dev/**/*constraints*.in,/Users/runner/work/pyref.dev/pyref.dev/**/pyproject.toml,/Users/runner/work/pyref.dev/pyref.dev/**/uv.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
test (macos-latest, 3.13)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
test (windows-latest, 3.11)
No file matched to [D:\a\pyref.dev\pyref.dev\**/*requirements*.txt,D:\a\pyref.dev\pyref.dev\**/*requirements*.in,D:\a\pyref.dev\pyref.dev\**/*constraints*.txt,D:\a\pyref.dev\pyref.dev\**/*constraints*.in,D:\a\pyref.dev\pyref.dev\**/pyproject.toml,D:\a\pyref.dev\pyref.dev\**/uv.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
test (windows-latest, 3.11)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
test (windows-latest, 3.13)
No file matched to [D:\a\pyref.dev\pyref.dev\**/*requirements*.txt,D:\a\pyref.dev\pyref.dev\**/*requirements*.in,D:\a\pyref.dev\pyref.dev\**/*constraints*.txt,D:\a\pyref.dev\pyref.dev\**/*constraints*.in,D:\a\pyref.dev\pyref.dev\**/pyproject.toml,D:\a\pyref.dev\pyref.dev\**/uv.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
test (windows-latest, 3.13)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
test (windows-latest, 3.14)
No file matched to [D:\a\pyref.dev\pyref.dev\**/*requirements*.txt,D:\a\pyref.dev\pyref.dev\**/*requirements*.in,D:\a\pyref.dev\pyref.dev\**/*constraints*.txt,D:\a\pyref.dev\pyref.dev\**/*constraints*.in,D:\a\pyref.dev\pyref.dev\**/pyproject.toml,D:\a\pyref.dev\pyref.dev\**/uv.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
test (windows-latest, 3.14)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
test (windows-latest, 3.10)
No file matched to [D:\a\pyref.dev\pyref.dev\**/*requirements*.txt,D:\a\pyref.dev\pyref.dev\**/*requirements*.in,D:\a\pyref.dev\pyref.dev\**/*constraints*.txt,D:\a\pyref.dev\pyref.dev\**/*constraints*.in,D:\a\pyref.dev\pyref.dev\**/pyproject.toml,D:\a\pyref.dev\pyref.dev\**/uv.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
test (windows-latest, 3.10)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
test (macos-latest, 3.13t)
No file matched to [/Users/runner/work/pyref.dev/pyref.dev/**/*requirements*.txt,/Users/runner/work/pyref.dev/pyref.dev/**/*requirements*.in,/Users/runner/work/pyref.dev/pyref.dev/**/*constraints*.txt,/Users/runner/work/pyref.dev/pyref.dev/**/*constraints*.in,/Users/runner/work/pyref.dev/pyref.dev/**/pyproject.toml,/Users/runner/work/pyref.dev/pyref.dev/**/uv.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
test (macos-latest, 3.13t)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
test (windows-latest, 3.13t)
No file matched to [D:\a\pyref.dev\pyref.dev\**/*requirements*.txt,D:\a\pyref.dev\pyref.dev\**/*requirements*.in,D:\a\pyref.dev\pyref.dev\**/*constraints*.txt,D:\a\pyref.dev\pyref.dev\**/*constraints*.in,D:\a\pyref.dev\pyref.dev\**/pyproject.toml,D:\a\pyref.dev\pyref.dev\**/uv.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
test (windows-latest, 3.13t)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
test (windows-latest, 3.14t)
No file matched to [D:\a\pyref.dev\pyref.dev\**/*requirements*.txt,D:\a\pyref.dev\pyref.dev\**/*requirements*.in,D:\a\pyref.dev\pyref.dev\**/*constraints*.txt,D:\a\pyref.dev\pyref.dev\**/*constraints*.in,D:\a\pyref.dev\pyref.dev\**/pyproject.toml,D:\a\pyref.dev\pyref.dev\**/uv.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
test (windows-latest, 3.14t)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
test (macos-latest, 3.11)
No file matched to [/Users/runner/work/pyref.dev/pyref.dev/**/*requirements*.txt,/Users/runner/work/pyref.dev/pyref.dev/**/*requirements*.in,/Users/runner/work/pyref.dev/pyref.dev/**/*constraints*.txt,/Users/runner/work/pyref.dev/pyref.dev/**/*constraints*.in,/Users/runner/work/pyref.dev/pyref.dev/**/pyproject.toml,/Users/runner/work/pyref.dev/pyref.dev/**/uv.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
test (macos-latest, 3.11)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
test (macos-latest, 3.14t)
No file matched to [/Users/runner/work/pyref.dev/pyref.dev/**/*requirements*.txt,/Users/runner/work/pyref.dev/pyref.dev/**/*requirements*.in,/Users/runner/work/pyref.dev/pyref.dev/**/*constraints*.txt,/Users/runner/work/pyref.dev/pyref.dev/**/*constraints*.in,/Users/runner/work/pyref.dev/pyref.dev/**/pyproject.toml,/Users/runner/work/pyref.dev/pyref.dev/**/uv.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
test (macos-latest, 3.14t)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
test (windows-latest, 3.12)
No file matched to [D:\a\pyref.dev\pyref.dev\**/*requirements*.txt,D:\a\pyref.dev\pyref.dev\**/*requirements*.in,D:\a\pyref.dev\pyref.dev\**/*constraints*.txt,D:\a\pyref.dev\pyref.dev\**/*constraints*.in,D:\a\pyref.dev\pyref.dev\**/pyproject.toml,D:\a\pyref.dev\pyref.dev\**/uv.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
test (windows-latest, 3.12)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
|
test (macos-latest, 3.12)
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
test (macos-latest, 3.14)
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
test (macos-latest, 3.10)
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
test (macos-latest, 3.13)
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
test (windows-latest, 3.11)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
test (windows-latest, 3.13)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
test (windows-latest, 3.14)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
test (windows-latest, 3.10)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
test (macos-latest, 3.13t)
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
test (windows-latest, 3.13t)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
test (windows-latest, 3.14t)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
test (macos-latest, 3.11)
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
test (macos-latest, 3.14t)
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
|
test (windows-latest, 3.12)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|