10BC0 chore: upgrade uv by joshuarli · Pull Request #107166 · getsentry/sentry · GitHub
[go: up one dir, main page]

Skip to content

Conversation

@joshuarli
Copy link
Member

this'll proactively enable future python upgrades as we're limited to like 3.13.4 on this older uv version

@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Jan 28, 2026
Copy link
Contributor
@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

# used for autoupdate
version = 0.8.2
# NOTE: when bumping, please also update versions for astral-sh/setup-uv github action accordingly
version = 0.9.27
Copy link
Contributor

Choose a reason for hiding this comment

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

Dockerfile uv version not updated, creating inconsistency

Medium Severity

The self-hosted/Dockerfile still pins uv==0.8.2 while all GitHub workflows and devenv/config.ini have been upgraded to 0.9.27. Before this PR, all environments used uv 0.8.2 consistently. After this PR, there's a version mismatch between CI/development (0.9.27) and the 904A production Docker image (0.8.2). This inconsistency could cause subtle differences in dependency resolution behavior between environments. Given the PR's stated goal of enabling future Python upgrades, the Docker image would also need the updated uv version to benefit from this change.

Fix in Cursor Fix in Web

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

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

0