Skip to content

Lock file maintenance - #4598

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

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

Conversation

@renovate

@renovate renovate Bot commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

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.

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

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lock File Maintenance Review

MSRV / Build Breakage (High Severity)

The AWS SDK crate bumps in nexus/Cargo.lock raise the minimum supported Rust version (MSRV) to rustc 1.94.1, but the Docker build environment currently uses rustc 1.93.0. This causes the docker-build CI job to fail with:

error: rustc 1.93.0 is not supported by the following packages:
  aws-config@1.9.0 requires rustc 1.94.1
  aws-credential-types@1.3.0 requires rustc 1.94.1
  aws-runtime@1.8.1 requires rustc 1.94.1
  aws-sdk-kms@1.112.0 requires rustc 1.94.1
  aws-sdk-sso@1.103.0 requires rustc 1.94.1
  aws-sdk-ssooidc@1.105.0 requires rustc 1.94.1
  aws-sdk-sts@1.108.0 requires rustc 1.94.1
  aws-sigv4@1.5.1 requires rustc 1.94.1
  aws-smithy-async@1.3.0 requires rustc 1.94.1
  aws-smithy-http@0.64.0 requires rustc 1.94.1
  aws-smithy-http-client@1.2.0 requires rustc 1.94.1
  aws-smithy-json@0.63.0 requires rustc 1.94.1
  aws-smithy-observability@0.3.0 requires rustc 1.94.1
  aws-smithy-query@0.61.1 requires rustc 1.94.1
  aws-smithy-runtime@1.12.0 requires rustc 1.94.1
  aws-smithy-runtime-api@1.13.0 requires rustc 1.94.1
  aws-smithy-runtime-api-macros@1.1.0 requires rustc 1.94.1
  aws-smithy-schema@0.2.0 requires rustc 1.94.1
  aws-smithy-types@1.6.1 requires rustc 1.94.1
  aws-smithy-xml@0.61.1 requires rustc 1.94.1
  aws-types@1.4.0 requires rustc 1.94.1

This PR cannot be merged as-is. Either the Rust toolchain in the Docker image needs to be updated to ≥1.94.1, or the AWS SDK crate versions need to be pinned/constrained to versions compatible with rustc 1.93.0.

Clippy Failure (Pre-existing)

The clippy CI job also fails with clippy::useless_borrows_in_formatting at peer-cursor/src/util.rs:51. This appears to be a pre-existing issue (not introduced by this PR's lock file changes), likely triggered by a newer clippy version in CI.

Cargo.lock Bumps Summary

~45 crates bumped, mostly patch versions. Notable minor bumps:

  • AWS SDK suite: 21 crates bumped (see MSRV issue above)
  • regex: 1.12.4 → 1.13.1 — new minor, routine feature additions
  • tokio: 1.52.3 → 1.52.4 — patch fix
  • rustls: 0.23.41 → 0.23.42 — patch fix
  • uuid: 1.23.4 → 1.24.0 — minor bump
  • http-body: 1.0.1 → 1.1.0 — minor bump
  • Other crates: patch-level bumps with no known regressions

package-lock.json Bumps Summary

~50+ npm packages refreshed, all patch or minor bumps:

  • next: 16.2.9 → 16.2.10 (patch)
  • tailwindcss: 4.3.1 → 4.3.2 (patch)
  • webpack: 5.108.1 → 5.108.4 (patch)
  • typescript-eslint: 8.62.0 → 8.63.0 (minor)
  • prettier: 3.9.1 → 3.9.5 (patch)
  • protobufjs: 8.6.5 → 8.7.0 (minor)
  • @radix-ui packages: various patch bumps
  • No breaking changes or known regressions identified in npm bumps

PII/Secrets Check

No PII or secrets found in the changes. ✓

🤖 Generated with Claude Code

@github-actions

Copy link
Copy Markdown
Contributor

🔄 Flaky Test Detected

Analysis: The single failed shard (mysql-pos 7.0) failed in MySQL test-setup with a transient handshake connection error ("readInitialHandshake ... EOF: connection was bad") on a lock-file-only Renovate PR while the other two matrix shards passed, indicating an infrastructure flake rather than a real bug.
Confidence: 0.92

✅ Automatically retrying the workflow

View workflow run

@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 9ea5b38 to c0603fe Compare July 20, 2026 16:54

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lock File Maintenance Review

MSRV Regression (Breaking)

The AWS SDK crate bumps in this lock file refresh require Rust 1.94.1, but the Docker build image in stacks/peerdb-server.Dockerfile pins Rust 1.93.0. This causes the docker-build CI job to fail:

error: rustc 1.93.0 is not supported by the following packages:
  aws-config@1.9.0 requires rustc 1.94.1
  aws-credential-types@1.3.0 requires rustc 1.94.1
  aws-runtime@1.8.1 requires rustc 1.94.1
  aws-sdk-kms@1.112.0 requires rustc 1.94.1
  ... (20 total aws-* crates)

Action required: Either bump the Rust toolchain in stacks/peerdb-server.Dockerfile to >= 1.94.1, or pin the AWS SDK crates to their previous versions in Cargo.toml.

Other Dependency Bumps — No Regressions Found

Category Key bumps Verdict
syn 3.0.2 (new major) Used by serde_derive, thiserror-impl, async-trait. Breaking changes are internal to syn's API; downstream proc-macro crates already absorb them. PeerDB doesn't use syn directly. Safe
tokio 1.52.3 → 1.53.0 Bug fixes (FastRand, mpsc wake timing, timer reset). No breaking changes. Safe
hyper 1.10.1 → 1.11.0 HTTP/1 correctness fixes. Additive only. Safe
http-body 1.0.1 → 1.1.0 Adds Add/Copy for SizeHint. No breaking changes. Safe
AWS SDK family Minor bumps across ~20 crates. No API breaks beyond MSRV. Safe (after MSRV fix)
rustls 0.23.41 → 0.23.42 Patch. Safe
regex 1.12.4 → 1.13.1 Minor. Safe
serde 1.0.228 → 1.0.229 Patch. Safe
Next.js 16.2.9 → 16.2.10 Patch. Safe
Radix UI (30+ packages) Patch/minor. Safe
Tailwind CSS 4.3.1 → 4.3.2 Patch. Safe

Security / PII Check

No passwords, tokens, or secrets found in the diff. Lock files only.

Note on clippy CI failure

The clippy job fails on a pre-existing lint (clippy::useless_borrows_in_formatting at peer-cursor/src/util.rs:51) unrelated to this PR's lock file changes.

@codecov

codecov Bot commented Jul 20, 2026

Copy link
Copy Markdown

❌ 8 Tests Failed:

Tests completed Failed Passed Skipped
3033 8 3025 377
View the top 3 failed test(s) by shortest run time
github.com/PeerDB-io/peerdb/flow/e2e::TestPeerFlowE2ETestSuiteMariaDB_CH
Stack Traces | 0.01s run time
=== RUN   TestPeerFlowE2ETestSuiteMariaDB_CH
=== PAUSE TestPeerFlowE2ETestSuiteMariaDB_CH
=== CONT  TestPeerFlowE2ETestSuiteMariaDB_CH
--- FAIL: TestPeerFlowE2ETestSuiteMariaDB_CH (0.01s)
2026/07/20 17:04:50 INFO Received AWS credentials from peer for connector: ci x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN}
2026/07/20 17:04:50 INFO Received AWS credentials from peer for connector: clickhouse x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN}
github.com/PeerDB-io/peerdb/flow/e2e::TestPeerFlowE2ETestSuiteMariaDB_CH_Cluster
Stack Traces | 0.01s run time
=== RUN   TestPeerFlowE2ETestSuiteMariaDB_CH_Cluster
=== PAUSE TestPeerFlowE2ETestSuiteMariaDB_CH_Cluster
=== CONT  TestPeerFlowE2ETestSuiteMariaDB_CH_Cluster
--- FAIL: TestPeerFlowE2ETestSuiteMariaDB_CH_Cluster (0.01s)
2026/07/20 17:09:28 INFO Received AWS credentials from peer for connector: ci x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN}
2026/07/20 17:09:28 INFO Received AWS credentials from peer for connector: clickhouse x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN}
2026/07/20 17:09:28 INFO fetched schema x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} table=e2e_test_mych_gs7ghzyw.test_vector
github.com/PeerDB-io/peerdb/flow/e2e::TestPeerFlowE2ETestSuiteMySQL_CH_Cluster
Stack Traces | 0.01s run time
=== RUN   TestPeerFlowE2ETestSuiteMySQL_CH_Cluster
=== PAUSE TestPeerFlowE2ETestSuiteMySQL_CH_Cluster
=== CONT  TestPeerFlowE2ETestSuiteMySQL_CH_Cluster
--- FAIL: TestPeerFlowE2ETestSuiteMySQL_CH_Cluster (0.01s)
2026/07/20 17:08:16 INFO Received AWS credentials from peer for connector: ci x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN}
2026/07/20 17:08:16 INFO Received AWS credentials from peer for connector: clickhouse x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN}
2026/07/20 17:08:16 INFO fetched schema x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} table=e2e_test_machcl_idhftl2g.test_sc_resync_cluster
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 17:10:34 INFO Received AWS credentials from peer for connector: ci x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN}
2026/07/20 17:10:34 INFO Received AWS credentials from peer for connector: clickhouse x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN}
github.com/PeerDB-io/peerdb/flow/e2e::TestPeerFlowE2ETestSuiteMariaDB_CH/Test_MySQL_DateTime_ClickHouse_Range
Stack Traces | 20.1s run time
=== RUN   TestPeerFlowE2ETestSuiteMariaDB_CH/Test_MySQL_DateTime_ClickHouse_Range
=== PAUSE TestPeerFlowE2ETestSuiteMariaDB_CH/Test_MySQL_DateTime_ClickHouse_Range
=== CONT  TestPeerFlowE2ETestSuiteMariaDB_CH/Test_MySQL_DateTime_ClickHouse_Range
2026/07/20 17:03:22 INFO Received AWS credentials from peer for connector: ci x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN}
2026/07/20 17:03:22 INFO Received AWS credentials from peer for connector: clickhouse x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN}
2026/07/20 17:03:22 INFO fetched schema x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} table=e2e_test_machclg_fggjidhw.test_simple_schema_changes
    clickhouse_mysql_test.go:2139: WaitFor waiting on snapshot 2026-07-20 17:03:26.082866974 +0000 UTC m=+280.056436398
    clickhouse_mysql_test.go:2143: WaitFor waiting on cdc 2026-07-20 17:03:26.0877522 +0000 UTC m=+280.061321624
2026/07/20 17:03:26 INFO fetched schema x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} table=e2e_test_machclg_fggjidhw.test_simple_schema_changes
    clickhouse_mysql_test.go:2160: 
        	Error Trace:	.../flow/e2e/clickhouse_mysql_test.go:2160
        	            				.../flow/e2e/clickhouse_mysql_test.go:2166
        	            				.../hostedtoolcache/go/1.26.5.../src/runtime/asm_amd64.s:1771
        	Error:      	Not equal: 
        	            	expected: "1900-01-01"
        	            	actual  : "1000-06-15"
        	            	
        	            	Diff:
        	            	--- Expected
        	            	+++ Actual
        	            	@@ -1 +1 @@
        	            	-1900-01-01
        	            	+1000-06-15
        	Test:       	TestPeerFlowE2ETestSuiteMariaDB_CH/Test_MySQL_DateTime_ClickHouse_Range
--- FAIL: TestPeerFlowE2ETestSuiteMariaDB_CH/Test_MySQL_DateTime_ClickHouse_Range (20.15s)
github.com/PeerDB-io/peerdb/flow/e2e::TestPeerFlowE2ETestSuiteMySQL_CH/Test_MySQL_DateTime_ClickHouse_Range
Stack Traces | 20.1s run time
=== RUN   TestPeerFlowE2ETestSuiteMySQL_CH/Test_MySQL_DateTime_ClickHouse_Range
=== PAUSE TestPeerFlowE2ETestSuiteMySQL_CH/Test_MySQL_DateTime_ClickHouse_Range
=== CONT  TestPeerFlowE2ETestSuiteMySQL_CH/Test_MySQL_DateTime_ClickHouse_Range
2026/07/20 17:09:49 INFO Received AWS credentials from peer for connector: ci x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN}
2026/07/20 17:09:49 INFO Received AWS credentials from peer for connector: clickhouse x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN}
2026/07/20 17:09:49 INFO fetched schema x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} table=e2e_test_mych_rgme8wnn.test_mysql_schema_changes
    clickhouse_mysql_test.go:2139: WaitFor waiting on snapshot 2026-07-20 17:09:53.656434764 +0000 UTC m=+667.630004178
    clickhouse_mysql_test.go:2143: WaitFor waiting on cdc 2026-07-20 17:09:53.661576128 +0000 UTC m=+667.635145542
2026/07/20 17:09:53 INFO fetched schema x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} table=e2e_test_mych_rgme8wnn.test_mysql_schema_changes
    clickhouse_mysql_test.go:2160: 
        	Error Trace:	.../flow/e2e/clickhouse_mysql_test.go:2160
        	            				.../flow/e2e/clickhouse_mysql_test.go:2166
        	            				.../hostedtoolcache/go/1.26.5.../src/runtime/asm_amd64.s:1771
        	Error:      	Not equal: 
        	            	expected: "1900-01-01"
        	            	actual  : "1000-06-15"
        	            	
        	            	Diff:
        	            	--- Expected
        	            	+++ Actual
        	            	@@ -1 +1 @@
        	            	-1900-01-01
        	            	+1000-06-15
        	Test:       	TestPeerFlowE2ETestSuiteMySQL_CH/Test_MySQL_DateTime_ClickHouse_Range
--- FAIL: TestPeerFlowE2ETestSuiteMySQL_CH/Test_MySQL_DateTime_ClickHouse_Range (20.15s)
github.com/PeerDB-io/peerdb/flow/e2e::TestPeerFlowE2ETestSuiteMariaDB_CH_Cluster/Test_MySQL_DateTime_ClickHouse_Range
Stack Traces | 20.3s run time
=== RUN   TestPeerFlowE2ETestSuiteMariaDB_CH_Cluster/Test_MySQL_DateTime_ClickHouse_Range
=== PAUSE TestPeerFlowE2ETestSuiteMariaDB_CH_Cluster/Test_MySQL_DateTime_ClickHouse_Range
=== CONT  TestPeerFlowE2ETestSuiteMariaDB_CH_Cluster/Test_MySQL_DateTime_ClickHouse_Range
2026/07/20 17:08:42 INFO Received AWS credentials from peer for connector: ci x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN}
    clickhouse_mysql_test.go:2139: WaitFor waiting on snapshot 2026-07-20 17:08:47.742713968 +0000 UTC m=+601.716283382
    clickhouse_mysql_test.go:2143: WaitFor waiting on cdc 2026-07-20 17:08:47.751510727 +0000 UTC m=+601.725080141
2026/07/20 17:08:47 INFO fetched schema x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} table=e2e_test_machcl_hrqdxfkx.test_my_enum
    clickhouse_mysql_test.go:2160: 
        	Error Trace:	.../flow/e2e/clickhouse_mysql_test.go:2160
        	            				.../flow/e2e/clickhouse_mysql_test.go:2166
        	            				.../hostedtoolcache/go/1.26.5.../src/runtime/asm_amd64.s:1771
        	Error:      	Not equal: 
        	            	expected: "1900-01-01"
        	            	actual  : "1000-06-15"
        	            	
        	            	Diff:
        	            	--- Expected
        	            	+++ Actual
        	            	@@ -1 +1 @@
        	            	-1900-01-01
        	            	+1000-06-15
        	Test:       	TestPeerFlowE2ETestSuiteMariaDB_CH_Cluster/Test_MySQL_DateTime_ClickHouse_Range
--- FAIL: TestPeerFlowE2ETestSuiteMariaDB_CH_Cluster/Test_MySQL_DateTime_ClickHouse_Range (20.27s)
github.com/PeerDB-io/peerdb/flow/e2e::TestPeerFlowE2ETestSuiteMySQL_CH_Cluster/Test_MySQL_DateTime_ClickHouse_Range
Stack Traces | 20.3s run time
=== RUN   TestPeerFlowE2ETestSuiteMySQL_CH_Cluster/Test_MySQL_DateTime_ClickHouse_Range
=== PAUSE TestPeerFlowE2ETestSuiteMySQL_CH_Cluster/Test_MySQL_DateTime_ClickHouse_Range
=== CONT  TestPeerFlowE2ETestSuiteMySQL_CH_Cluster/Test_MySQL_DateTime_ClickHouse_Range
2026/07/20 17:07:33 INFO Received AWS credentials from peer for connector: ci x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN}
2026/07/20 17:07:34 INFO fetched schema x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} table=e2e_test_mychcl_6ridbu3b.test_mysql_schema_changes
2026/07/20 17:07:34 INFO fetched schema x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} table=e2e_test_mychcl_lb52080z.test_ghost_add_col_types
    clickhouse_mysql_test.go:2139: WaitFor waiting on snapshot 2026-07-20 17:07:39.116452393 +0000 UTC m=+533.090021807
    clickhouse_mysql_test.go:2143: WaitFor waiting on cdc 2026-07-20 17:07:39.12643549 +0000 UTC m=+533.100004904
    clickhouse_mysql_test.go:2160: 
        	Error Trace:	.../flow/e2e/clickhouse_mysql_test.go:2160
        	            				.../flow/e2e/clickhouse_mysql_test.go:2166
        	            				.../hostedtoolcache/go/1.26.5.../src/runtime/asm_amd64.s:1771
        	Error:      	Not equal: 
        	            	expected: "1900-01-01"
        	            	actual  : "1000-06-15"
        	            	
        	            	Diff:
        	            	--- Expected
        	            	+++ Actual
        	            	@@ -1 +1 @@
        	            	-1900-01-01
        	            	+1000-06-15
        	Test:       	TestPeerFlowE2ETestSuiteMySQL_CH_Cluster/Test_MySQL_DateTime_ClickHouse_Range
2026/07/20 17:07:54 INFO fetched schema x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} table=e2e_test_mychcl_bntcsyyl.test_blobs
--- FAIL: TestPeerFlowE2ETestSuiteMySQL_CH_Cluster/Test_MySQL_DateTime_ClickHouse_Range (20.27s)

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

Copy link
Copy Markdown
Contributor

❌ Test Failure

Analysis: Not flaky — Test_MySQL_DateTime_ClickHouse_Range fails deterministically in all 4 ClickHouse variants because the latest ClickHouse extended its Date32 range and returns "1000-06-15" instead of clamping to the test's hardcoded expected boundary "1900-01-01", a real behavior mismatch needing a test fix, not a retry.
Confidence: 0.88

⚠️ This appears to be a real bug - manual intervention needed

View workflow run

@renovate renovate Bot changed the title Lock file maintenance chore(deps): lock file maintenance Jul 21, 2026
@renovate renovate Bot changed the title chore(deps): lock file maintenance Lock file maintenance Jul 22, 2026
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from c0603fe to 870df7c Compare July 24, 2026 15:32
@claude

claude Bot commented Jul 24, 2026

Copy link
Copy Markdown

Lock File Maintenance Review

Reviewed the lock file refresh across nexus/Cargo.lock and ui/package-lock.json. No source code changes — only transitive dependency version bumps.

Cargo.lock highlights

  • AWS SDK suite: Coordinated minor bump (e.g. aws-config 1.8.18 → 1.10.0, aws-smithy-runtime-api 1.12.3 → 1.14.0). All within PeerDB's "1" version constraints. New transitive dep aws-smithy-schema added by SDK crates.
  • syn 3.0.3 added alongside existing 2.0.119 — pulled in transitively by async-trait 0.1.91 and clap_derive 4.6.4. PeerDB has no direct syn dependency; dual major versions in the lock file are normal during ecosystem migration.
  • tokio 1.52.3 → 1.53.1, hyper 1.10.1 → 1.11.0, http-body 1.0.1 → 1.1.0, regex 1.12.4 → 1.13.1: All minor/patch, backward compatible.
  • cc 1.2.66 → 1.4.0: Build tool crate minor bump.
  • Other routine patch bumps: serde, borsh, uuid, clap, rustls, bytes, futures, etc.

package-lock.json highlights

  • next 16.2.9 → 16.2.10: Patch release with bug fixes.
  • tailwindcss 4.3.1 → 4.3.3, postcss 8.5.16 → 8.5.19: Patch releases.
  • typescript-eslint 8.62.0 → 8.64.0, eslint 9.39.4 → 9.39.5: Minor/patch, backward compatible.
  • protobufjs 8.6.5 → 8.7.1, webpack 5.108.1 → 5.108.4: Minor/patch releases.
  • @radix-ui components: Routine patch bumps.

Checks

  • ✅ No PII/secret exposure risk (lock files only, no logging changes)
  • ✅ No breaking changes or regressions identified in upstream release notes
  • ✅ No security advisories found for bumped versions
  • ✅ All version constraints in Cargo.toml remain satisfied

Looks clean.

🤖 Reviewed with Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant