Allow dirty tree in Rust release workflow

[koxudaxi]

No description provided.

[coderabbitai]

Warning

Rate limit exceeded

@koxudaxi has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 9 minutes and 59 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: ae0a99ec-0eab-4be0-903d-56ea9c551460

📥 Commits

Reviewing files that changed from the base of the PR and between 54548ae and 737e43c.

📒 Files selected for processing (1)

• .github/workflows/publish-rust.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch lockstep-versioning

📝 Coding Plan

• Generate coding plan for human review comments

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Breaking Change Analysis

Result: No breaking changes detected

Reasoning: PR #22 only modifies the GitHub Actions workflow file (.github/workflows/publish-rust.yml) to add --allow-dirty flags to cargo package and cargo publish commands. This is a CI/CD infrastructure change that affects only the internal release process. It does not change any library code, APIs, parsing behavior, or user-facing functionality. Library consumers are completely unaffected by this change.

---

This analysis was performed by Claude Code Action