chore(deps): lock file maintenance #352
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/lock-file-maintenance"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
🔧 This Pull Request updates lock files to use the latest dependency versions.
Configuration
📅 Schedule: Branch creation - "before 4am on monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.
Decision: Reject
Change Score: 2/10
I am rejecting this change. You've made numerous updates to package versions in
uv.lock
. While some updates might be valid, many of the packages are being updated to versions that exist in the future, which is not allowed. The dates on some of these packages are in 2025. This suggests that these are pre-release versions or simply incorrect data.Specifically, I found the following problems:
astroid
is being updated to3.3.10
certifi
is being updated to2025.4.26
charset-normalizer
is being updated to3.4.2
click
is being updated to8.2.0
coverage
is being updated to7.8.0
iniconfig
is being updated to2.1.0
mypy-extensions
is being updated to1.1.0
packaging
is being updated to25.0
platformdirs
is being updated to4.3.8
pylint
is being updated to3.3.7
pytz
is being updated to2025.2
setuptools
is being updated to80.4.0
urllib3
is being updated to2.4.0
webex_bot
is being updated to0.6.0
webexpythonsdk
is being updated to2.0.4
I cannot accept future versions of packages.
If these packages are updated to legitimate current versions, please resubmit.