fix(release): refresh crate deps before authorize

[DecisionNerd]

Summary

• Latest recovery 30717011503 reached 13/15, then authorize for graphforge-api failed with blocked_dependencies after a 470s Retry-After on exec.
• Missing on crates.io: graphforge-api, graphforge-cli. Tag stays at dd1fd8c.
• Root cause: fix(release): refresh crate observation before authorize #326 refreshes only the current node; verified deps (e.g. search accepted ~10m earlier) age to observation_stale and block dependents.
• Refresh the current node and its crates dependencies before authorize; include dependency_states in authorize error text.

Test plan

• python3 scripts/ci/test-release-publish-preflight.py
• python3 scripts/ci/test-release-action.py
• Required CI / CI Gate green on exact head SHA
• After merge: one publish.yaml workflow_dispatch for v0.5.1 to finish api+cli

Closes #327

Made with Cursor

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

Note

Refresh crate dependencies before authorization in the publish workflow

• Adds crate-authorize-refresh-nodes.py, a CLI script that enumerates a crates node and its crates dependencies from a JSON manifest, for use by the publish workflow.
• Updates the publish workflow to iterate over all dependency nodes (not just the current node) and refresh each one before authorization.
• Authorization failures in release_action.authorize now include dependency state details (e.g. deps[dep=indeterminate]) in the exception message.
• Adds tests for the new helper script and extends existing authorization and preflight tests to cover these behaviors.

^{Macroscope summarized e769ed2.}

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 28 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 65c92d5a-f54f-4bf5-8138-5969fa1b6cb1

📥 Commits

Reviewing files that changed from the base of the PR and between 6ed5325 and e769ed2.

⛔ Files ignored due to path filters (2)

• .github/workflows/publish.yaml is excluded by !**/.github/**
• .github/workflows/test.yml is excluded by !**/.github/**

📒 Files selected for processing (5)

• scripts/ci/crate-authorize-refresh-nodes.py
• scripts/ci/release_action.py
• scripts/ci/test-crate-authorize-refresh-nodes.py
• scripts/ci/test-release-action.py
• scripts/ci/test-release-publish-preflight.py

---

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