chore: force cache bust

[beaussan]

🎯 Changes

✅ Checklist

• I have followed the steps in the Contributing guide.
• I have tested this code locally with pnpm test:pr.

🚀 Release Impact

• This change affects published code, and I have generated a changeset.
• This change is docs/CI/dev-only (no release).

[slorber]

Hey, just wondering, why not completely ignore caches when you are in a release workflow?

To me, this is safer to never use any cache in publish workflows. It's better to be secure than faster.

We disabled cache on Docusaurus workflow for that reason: facebook/docusaurus#11795

[SeanCassiere]

Hey, just wondering, why not completely ignore caches when you are in a release workflow?

To me, this is safer to never use any cache in publish workflows. It's better to be secure than faster.

We disabled cache on Docusaurus workflow for that reason: facebook/docusaurus#11795

We're definitely in agreement there. It's on our list of things to action. We're also weighing the option of nuking cache in general.

On this, we should have consensus on a decision soon and we'll roll out something soon to harden stuff across the packages.

[SeanCassiere]

Turned it off for now anyways - 47d572f

[slorber]

👍

See also this related GitHub Actions discussion: https://github.com/orgs/community/discussions/194493

[SeanCassiere]

👍

See also this related GitHub Actions discussion: https://github.com/orgs/community/discussions/194493

Thanks for the heads up on this 🙌🏼