Skip to content

update-constraints: Use latest version if multiple indices used #35

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.

Sign up for GitHub

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

Merged
courtneypacheco merged 1 commit into from
Jun 18, 2025
Merged

update-constraints: Use latest version if multiple indices used #35

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions actions/update-constraints/generate_constraints.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,14 +7,13 @@ if [ "$(uname)" != "Linux" ]; then
exit 1
fi

# If we run from tox, ignore the index url
unset PIP_EXTRA_INDEX_URL

# Read list of requirements files from the config file
REQUIREMENTS_FILES=$(grep -v '^#' requirements-files.in | tr '\n' ' ')

CONSTRAINTS_FILE=constraints-dev.txt

export UV_INDEX_STRATEGY=unsafe-best-match
Copy link
Contributor Author

@booxter booxter Jun 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's called unsafe because there's an attack vector: https://docs.astral.sh/uv/concepts/indexes/#searching-across-multiple-indexes but it applies to any pip runs. Since we use pip anyway, it doesn't seem to make it any worse than status quo.


# shellcheck disable=SC2086
uv pip compile -U \
--no-header \
Expand Down
Loading