Upgrade trunk to 1.25.1-beta.9

[trunk-open-pr-bot]

cli upgraded: 1.22.15 → 1.25.1-beta.9

2 linters were upgraded:

• eslint 9.27.0 → 9.39.1
• pmd pmd_releases/7.12.0 → pmd_releases/7.18.0

1 plugin was upgraded:

• trunk-io/configs v1.0.12 → v1.1.2

2 tools were upgraded:

• clangd 19.1.2 → 21.1.0
• clangd-indexing-tools 19.1.2 → 21.1.0

This PR was generated by the Trunk Action. For more info, see our docs or reach out on Slack.

[trunk-io]

⏱️ 1h 8m total CI duration on this PR

Job	Cumulative Duration	Recent Runs
Linter Tests ubuntu-latest	22m	🟩
Linter Tests macOS	20m	🟩
Tool Tests (ubuntu-latest)	11m	🟩
Tool Tests (macOS)	6m	🟩
Action Tests	3m	🟩 🟩
CodeQL-Build	3m	🟩 🟩
Trunk Check runner [linux]	2m	🟩 🟩
Repo Tests / Plugin Tests	38s	🟩
Detect changed files	8s	🟩 🟩
Aggregate Test Results	1s	🟩

_{settings ⋅ feedback ⋅ docs ⋅ learn more about trunk.io}

[trunk-staging-io]

     

Failed Test	Failure Summary	Logs
Testing linter nancy test CUSTOM	The linter 'nancy' failed to run with exit code 3, showing multiple vulnerabilities in the Gitea package.	Logs ↗︎

View Full Report ↗︎ ⋅ Docs

[trunk-staging-io]

     

View Full Report ↗︎ ⋅ Docs

[trunk-staging-io]

     

View Full Report ↗︎ ⋅ Docs

[trunk-io]

     

Failed Test	Failure Summary	Logs
Testing formatter nixpkgs-fmt test test	The test failed because the expected object did not match the received object, indicating a mismatch in task failure details during plugin installa...	Logs ↗︎
Testing linter nancy test CUSTOM	The test failed because the Nancy linter encountered an authorization error accessing the OSS Index, resulting in a non-zero exit code.	Logs ↗︎

Flaky Test	Failure Summary	Logs
Testing tool ripgrep rg --version	The test failed because the actual object did not match the expected object, indicating a mismatch in the exit code and output message.	Logs ↗︎

View Full Report ↗︎ ⋅ Docs

[chip-agent]

I was unable to retrieve any test logs using the testLogsTool. It is possible that the tests did not generate any logs, or that the tool is not configured to access the relevant logs for this repository.

Since I cannot determine the root cause of the flaky tests without more information, I recommend the following:

1. Check the CI/CD pipeline configuration: Verify that the test logs are being correctly captured and stored.
2. Manually inspect the test results: Examine the detailed test results in the CI/CD system to identify the failing tests and their error messages.
3. Consult the repository maintainers: Ask the repository maintainers for assistance in locating the test logs and understanding the cause of the flaky tests.

---

Is this helpful? Click the 👍/👎 buttons below to let us know!

Icons by Icons8

[trunk-staging-io]

🔴 Test Results: 2 Failures

Category	Count	Description
🔧 Version Mismatch	1	Test failed due to a version mismatch for the uv tool.
🤷 Unrelated Failure	1	Failure appears to be unrelated to the changes in this PR.

🔧 Version Mismatch

View affected tests and solution

Affected tests:

• Testing tool uv tool

What broke

The test Testing tool uv tool failed due to a version mismatch for the uv tool. The trunk_cli_version was updated in the PR, which likely introduced a stricter version check or changed the expected version format for tools. The test expects 0.3 but received 0.3.0. This indicates that the test's assertion for the uv tool's version is now out of sync with the new cli's behavior.

🤷 Unrelated Failure

View affected tests and solution

Affected tests:

• Test execution failure: could be caused by test hooks like 'afterAll'.

What broke

This failure appears to be unrelated to the changes in this PR.

The PR upgrades trunk, eslint, pmd, trunk-io/configs, clangd, and clangd-indexing-tools. The failing test is related to the uv tool, which is not mentioned in the PR changes. The error "uv: command not found" indicates that the uv command is missing in the test environment, which is an infrastructure issue and not a direct consequence of the code changes in this PR.

View trace in langsmith

Feedback

[trunk-staging-io]

🔴 Test Results: 1 Failure

Category	Count	Description
🎲 Known Flakiness	1	Existing flaky behavior unrelated to the PR.

🎲 Known Flakiness

View affected tests and solution

Affected tests:

• Testing tool action-validator action-validator --version (FLAKY)

What broke

This failure appears to be existing flaky behavior unrelated to this PR.

The PR only updates tool versions in .trunk/trunk.yaml. The failing test Testing tool action-validator action-validator --version is a test for the action-validator tool, which is not updated in this PR. The error Error: write EPIPE is a generic pipe error that has been observed in previous flaky failures of this test and is not directly related to the changes in tool versions.

View trace in langsmith

Feedback

[trunk-staging-io]

🔴 Test Results: 1 Failure

Category	Count	Description
🐍 Missing Dependency	1	Bandit linter failing due to missing 'pbr' package.

🐍 Missing Dependency

View affected tests and solution

Affected tests:

• Testing linter bandit test basic

What broke

The bandit linter is failing with a ModuleNotFoundError: No module named 'pbr'. This indicates a missing Python dependency, which causes the linter to fail instead of producing the expected linting issues, leading to a snapshot mismatch.

Fix

The fix is to add pbr as a required package to the bandit tool definition.

In linters/bandit/plugin.yaml:6

-       package: bandit
+       package: bandit
+       required_packages:
+         - pbr

View trace in langsmith

Feedback

[trunk-staging-io]

🔴 Test Results: 1 Failure

Category	Count	Description
🐍 Missing Dependency	1	The bandit linter is missing the pbr Python package.

🐍 Missing Dependency

View affected tests and solution

Affected tests:

• Testing linter bandit test basic

What broke

The bandit linter failed to execute due to a ModuleNotFoundError: No module named 'pbr'. This indicates that a required Python dependency for bandit is missing in its execution environment. The PR updated the trunk CLI version, which likely affected the linter's environment setup.

Fix

The bandit linter requires the pbr Python package. This can be resolved by explicitly adding pbr as a dependency for bandit in the .trunk/trunk.yaml file.

In .trunk/trunk.yaml:22

- lint:
-   enabled:
-     # enabled linters inherited from github.com/trunk-io/configs plugin
-     - [email protected]
-     - pmd@pmd_releases/7.16.0
-     - definition-checker
-     - [email protected]
-     - [email protected]
-   disabled:
-     - pylint # pylint diagnostics are too strict
+ lint:
+   definitions:
+     - id: bandit
+       dependencies:
+         - pbr
+   enabled:
+     # enabled linters inherited from github.com/trunk-io/configs plugin
+     - [email protected]
+     - pmd@pmd_releases/7.16.0
+     - definition-checker
+     - [email protected]
+     - [email protected]
+   disabled:
+     - pylint # pylint diagnostics are too strict

View trace in langsmith

Feedback

[trunk-staging-io]

🔴 Test Results: 2 Failures

Category	Count	Description
🔧 Version Mismatch	1	Stricter version validation in the upgraded Trunk CLI caused a mismatch.
🤷 Unrelated Failure	1	The uv command was not found, likely due to a missing dependency.

🔧 Version Mismatch

View affected tests and solution

Affected tests:

• Testing tool uv tool

What broke

The test Testing tool uv tool failed due to a version mismatch error during the uv tool's health check. The test expected a successful installation (exit code 0), but the process failed with exit code 1.

The error message Health check failed for 'uv'. Version mismatch. Expected '0.3' but got '0.3.0' indicates that the upgraded Trunk CLI version (1.25.1-beta.5) enforces a stricter version format. The existing tool definition for uv specifies version 0.3, which the new CLI resolves to 0.3.0 and then flags as a mismatch. This is a direct result of the CLI upgrade in this PR.

Fix

The fix is to update the uv tool's version definition to the more specific 0.3.0 format, which aligns with the stricter validation of the upgraded Trunk CLI.

In tools/uv/trunk.yaml:10

-    - version: "0.3"
+    - version: "0.3.0"
       supported_platforms:
         - linux
         - macos

🤷 Unrelated Failure

View affected tests and solution

Affected tests:

• Test execution failure: could be caused by test hooks like 'afterAll'.

What broke

This failure appears to be unrelated to the changes in this PR.

The test Testing tool uv is failing because the uv command is not found, as indicated by the error messages "uv-check: line 1: uv: command not found" and "uv-lock: line 1: uv: command not found". The PR primarily upgrades various tool versions and the trunk CLI version, and adds a Java runtime. These changes do not directly impact the availability or installation of the uv tool, which seems to be a missing dependency in the test environment.

View trace in langsmith

Feedback

[trunk-staging-io]

🔴 Test Results: 1 Failure

Category	Count	Description
🐍 Dependency Issue	1	Bandit linter failing due to missing pbr module.

🐍 Dependency Issue

View affected tests and solution

Affected tests:

• Testing linter bandit test basic

What broke

The bandit linter is failing because it cannot find the pbr module, resulting in a ModuleNotFoundError. This is likely due to a change in the trunk CLI's dependency management or environment setup, as the bandit linter itself was not explicitly upgraded in the PR.

Fix

In .trunk/trunk.yaml:20

       - [email protected]
       - [email protected]
   definitions:
+    - name: pbr
+      runtime: [email protected]
     - name: actionlint
       files:
         - .actionlint.yaml

View trace in langsmith

Feedback