Remove cargo-cache action from build-platforms workflow

[DZakh]

Removes the cargo-cache action step from the build-platforms CI workflow.

Changes

• Removed the ./.github/actions/cargo-cache action invocation that was caching Cargo artifacts per target platform

Rationale

This simplifies the CI workflow by eliminating the per-target cargo caching step. This may reduce CI complexity or address issues with the caching strategy for multi-platform builds.

https://claude.ai/code/session_014sbg79Er1e6Mw2QTMeLuYE

Summary by CodeRabbit

• Chores
  • Updated platform build workflow configuration to enhance build integrity and security practices.

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

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: 8bcacb26-9ce6-4c34-b76c-9c1e958cfe87

📥 Commits

Reviewing files that changed from the base of the PR and between a9ba153 and b7505be.

📒 Files selected for processing (1)

• .github/workflows/build-platforms.yml

---

📝 Walkthrough

Walkthrough

The build-platforms workflow documentation is updated to explicitly clarify that Cargo caching is intentionally omitted from the build process to prevent tampered or poisoned cached artifacts. This replaces implicit behavior with explicit inline comments.

Changes

Cargo Cache Documentation

Layer / File(s)	Summary
Cargo cache safety documentation .github/workflows/build-platforms.yml	Comments are added to document why the workflow does not use Cargo cache, citing artifact integrity concerns.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 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 accurately summarizes the main change: removing the cargo-cache action from the build-platforms workflow, matching the primary modification in the changeset.
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.}

---

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