Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 26, 2025

This PR contains the following updates:

Package Type Update Change
astral-sh/setup-uv action minor v7.1.1v7.2.1

Release Notes

astral-sh/setup-uv (astral-sh/setup-uv)

v7.2.1

Compare Source

v7.2.0: 🌈 add outputs python-version and python-cache-hit

Compare Source

Changes

Among some minor typo fixes and quality of life features for developers of actions the main feature of this release are new outputs:

  • python-version: The Python version that was set (same content as existing UV_PYTHON)
  • python-cache-hit: A boolean value to indicate the Python cache entry was found

While implementing this it became clear, that it is easier to handle the Python binaries in a separate cache entry. The added benefit for users is that the "normal" cache containing the dependencies can be used in all runs no matter if these cache the Python binaries or not.

[!NOTE]
This release will invalidate caches that contain the Python binaries. This happens a single time.

🐛 Bug fixes
  • chore: remove stray space from UV_PYTHON_INSTALL_DIR message @​akx (#​720)
🚀 Enhancements
🧰 Maintenance
⬆️ Dependency updates

v7.1.6: 🌈 add OS version to cache key to prevent binary incompatibility

Compare Source

Changes

This release will invalidate your cache existing keys!

The os version e.g. ubuntu-22.04 is now part of the cache key. This prevents failing builds when a cache got populated with wheels built with different tools (e.g. glibc) than are present on the runner where the cache got restored.

🐛 Bug fixes
🧰 Maintenance
⬆️ Dependency updates

v7.1.5: 🌈 allow setting cache-local-path without enable-cache: true

Compare Source

Changes

#​612 fixed a faulty behavior where this action set UV_CACHE_DIR even though enable-cache was false. It also fixed the cases were the cache dir is already configured in a settings file like pyproject.toml or UV_CACHE_DIR was already set. Here the action shouldn't overwrite or set UV_CACHE_DIR.

These fixes introduced an unwanted behavior: You can still set cache-local-path but this action didn't do anything. This release fixes that.

You can now use cache-local-path to automatically set UV_CACHE_DIR even when enable-cache is false (or gets set to false by default e.g. on self-hosted runners)

- name: This is now possible
  uses: astral-sh/setup-uv@v7
  with:
    enable-cache: false
    cache-local-path: "/path/to/cache"
🐛 Bug fixes
🧰 Maintenance
⬆️ Dependency updates

v7.1.4: 🌈 Fix libuv closing bug on Windows

Compare Source

Changes

This release fixes the bug Assertion failed: !(handle->flags & UV_HANDLE_CLOSING) on Windows runners

🐛 Bug fixes
🧰 Maintenance

v7.1.3: 🌈 Support act

Compare Source

Changes

This bug fix release adds support for https://github.com/nektos/act
It was previously broken because of a too new undici version and TS transpilation target.

Compatibility with act is now automatically tested.

🐛 Bug fixes
🧰 Maintenance
📚 Documentation

v7.1.2: 🌈 Speed up extraction on Windows

Compare Source

Changes

@​lazka fixed a bug that caused extracting uv to take up to 30s. Thank you!

🐛 Bug fixes

🧰 Maintenance

⬆️ Dependency updates


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot enabled auto-merge (squash) October 26, 2025 17:13
renovate-approve[bot]
renovate-approve bot previously approved these changes Oct 26, 2025
@codecov
Copy link

codecov bot commented Oct 26, 2025

❌ 1 Tests Failed:

Tests completed Failed Passed Skipped
105 1 104 16
View the top 1 failed test(s) by shortest run time
tests\test_ruleset.py::test_ruleset::test_solve_total_value[HIGHS]
Stack Traces | 0.069s run time
ruleset = RuleSet(numbers=13, repeats=2, colours=4, jokers=2, min_len=3, min_initial_value=30, solver_backend=<MILPSolver.HIGHS: 'HIGHS'>)
in_progress_game = <GameState([... 53 tiles ...], table=(<Black 1 (1)>, <Black 2 (2)>, <Black 3 (3)>, <Black 4 (4)>, <Black 5 (5)>, <Blac... 9 (35)>, <Orange 12 (38)>, <Orange 12 (38)>, <Red 2 (41)>, <Red 4 (43)>, <Red 7 (46)>, <Red 12 (51)>), initial=False)>

    #x1B[0m#x1B[94mdef#x1B[39;49;00m#x1B[90m #x1B[39;49;00m#x1B[92mtest_solve_total_value#x1B[39;49;00m(ruleset: RuleSet, in_progress_game: GameState) -> #x1B[94mNone#x1B[39;49;00m:#x1B[90m#x1B[39;49;00m
        in_progress_game.initial = #x1B[94mFalse#x1B[39;49;00m#x1B[90m#x1B[39;49;00m
    #x1B[90m#x1B[39;49;00m
        solution = ruleset.solve(in_progress_game, mode=SolverMode.TOTAL_VALUE)#x1B[90m#x1B[39;49;00m
        #x1B[94massert#x1B[39;49;00m solution #x1B[95mis#x1B[39;49;00m #x1B[95mnot#x1B[39;49;00m #x1B[94mNone#x1B[39;49;00m#x1B[90m#x1B[39;49;00m
    #x1B[90m#x1B[39;49;00m
        #x1B[90m# backends may select different tiles, and differ in their ability to#x1B[39;49;00m#x1B[90m#x1B[39;49;00m
        #x1B[90m# maximize the total tile value, so we can, at best, include known values#x1B[39;49;00m#x1B[90m#x1B[39;49;00m
        #x1B[90m# for different solvers and use this as a range for any others. The exact#x1B[39;49;00m#x1B[90m#x1B[39;49;00m
        #x1B[90m# sets differ based on the tiles selected.#x1B[39;49;00m#x1B[90m#x1B[39;49;00m
        expected_tile_sum = {#x1B[90m#x1B[39;49;00m
            MILPSolver.CBC: #x1B[94m515#x1B[39;49;00m,#x1B[90m#x1B[39;49;00m
            #x1B[90m# MILPSolver.GLPK_MI  is either 515 _or_ 589, depending on the exact version installed.#x1B[39;49;00m#x1B[90m#x1B[39;49;00m
            MILPSolver.SCIPY: #x1B[94m515#x1B[39;49;00m,#x1B[90m#x1B[39;49;00m
            MILPSolver.HIGHS: #x1B[94m589#x1B[39;49;00m,#x1B[90m#x1B[39;49;00m
            MILPSolver.SCIP: #x1B[94m589#x1B[39;49;00m,#x1B[90m#x1B[39;49;00m
        }#x1B[90m#x1B[39;49;00m
        #x1B[94mif#x1B[39;49;00m expected := expected_tile_sum.get(ruleset.backend):#x1B[90m#x1B[39;49;00m
>           #x1B[94massert#x1B[39;49;00m #x1B[96msum#x1B[39;49;00m(solution.tiles) == expected#x1B[90m#x1B[39;49;00m
#x1B[1m#x1B[31mE           assert 515 == 589#x1B[0m
#x1B[1m#x1B[31mE            +  where 515 = sum([<Black 1 (1)>, <Black 3 (3)>, <Black 4 (4)>, <Black 10 (10)>, <Blue 1 (14)>, <Blue 2 (15)>, ...])#x1B[0m
#x1B[1m#x1B[31mE            +    where [<Black 1 (1)>, <Black 3 (3)>, <Black 4 (4)>, <Black 10 (10)>, <Blue 1 (14)>, <Blue 2 (15)>, ...] = ProposedSolution(tiles=[<Black 1 (1)>, <Black 3 (3)>, <Black 4 (4)>, <Black 10 (10)>, <Blue 1 (14)>, <Blue 2 (15)>, <Blue 8 (21)>, <Blue 10 (23)>, <Blue 13 (26)>, <Orange 3 (29)>, <Orange 5 (31)>, <Orange 7 (33)>, <Orange 7 (33)>, <Orange 8 (34)>, <Orange 9 (35)>, <Orange 9 (35)>, <Orange 12 (38)>, <Red 2 (41)>, <Red 4 (43)>, <Red 7 (46)>], sets=[(<Black 1 (1)>, <Black 2 (2)>, <Black 3 (3)>, <Black 4 (4)>), (<Black 1 (1)>, <Blue 1 (14)>, <Joker (53)>), (<Black 3 (3)>, <Blue 3 (16)>, <Orange 3 (29)>), (<Black 4 (4)>, <Blue 4 (17)>, <Red 4 (43)>), (<Black 5 (5)>, <Blue 5 (18)>, <Red 5 (44)>), (<Black 6 (6)>, <Black 7 (7)>, <Black 8 (8)>, <Black 9 (9)>, <Black 10 (10)>), (<Black 13 (13)>, <Blue 13 (26)>, <Red 13 (52)>), (<Blue 2 (15)>, <Orange 2 (28)>, <Red 2 (41)>), (<Blue 5 (18)>, <Blue 6 (19)>, <Blue 7 (20)>, <Blue 8 (21)>), (<Blue 8 (21)>, <Blue 9 (22)>, <Blue 10 (23)>), (<Orange 3 (29)>, <Orange 4 (30)>, <Orange 5 (31)>), (<Orange 7 (33)>, <Orange 8 (34)>, <Orange 9 (35)>), (<Orange 7 (33)>, <Orange 8 (34)>, <Orange 9 (35)>), (<Orange 10 (36)>, <Orange 11 (37)>, <Orange 12 (38)>, <Orange 13 (39)>), (<Red 7 (46)>, <Red 8 (47)>, <Red 9 (48)>, <Red 10 (49)>)], free_jokers=0).tiles#x1B[0m

#x1B[1m#x1B[31mtests\test_ruleset.py#x1B[0m:460: AssertionError

To view more test analytics, go to the Test Analytics Dashboard
📋 Got 3 mins? Take this short survey to help us improve Test Analytics.

@renovate renovate bot changed the title chore(deps): update astral-sh/setup-uv action to v7.1.2 chore(deps): update astral-sh/setup-uv action to v7.1.3 Nov 11, 2025
@renovate renovate bot force-pushed the renovate/astral-sh-setup-uv-7.x branch from a9fda99 to 488e076 Compare November 11, 2025 00:51
renovate-approve[bot]
renovate-approve bot previously approved these changes Nov 11, 2025
@renovate renovate bot changed the title chore(deps): update astral-sh/setup-uv action to v7.1.3 chore(deps): update astral-sh/setup-uv action to v7.1.4 Nov 21, 2025
@renovate renovate bot force-pushed the renovate/astral-sh-setup-uv-7.x branch from 488e076 to 08b9d4a Compare November 21, 2025 09:52
renovate-approve[bot]
renovate-approve bot previously approved these changes Nov 21, 2025
@renovate renovate bot force-pushed the renovate/astral-sh-setup-uv-7.x branch from 08b9d4a to 4df48d5 Compare December 7, 2025 21:39
@renovate renovate bot changed the title chore(deps): update astral-sh/setup-uv action to v7.1.4 chore(deps): update astral-sh/setup-uv action to v7.1.5 Dec 7, 2025
renovate-approve[bot]
renovate-approve bot previously approved these changes Dec 7, 2025
@renovate renovate bot changed the title chore(deps): update astral-sh/setup-uv action to v7.1.5 chore(deps): update astral-sh/setup-uv action to v7.1.6 Dec 13, 2025
@renovate renovate bot force-pushed the renovate/astral-sh-setup-uv-7.x branch from 4df48d5 to 60fb152 Compare December 13, 2025 17:49
renovate-approve[bot]
renovate-approve bot previously approved these changes Dec 13, 2025
@renovate renovate bot force-pushed the renovate/astral-sh-setup-uv-7.x branch from 60fb152 to 62a030f Compare January 6, 2026 18:00
@renovate renovate bot changed the title chore(deps): update astral-sh/setup-uv action to v7.1.6 chore(deps): update astral-sh/setup-uv action to v7.2.0 Jan 6, 2026
renovate-approve[bot]
renovate-approve bot previously approved these changes Jan 6, 2026
@renovate renovate bot changed the title chore(deps): update astral-sh/setup-uv action to v7.2.0 chore(deps): update astral-sh/setup-uv action to v7.2.1 Jan 30, 2026
@sonarqubecloud
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants