repos/webexmemebot
4
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Releases 46 Activity

chore(deps): lock file maintenance #485

Closed
renovate-bot wants to merge 1 commits from renovate/lock-file-maintenance into main
pull from: renovate/lock-file-maintenance
merge into: repos:main
Conversation 1 Commits 1 Files Changed 1 +268 -267
renovate-bot commented 2025-05-12 02:49:27 +02:00
Member
Copy Link

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

🔧 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.

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

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Update | Change | |---|---| | lockFileMaintenance | All locks refreshed | 🔧 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](https://github.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MC44LjIiLCJ1cGRhdGVkSW5WZXIiOiI0MC44LjIiLCJ0YXJnZXRCcmFuY2giOiJtYWluIiwibGFiZWxzIjpbInR5cGUvZGVwZW5kZW5jaWVzIl19-->
renovate-bot added the
type
dependencies
 label 2025-05-12 02:49:27 +02:00
renovate-bot added 1 commit 2025-05-12 02:49:32 +02:00
chore(deps): lock file maintenance
Some checks failed
Enforce Conventional Commit PR Title / Validate PR Title (pull_request_target) Successful in 17s
Details
CI / ci (pull_request) Failing after 1m0s
Details
2b06839924
renovate-bot requested review from luke 2025-05-12 02:49:33 +02:00
renovate-bot force-pushed renovate/lock-file-maintenance from 2b06839924 to 41a3d7a981 2025-06-06 19:39:00 +02:00 Compare
renovate-bot force-pushed renovate/lock-file-maintenance from 41a3d7a981 to f90a653ac7 2025-06-06 20:02:53 +02:00 Compare
ai-review-bot commented 2025-06-06 20:02:59 +02:00
Member
Copy Link

Decision: Reject
Change Score: 2/10

These changes to uv.lock introduce several concerning aspects:

  1. Upload Times in the Future: The upload-time metadata for several packages (e.g., astroid, black, certifi) are dated in the future (2025). This is HIGHLY SUSPICIOUS and suggests that these packages are not genuine releases from PyPI, or that some process is injecting bogus metadata.

  2. Revision Increase: The revision = 2 bump without a clear justification is concerning. What warranted this revision bump? There is no explanation.

  3. Python Version Locking: While updating the requires-python is acceptable if you've verified compatibility, please keep in mind that a check of your dependencies may be required.

I cannot accept these changes due to the potential security risks associated with future dated packages, and also due to the lack of clear reasoning.

I would propose you examine and resolve these issues, then resubmit your changes.

**Decision: Reject** **Change Score: 2/10** These changes to `uv.lock` introduce several concerning aspects: 1. **Upload Times in the Future:** The `upload-time` metadata for several packages (e.g., astroid, black, certifi) are dated in the future (2025). This is HIGHLY SUSPICIOUS and suggests that these packages are not genuine releases from PyPI, or that some process is injecting bogus metadata. 2. **Revision Increase:** The `revision = 2` bump without a clear justification is concerning. What warranted this revision bump? There is no explanation. 3. **Python Version Locking:** While updating the `requires-python` is acceptable if you've verified compatibility, please keep in mind that a check of your dependencies may be required. I cannot accept these changes due to the potential security risks associated with future dated packages, and also due to the lack of clear reasoning. I would propose you examine and resolve these issues, then resubmit your changes.
luke closed this pull request 2025-06-06 20:58:55 +02:00
All checks were successful
Enforce Conventional Commit PR Title / Validate PR Title (pull_request_target) Successful in 5s
Required
Details
CI / ci (pull_request) Successful in 1m8s
Required
Details

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No Reviewers
luke
Labels
Clear labels
blocked
bug
Something isn't working
dependencies
documentation
Improvements or additions to documentation
duplicate
This issue or pull request already exists
enhancement
New feature or request
good first issue
Good for newcomers
help wanted
Extra attention is needed
invalid
This doesn't seem right
linting
question
Further information is requested
security
type
bugfix
type
dependencies
type
feature
type
other
unit-tests
wontfix
This will not be worked on
Compat/Breaking
Breaking change that won't be backward compatible
Kind/Bug
Something is not working
Kind/Documentation
Documentation changes
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/Security
This is security issue
Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
No Label
type
dependencies
Milestone
No items
No Milestone
Assignees
Clear assignees
ai-review-bot gitea-actions-bot luke renovate-bot
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: repos/webexmemebot#485
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?