search

adamchainz / pip-lock

Check for differences between requirements.txt files and your environment
MIT License
36 stars 7 forks source link

Bump astral-sh/setup-uv from 1 to 3 in the github-actions group #463

Closed dependabot[bot] closed 1 month ago

dependabot[bot] commented 1 month ago

Bumps the github-actions group with 1 update: astral-sh/setup-uv.

Updates astral-sh/setup-uv from 1 to 3

Release notes

Sourced from astral-sh/setup-uv's releases.

v3.1.3 🌈 update known checksums for 0.4.17

Changes

🧰 Maintenance

⬆️ Dependency updates

v3.1.2 🌈 update known checksums for 0.4.16

Changes

🐛 Bug fixes

🧰 Maintenance

⬆️ Dependency updates

v3.1.1 🌈 update known checksums for 0.4.15

Changes

🧰 Maintenance

📚 Documentation

v3.0.0 🌈 Set the cache-dependency-glob default to **/uv.lock

Changes

With this release cache-dependency-glob defaults to **/uv.lock. This is in line with what most users would expect and also mirrors the default behaviors for setup-python which use **/requirements.txt, **/Pipfile.lock or **/poetry.lock.

The previous default led to the cache being created only once and never invalidated or updated even when the dependencies changed.

This change only affects you if you are using enable-cache: true without specifying cache-dependency-glob. The only behavioral change you might see is one time cache miss.

Learn more about cache-dependency-glob in the README section.

... (truncated)

Commits
  • 023eb78 chore: update known checksums for 0.4.17 (#104)
  • 315da29 Bump @​types/node from 22.7.0 to 22.7.3 (#103)
  • 4cda7d7 Bump @​types/node from 22.6.1 to 22.7.0 (#101)
  • 8114e5e chore: update known checksums for 0.4.16 (#100)
  • 7ee921e Bump @​types/node from 22.5.5 to 22.6.1 (#98)
  • 8c3a35e Only log checksum is valid when it really is (#97)
  • abac0ce Use runner label selfhosted-ubuntu-arm64 (#96)
  • 03e245b chore: update known checksums for 0.4.15 (#95)
  • aeb4649 Set tool(-bin) dir and add to PATH (#87)
  • dbb680f chore: update known checksums for 0.4.14 (#94)
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions