chore: update dependencies and workflows#52
Conversation
|
Warning Review limit reached
Next review available in: 47 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (5)
📝 WalkthroughWalkthroughThis PR bumps pinned GitHub Actions versions across codeql.yml, release-arm64.yml, and release.yml, and updates Cargo dependencies chrono (0.4.41→0.4.45), nu-plugin and nu-protocol (0.112.0→0.113.1). commit.txt and pr_body.txt are updated to document the changes. ChangesDependency and GitHub Actions Updates
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Bumping nu-plugin and nu-protocol to 0.113.1 to close #51. I also rolled in all the open dependabot bumps for chrono, log, and the github actions workflows so we can clear out that queue.
SuaveIV
force-pushed
the
chore/update-deps
branch
from
12a4e86 to
e8e75d8
Compare
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 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-arm64.yml:
- Around line 83-87: The release upload step in the workflow is redundant
because the runner already has gh available and the repo’s release job uses gh
release create directly. Remove the softprops/action-gh-release step from the
arm64 workflow and switch the upload logic to the native gh CLI so it matches
the existing release.yml host job and reduces third-party dependency usage; keep
the provenance attestation step intact.
In @.github/workflows/release.yml:
- Line 58: The pinned GitHub Actions in the release workflow are missing the
trailing version comments, which makes these SHA pins harder to audit
consistently. Update each occurrence of the affected action references in the
workflow jobs that use actions/checkout, actions/upload-artifact,
actions/download-artifact, and actions/attest-build-provenance so they match the
same “# vX.X.X” annotation pattern used in the sibling workflow files. Keep the
SHA pins unchanged and only add the matching version comment next to each unique
action reference.
🪄 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: ASSERTIVE
Plan: Pro
Run ID: 1b3b69f6-43f8-4664-b329-3c66155d5974
⛔ Files ignored due to path filters (1)
Cargo.lockis excluded by!**/*.lock
📒 Files selected for processing (6)
.github/workflows/codeql.yml.github/workflows/release-arm64.yml.github/workflows/release.ymlCargo.tomlcommit.txtpr_body.txt
I completely missed that the release workflow was generated by cargo-dist. We need to update the SHAs in dist-workspace.toml too, otherwise the next dist run will just revert everything. This commit syncs them up.
Switched the release upload step in the ARM64 workflow to use the native `gh` CLI rather than relying on `softprops/action-gh-release`. Since the runner already has the CLI available and our primary release job uses it, this cuts down on an unnecessary third-party dependency.
1 participant
This updates nu-plugin and nu-protocol to 0.113.1 to fix #51.
I also noticed a backlog of dependabot PRs for our cargo and github actions dependencies. I rolled those bumps in here so we can get them out of the way all at once.
Summary by CodeRabbit
chrono,nu-plugin, andnu-protocol, to newer releases.