fix(ci): pin trunk-action to valid v1.3.1 SHA - #623
Conversation
🤖 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:XS
|
![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: ada7a98018
ℹ️ 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".
| - name: Trunk Upgrade (on schedule only) | ||
| if: github.event_name == 'schedule' | ||
| uses: trunk-io/trunk-action@d90b9166660d5e5afae248a58172a3a0e99d56d5 # v1.0.4 | ||
| uses: trunk-io/trunk-action@04ba50e7658c81db7356da96657e6e77f220bfa3 # v1.3.1 |
There was a problem hiding this comment.
On scheduled runs this updated uses still resolves the root Trunk Check action, not the upgrade action; upstream v1.3.1 documents automatic upgrades with trunk-io/trunk-action/upgrade@v1, and its upgrade/action.yaml input is arguments for “trunk upgrade”, while the root action only defines arguments for checks. In this workflow the following trunk-args: --upgrade input is ignored, so the Monday job runs another check instead of creating an upgrade PR; point this line at /upgrade@04ba50e... and pass arguments if needed.
Useful? React with 👍 / 👎.
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (1 file)
Reviewed by step-3.7-flash · Input: 41.7K · Output: 4.9K · Cached: 141.4K |
User description
The trunk-check.yml workflow pinned trunk-io/trunk-action@d90b916, which does not exist upstream (GitHub API: 422, verified against trunk-io/trunk-action refs) — the same invalid SHA that previously broke Apisync's Trunk Check until #48 pinned v1.3.1.
This pins both uses to the verified v1.3.1 commit 04ba50e7658c81db7356da96657e6e77f220bfa3 (confirmed via ls-remote + GitHub API).
Scope: one file, pin-only. Required checks (ci / lint, ci / test) are unaffected by this workflow.
CodeAnt-AI Description
Restore reliable Trunk checks in CI
What Changed
Impact
✅ Fewer CI workflow failures✅ Reliable lint and format checks✅ Working scheduled Trunk upgrades💡 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.