chore: 🤖 replace deprecated yarn flag frozen-lockfile

[punkbit]

Why?

Replace deprecated yarn flag frozen-lockfile to favour immutable.

How?

• Replace flags in create and publish workflows

Tickets?

N/A

Preview?

N/A

[changeset-bot]

⚠️ No Changeset found

Latest commit: 1d8732e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

Claude finished @punkbit's task in 30s —— View job

---

PR Review

• Gather context
• Review changes

---

✅ Looks great! No issues found — nice work!

The replacement of --frozen-lockfile (Yarn 1) with --immutable (Yarn Berry) is correct and necessary. Both workflows already use corepack enable, so they're running the modern Yarn version where --immutable is the proper flag to prevent lockfile modifications during CI installs. The change is consistent across both affected workflows.

No changeset needed — this is a CI-only fix with no impact on the published package.

[workflow-authentication-public]

📚 Storybook Preview Deployed

✅ Preview URL: https://click-e60bc35a2-clickhouse.vercel.app

Built from commit: d8373a8be55c495fba2b91da967c11e1a6458e8f