Skip to content

chore(deps): update astral-sh/setup-uv action to v6.3.1 #50

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jun 19, 2025

This PR contains the following updates:

Package Type Update Change
astral-sh/setup-uv action patch v6.3.0 -> v6.3.1

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

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

v6.3.1: 🌈 Do not warn when version not in manifest-file

Compare Source

Changes

This is a hotfix to change the warning messages that a version could not be found in the local manifest-file to info level.

A setup-uv release contains a version-manifest.json file with infos in all available uv releases. When a new uv version is released this is not contained in this file until the file gets updated and a new setup-uv release is made.
We will overhaul this process in the future but for now the spamming of warnings is removed.

🐛 Bug fixes

🧰 Maintenance


Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, 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.

@codecov-commenter
Copy link

codecov-commenter commented Jun 19, 2025

❌ 1 Tests Failed:

Tests completed Failed Passed Skipped
284 1 283 10
View the full list of 1 ❄️ flaky tests
tests.aignostics.application.gui_test::test_gui_index

Flake rate in main: 25.93% (Passed 20 times, Failed 7 times)

Stack Traces | 3.9s run time
There were unexpected ERROR logs.

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 force-pushed the renovate/astral-sh-setup-uv-6.x branch from e3cc4f6 to 03c455f Compare June 20, 2025 05:50
@renovate renovate bot changed the title chore(deps): update astral-sh/setup-uv action to v6.2.1 chore(deps): update astral-sh/setup-uv action to v6.3.0 Jun 20, 2025
@renovate renovate bot changed the title chore(deps): update astral-sh/setup-uv action to v6.3.0 chore(deps): update astral-sh/setup-uv action to v6.3.0 - autoclosed Jun 24, 2025
@renovate renovate bot closed this Jun 24, 2025
@renovate renovate bot changed the title chore(deps): update astral-sh/setup-uv action to v6.3.0 - autoclosed chore(deps): update astral-sh/setup-uv action to v6.3.0 Jun 25, 2025
@renovate renovate bot reopened this Jun 25, 2025
@renovate renovate bot force-pushed the renovate/astral-sh-setup-uv-6.x branch from 76084c9 to 03c455f Compare June 25, 2025 16:07
@renovate renovate bot changed the title chore(deps): update astral-sh/setup-uv action to v6.3.0 chore(deps): update astral-sh/setup-uv action to v6.3.1 Jun 25, 2025
@renovate renovate bot force-pushed the renovate/astral-sh-setup-uv-6.x branch from 03c455f to 4be6597 Compare June 25, 2025 17:56
Copy link

Copy link
Author

renovate bot commented Jun 27, 2025

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants