ci: run release checksums under bash - #127
Conversation
Use the cross-platform bash shell for the POSIX checksum command so Windows release matrix jobs can generate and upload sidecars.\n\nCo-Authored-By: ForgeCode <noreply@forgecode.dev>
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
🤖 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 · |
|
Dependency limit exceeded — report not shown. This pull request scan exceeded the 10,000-dependency limit applied to this scan, so the results are incomplete and may be inaccurate. To avoid reporting false positives, Socket has not posted a report. Upgrade your plan to raise the dependency limit and get complete reports, or view the partial scan in the dashboard. Socket is always free for open source. If this is a non-commercial open source project, contact us to request a free Team account. |
Assert the generated matrix keeps both Unix and Windows targets while using the explicit bash checksum shell.\n\nCo-Authored-By: ForgeCode <noreply@forgecode.dev>
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (4 files)
Reviewed by step-3.7-flash · Input: 59K · Output: 10.1K · Cached: 324.1K |
User description
Summary
bashon every release matrix runnerThis follows post-merge run 30771049704, where both Windows targets failed because the checksum step was interpreted by PowerShell.
Validation
env -u CI CARGO_NET_OFFLINE=true CARGO_TARGET_DIR=/private/tmp/forgecode-release-checksum-windows-fix-target cargo test -p forge_ci --test ci(7/7)CI=1 CARGO_NET_OFFLINE=true CARGO_TARGET_DIR=/private/tmp/forgecode-release-checksum-windows-fix-target cargo test -p forge_ci --test ci(7/7)cargo check -p forge_ci --offlinecargo fmt --all -- --checkgit diff --checkCodeAnt-AI Description
Run release checksum generation reliably on Windows
What Changed
Impact
✅ Fewer Windows release failures✅ Reliable checksum sidecar uploads✅ Consistent release artifacts across platforms💡 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.