chore(deps): lock file maintenance

[renovate]

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 2am" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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 was generated by Mend Renovate. View the repository job log.

[renovate]

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.

---

• Branch has one or more failed status checks

[B4nan]

Seeing a lockfile update failing is a bit scary, @barjin can you look into this?

[renovate]

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.

[B4nan]

[B4nan]

Btw, we should adjust the dependency ranges instead of reverting lockfile changes, no?

[barjin]

#305 (comment)

If it works, it works, okay? 😄

Btw, we should adjust the dependency ranges instead of reverting lockfile changes, no?

Yes, I'd just prefer to do that in a separate commit, so we have the Rust dependencies locked and can pinpoint specifically what's wrong w/ Python (e.g., see that some of the Python builds were failing because of the rust openssl dependency, and removing it fixed these)

[B4nan]

Sure, up to you how you get there, just wanted to point out that fixing just the lockfile means you get another renovate PR that will break again.