Repository navigation
fix(release): configure linker via env vars to avoid polluting worktree - #766
Conversation
📝 WalkthroughWalkthroughThe release workflow now configures ChangesMusl linker workflow
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/release.yml:
- Around line 90-96: Remove the added
CARGO_TARGET_X86_64_UNKNOWN_LINUX_MUSL_LINKER entry from the release workflow’s
job-level env block. Keep .github/workflows/release.yml unchanged unless this is
explicitly approved as a CI-maintenance change; relocate the linker
configuration to an allowed non-workflow configuration path instead.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 6ee0d7db-c096-4ca4-9071-6c1e86c54319
📒 Files selected for processing (1)
.github/workflows/release.yml
Should fix the warnings about building from an unclean checkout
Summary by CodeRabbit