Upgrade trunk to 1.22.16-beta.4

[trunk-open-pr-bot]

cli upgraded: 1.22.12 → 1.22.16-beta.4

1 linter was upgraded:

• eslint 9.24.0 → 9.26.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 sourcery test CUSTOM	Error installing hermetic tool sourcery v1.2.0, no matching distribution found.	Logs ↗︎
Testing linter hadolint test CUSTOM	The test exceeded the timeout of 900000 ms.	Logs ↗︎

Flaky Test	Failure Summary	Logs
Testing tool sourcery sourcery --version	The expected output of a command did not match the received output, with a difference in the 'exitCode' and 'stdout' properties.	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 linter sourcery test CUSTOM	Error installing hermetic tool sourcery v1.2.0, no matching distribution found.	Logs ↗︎
Testing linter hadolint test CUSTOM	The test exceeded the timeout of 900000 ms.	Logs ↗︎

Flaky Test	Failure Summary	Logs
Testing tool sourcery sourcery --version	The expected output did not match the received output, with a difference in the 'exitCode' property.	Logs ↗︎

View Full Report ↗︎ ⋅ Docs

[chip-agent]

Summary

The test Testing linter sourcery test CUSTOM is failing because the sourcery linter installation failed. The error message indicates that the required version 1.2.0 could not be found.

Root Cause Analysis

The root cause is a CI Pipeline Failure. The upgrade of the trunk cli to version 1.22.16-beta.4 likely introduced a change in how the sourcery linter is handled, or the available versions of sourcery. The test expects sourcery version 1.2.0 to be available, but it is not found during the installation process in the CI environment.

Resolution Plan

1. Update the sourcery linter version in the test or trunk configuration to a version that is currently available.
2. If the version is explicitly defined in the test file tests/index.ts, update it there. Otherwise, check the trunk configuration files for the sourcery linter version.
3. If the test requires version 1.2.0, investigate why this version is not available in the CI environment and if it can be added back.
4. Re-run the CI pipeline with the updated configuration.

Since I cannot access the contents of tests/index.ts or other relevant configuration files, I am unable to provide a more specific resolution. The user should investigate the files and update the sourcery version accordingly.

---

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

Icons by Icons8