Skip to content

Lock file maintenance#4572

Closed
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/lock-file-maintenance
Closed

Lock file maintenance#4572
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/lock-file-maintenance

Conversation

@renovate

@renovate renovate Bot commented Jul 13, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

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

@renovate renovate Bot added the dependencies Pull requests that update a dependency file label Jul 13, 2026
@renovate
renovate Bot requested a review from a team as a code owner July 13, 2026 02:46
@renovate renovate Bot added the dependencies Pull requests that update a dependency file label Jul 13, 2026
@renovate
renovate Bot requested a review from a team July 13, 2026 02:46
@claude

claude Bot commented Jul 13, 2026

Copy link
Copy Markdown

Code review

No bugs or CLAUDE.md violations found. Checked for correctness issues, PII/secret leaks, dependency downgrades, and lock file integrity.

Dependency bump analysis

This is a lock-file-only maintenance PR — no Cargo.toml or package.json manifest changes. All bumped versions stay within the semver ranges already specified in the manifests.

Rust (nexus/Cargo.lock):

  • AWS SDK crates bumped: aws-config 1.8.18→1.9.0, aws-credential-types 1.2.14→1.3.0, aws-runtime 1.7.5→1.8.1, aws-sigv4 1.4.5→1.5.1, aws-sdk-kms 1.111.0→1.112.0, plus various aws-smithy-* crates
  • New transitive dependency: aws-smithy-schema (0.2.0) is now pulled in by aws-sdk-kms, aws-sdk-sso, aws-sdk-ssooidc, aws-sdk-sts, and aws-smithy-xml — part of upstream smithy-rs restructuring
  • Other minor bumps: bytes, cc, crossbeam-*, lru, memchr, md5, num-iter, rand
  • Note: several aws-smithy-* crates are pre-1.0 (0.x) where semver permits breaking changes in minor bumps

npm (ui/package-lock.json):

  • next / @next/* 16.2.9→16.2.10
  • @tailwindcss/* 4.3.1→4.3.2
  • @radix-ui/react-* various patch bumps
  • @radix-ui/react-use-escape-keydown replaced by @radix-ui/react-use-effect-event as a transitive dep of react-dismissable-layer (upstream Radix UI refactor)

⚠️ Note: Per REVIEW.md, upstream release notes should be checked for regressions in dependency bump PRs. I was unable to fetch release notes from GitHub (smithy-lang/smithy-rs, vercel/next.js, tailwindlabs/tailwindcss) due to network access restrictions in this environment. A human reviewer should verify the upstream changelogs before merging, particularly for the AWS SDK minor-version bumps and the pre-1.0 aws-smithy-* crates.

@codecov

codecov Bot commented Jul 13, 2026 •
edited
Loading

Copy link
Copy Markdown

❌ 2 Tests Failed:

Tests completed Failed Passed Skipped
3044 2 3042 399
View the top 2 failed test(s) by shortest run time 
github.com/PeerDB-io/peerdb/flow/e2e::TestPeerFlowE2ETestSuiteMySQL_CH
Stack Traces | 0.02s run time 
=== RUN   TestPeerFlowE2ETestSuiteMySQL_CH
=== PAUSE TestPeerFlowE2ETestSuiteMySQL_CH
=== CONT  TestPeerFlowE2ETestSuiteMySQL_CH
--- FAIL: TestPeerFlowE2ETestSuiteMySQL_CH (0.02s)
2026/07/20 03:31:46 INFO Received AWS credentials from peer for connector: ci x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN}
2026/07/20 03:31:46 INFO Received AWS credentials from peer for connector: clickhouse x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN}
2026/07/20 03:31:47 INFO fetched schema x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} table=e2e_test_mach_kcebqcy5.test_ghost_add_col_types

github.com/PeerDB-io/peerdb/flow/e2e::TestPeerFlowE2ETestSuiteMySQL_CH/Test_MySQL_BinlogIncident
Stack Traces | 55.6s run time 
=== RUN   TestPeerFlowE2ETestSuiteMySQL_CH/Test_MySQL_BinlogIncident
=== PAUSE TestPeerFlowE2ETestSuiteMySQL_CH/Test_MySQL_BinlogIncident
=== CONT  TestPeerFlowE2ETestSuiteMySQL_CH/Test_MySQL_BinlogIncident
2026/07/20 03:30:51 INFO Received AWS credentials from peer for connector: ci x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN}
2026/07/20 03:30:51 INFO Received AWS credentials from peer for connector: clickhouse x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN}
2026/07/20 03:30:51 INFO fetched schema x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} table=e2e_test_mych_sfeib2xz.test_date_coercion
    clickhouse_mysql_test.go:2281: 
        	Error Trace:	.../flow/e2e/mysql.go:130
        	            				.../flow/e2e/clickhouse_mysql_test.go:2281
        	            				.../hostedtoolcache/go/1.26.5.../src/runtime/asm_amd64.s:1771
        	Error:      	Received unexpected error:
        	            	MySQL execute error: readInitialHandshake: io.ReadFull(header) failed. err EOF: connection was bad
        	Test:       	TestPeerFlowE2ETestSuiteMySQL_CH/Test_MySQL_BinlogIncident
2026/07/20 03:31:16 INFO fetched schema x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} table=e2e_test_mych_fuax6iqq.test_float
--- FAIL: TestPeerFlowE2ETestSuiteMySQL_CH/Test_MySQL_BinlogIncident (55.60s)

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

@github-actions

github-actions Bot commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

🔄 Flaky Test Detected

Analysis: TestApiPg/TestResyncWithSnapshotConfigOnRunningPipe hit a 180s "wait for flow dropped" timeout on only one of three matrix legs of a dependency-only Renovate PR (resync data already validated), a classic flaky Temporal teardown timeout.
Confidence: 0.9

✅ Automatically retrying the workflow

View workflow run

@renovate renovate Bot changed the title chore(deps): lock file maintenance Lock file maintenance Jul 14, 2026
@ilidemi ilidemi mentioned this pull request Jul 16, 2026
Merged
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 318eb81 to 9ea5b38 Compare July 16, 2026 16:39
@claude

claude Bot commented Jul 16, 2026

Copy link
Copy Markdown

Lock File Maintenance Review

Reviewed the lock file refresh covering nexus/Cargo.lock and ui/package-lock.json.

Rust (Cargo.lock) — key bumps checked

  • AWS SDK ecosystem: aws-config 1.8.18→1.9.0, aws-credential-types 1.2.14→1.3.0, aws-sigv4 1.4.5→1.5.1, and related smithy crates — routine minor releases, no breaking changes, no security advisories.
  • regex 1.12.4→1.13.1 — adds new features in 1.13.0; 1.13.1 fixes a regression from 1.13.0, so the target version is safe.
  • tokio 1.52.3→1.52.4 — patch with scheduler bug fixes, no regressions.
  • rustls 0.23.41→0.23.42 — patch, no security fixes or breaking changes.
  • uuid 1.23.4→1.24.0 — minor with new generation methods, backward compatible.
  • http-body 1.0.1→1.1.0 — minor with new combinators, no breaking changes.
  • Other crates (bytes, clap, crossbeam, syn, etc.) are all routine patch bumps.

Node.js (package-lock.json) — key bumps checked

  • Next.js 16.2.9→16.2.10 — patch with CSS modules and parallel routes fixes, no breaking changes.
  • @radix-ui components (multiple primitives) — patch/minor bumps with accessibility and React 19 compatibility improvements, no breaking changes.

PII/Secrets check

No passwords, tokens, or sensitive data found in the diff.

Verdict

All upstream release notes reviewed — no breaking changes, no security advisories, no known unresolved regressions. Looks clean to merge. ✅

ilidemi added a commit that referenced this pull request Jul 16, 2026
@ilidemi
Include rust builder in renovate, fix script on mac (#4590)
fe839c5 
* Rust builder image has a custom naming scheme Renovate doesn't
recognize. Not updating the image blocks rust upgrades (#4572)
* sed on mac doesn't support inline replacement so use a temp file for
portability
* gitignore one more script output
@ilidemi ilidemi closed this Jul 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@serprex serprex serprex approved these changes

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@serprex @ilidemi