fix(ci): cargo command for rust workers + fetch annotated tag content

[guibeira]

Summary

Two follow-up fixes uncovered by the first publish attempt after #67 merged (failing run):

• _publish-registry.yml — the rust worker startup expanded cargo_args=(run ...) directly as the command, so the runner tried to exec run and died with run: command not found. Prefix the expansion with cargo so it actually launches cargo run.
• release.yml — fetch-depth: 0 does not bring annotated tag content. The git tag -l --format=%(contents) lookup returned empty, falling back to registry-tag=latest even when the create-tag dispatch wrote registry-tag: next into the annotation. Add fetch-tags: true to the setup checkout.

Test plan

• Re-dispatch create-tag.yml with worker=image-resize, bump=patch, tag=next
• Verify Setup notice prints registry-tag=next
• Verify Start local worker for interface collection runs cargo run --bin image-resize -- and the worker stays alive
• Verify POST /publish returns 200 with tag: "next" in the payload

Summary by CodeRabbit

Release Notes

No user-facing changes in this release. This update includes internal workflow improvements to the CI/CD pipeline for better build and release automation.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: ede65257-637e-4e25-95d7-e68193a158d6

📥 Commits

Reviewing files that changed from the base of the PR and between 292932d and bd51b84.

📒 Files selected for processing (2)

• .github/workflows/_publish-registry.yml
• .github/workflows/release.yml

---

📝 Walkthrough

Walkthrough

Two independent GitHub Actions workflow updates: one fixes the Rust worker startup command to explicitly invoke cargo, and the other adds tag fetching to the release workflow's checkout step to ensure tag metadata is available downstream.

Changes

Rust Worker Invocation Clarification

Layer / File(s)	Summary
Command Invocation .github/workflows/_publish-registry.yml	Explicitly invoke cargo when starting the local worker; change from "${cargo_args[@]}" to cargo "${cargo_args[@]}" and update the corresponding log message.

Release Workflow Tag Fetching

Layer / File(s)	Summary
Checkout Configuration .github/workflows/release.yml	Add fetch-tags: true to actions/checkout@v4 step alongside existing fetch-depth: 0 to ensure tag metadata is available for downstream parsing logic.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5 minutes

Possibly related PRs

• feat: collect worker interface (request/response format) on publish #67: Adds Rust worker support and launches workers via "cargo run" in the same workflow file, directly related to the explicit cargo invocation change.
• ci: add release pipelines for iii-lsp and VSCode extension #17: Modifies the same release workflow file, making it relevant to tag-fetching updates.

Suggested reviewers

• andersonleal
• sergiofilhowz

Poem

🐰 A cargo command now stands tall,
With tags fetched for all,
The workflows align just right—
No more missing might!
Hops happily into the build night ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly summarizes the two main changes: fixing the cargo command invocation for Rust workers and ensuring annotated tag content is fetched in CI workflows.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/publish-cargo-and-fetch-tags

---

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

_{Review rate limit: 0/1 reviews remaining, refill in 60 minutes.}

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