fix(ci): migrate trunk.yaml to schema v0.1 (lint/fmt blocks) - #626
Conversation
The legacy trunk.yaml (top-level linters/formatters/actions/cache/env)
is rejected by the current trunk CLI with config-errors ('missing config
version, please add version: 0.1', unrecognized keys), which has been
failing the Trunk Check job. Migrate to schema v0.1 with lint.enabled /
lint.definitions (preserving the custom actionlint, black --line-length 100,
clippy -D warnings, mypy, ruff commands) and fmt.enabled / fmt.definitions
(preserving black --line-length 100 and rustfmt commands). Versions are
trunk-io/plugins known-good versions; the community plugin source and the
legacy actions/cache/env blocks are dropped (defaults apply).
🤖 CodeAnt AI — Review Status
|
Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
codeant-ai
Bot
added
the
size:M
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f051148760
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| enabled: | ||
| - actionlint@1.7.8 | ||
| - black@25.9.0 | ||
| - clippy@1.65.0 |
There was a problem hiding this comment.
When the Trunk Check workflow runs on a Rust change, clippy@1.65.0 makes the Trunk v1.6.1 clippy plugin download and place Rust/Clippy 1.65 first in PATH (the plugin uses download: rust and ${linter}/bin). This workspace declares rust-version = "1.75" in Cargo.toml, so Cargo will reject the toolchain before linting; pin Clippy/Rustfmt to at least the workspace MSRV or use the CI toolchain instead.
Useful? React with 👍 / 👎.
Code Review SummaryStatus: 2 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)CRITICAL
WARNING
Files Reviewed (1 file)
Fix these issues in Kilo Cloud Reviewed by step-3.7-flash · Input: 73.1K · Output: 13.9K · Cached: 245.5K |
![kilo-code-bot[bot]](https://avatars.githubusercontent.com/in/2193792?s=60&v=4){kind=small}
| fmt: | ||
| enabled: | ||
| - black@25.9.0 | ||
| - prettier@3.6.2 |
There was a problem hiding this comment.
WARNING: prettier@3.6.2 is enabled without a fmt.definitions entry
Trunk v0.1 requires explicit command definitions for enabled formatters; black and rustfmt both have definitions, but prettier does not. If Trunk does not provide a built-in prettier command, formatting checks for Prettier-managed files will be silently skipped.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
codeant-ai
Bot
added
size:M
|
User description
Trunk Check fails on the legacy trunk.yaml schema (the current trunk CLI reports 'missing config version, please add version: 0.1' plus unrecognized top-level keys, e.g. linters/formatters/actions/cache/env).
Migrates to schema v0.1: version: 0.1, lint.enabled + lint.definitions (preserving the custom actionlint, black --line-length 100, clippy -D warnings, mypy, ruff commands), fmt.enabled + fmt.definitions (preserving black --line-length 100 and rustfmt). Tool versions are trunk-io/plugins known-good versions. The community plugin source and legacy actions/cache/env blocks are dropped (defaults apply).
Note: validation of the Trunk Check job currently depends on trunk.io's launcher env-cache endpoints, which are returning 403 (upstream outage, reproducible locally); the schema itself is verified against the trunk docs and is identical in shape to the Apisync equivalent.
CodeAnt-AI Description
Restore Trunk Check compatibility with the current configuration schema
What Changed
Impact
✅ Trunk Check can validate the repository with the current CLI✅ Existing lint and formatting checks remain enabled✅ Fewer CI configuration errors💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.