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: (in timezone Etc/UTC)

• Branch creation
  • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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.

[codecov]

❌ 2 Tests Failed:

Tests completed	Failed	Passed	Skipped
2177	2	2175	195

View the top 2 failed test(s) by shortest run time

github.com/PeerDB-io/peerdb/flow/e2e::TestGenericBQ

Stack Traces | 0s run time

=== RUN   TestGenericBQ
=== PAUSE TestGenericBQ
=== CONT  TestGenericBQ
--- FAIL: TestGenericBQ (0.00s)

github.com/PeerDB-io/peerdb/flow/e2e::TestGenericBQ/Test_Simple_Flow

Stack Traces | 33.5s run time

=== RUN   TestGenericBQ/Test_Simple_Flow
=== PAUSE TestGenericBQ/Test_Simple_Flow
=== CONT  TestGenericBQ/Test_Simple_Flow
    generic_test.go:124: UNEXPECTED STATUS TIMEOUT STATUS_SNAPSHOT
    bigquery.go:86: begin tearing down postgres schema bq_2dgblzuo_20260408152801
--- FAIL: TestGenericBQ/Test_Simple_Flow (33.48s)

To view more test analytics, go to the Test Analytics Dashboard
_{📋 Got 3 mins? Take this short survey to help us improve Test Analytics.}

[serprex]

until aws-types updates to r-efi 6.0.0 it can make sense to hold back on updating getrandom

[github-actions]

🔄 Flaky Test Detected

Analysis: The e2e test TestGenericBQ/Test_Schema_Change_Lost_Column_Bug failed due to BigQuery not recognizing good_column after a schema change, exhibiting a classic polling-timeout pattern (243s of retries) consistent with BigQuery schema propagation timing issues rather than a deterministic code bug.
Confidence: 0.75

✅ Automatically retrying the workflow

View workflow run

[github-actions]

🔄 Flaky Test Detected

Analysis: The test failed due to a transient "context deadline exceeded" error when connecting to the Temporal client, indicating an infrastructure connectivity issue rather than a code bug.
Confidence: 0.95

✅ Automatically retrying the workflow

View workflow run

[github-actions]

🔄 Flaky Test Detected

Analysis: The e2e Test_Types_CH test failed due to a 1-nanosecond time precision mismatch (9h7m58.482903s vs 9h7m58.482902s) when comparing QValueTime values between PostgreSQL and ClickHouse, a classic non-deterministic rounding issue rather than a real bug.
Confidence: 0.93

✅ Automatically retrying the workflow

View workflow run

[github-actions]

🔄 Flaky Test Detected

Analysis: The CI job failed due to a network timeout while downloading the Temporal CLI binary during setup, not due to any test or code issue.
Confidence: 0.97

✅ Automatically retrying the workflow

View workflow run

[github-actions]

🔄 Flaky Test Detected

Analysis: The e2e test TestGenericBQ/Test_Simple_Flow failed with UNEXPECTED STATUS TIMEOUT STATUS_SNAPSHOT, indicating a BigQuery snapshot operation timed out — a classic flaky failure from external service latency rather than a code bug.
Confidence: 0.9

✅ Automatically retrying the workflow

View workflow run

[github-actions]

🔄 Flaky Test Detected

Analysis: The e2e test suite hit its 15-minute (900s) timeout limit with a panic: test timed out, causing cascading failures across ~60 subtests — classic flaky behavior from a slow or hung test (TestGenericBQ/Test_Partitioned_Table_Without_Publish_Via_Partition_Root ran 305s) rather than a logic bug.
Confidence: 0.92

✅ Automatically retrying the workflow

View workflow run