chore(tooling): add changesets cli patch to allow yarn npm publish

[rubencarvalho]

Description

Adds a patch for @changesets/cli v2.29.7 that enables proper yarn support when publishing packages. The patch modifies two key functions:

1. getPublishTool - Now detects and returns yarn as the publish tool when yarn is the package manager
2. internalPublish - Uses yarn npm publish command instead of npm publish when yarn is detected

This ensures that workspace:* protocol references in package.json dependencies are properly replaced with actual version numbers during publishing.

Motivation and context

Without this patch, changeset publish fails to properly replace workspace:* references when publishing packages in a yarn workspace. This is because changesets defaults to using npm publish even in yarn workspaces, and npm doesn't understand yarn's workspace protocol.

The yarn npm publish command properly resolves workspace:* to the actual published version numbers before publishing to the registry.

Related issue(s)

• Related to upstream changesets/changesets#1449 - Similar fix pending merge
• Related to upstream changesets/changesets#1411 - Original issue report
• Related to upstream changesets/changesets#674 - Comprehensive rework (stalled)

This patch is a temporary solution until the upstream fix is merged and released.

[changeset-bot]

⚠️ No Changeset found

Latest commit: d4fe7db

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

[Rajdeepc]

@rubencarvalho Can you add a minimum validation step like which yarn version is this tested and which CI jobs were validated? Requesting some context here why this was done?

[nikkimk]

lgtm

[rubencarvalho]

@rubencarvalho Can you add a minimum validation step like which yarn version is this tested and which CI jobs were validated? Requesting some context here why this was done?

This is compatible with yarn 4 (our version). I tested this by running:

yarn changeset version --snapshot nightly
yarn changeset publish --tag nightly --no-git-tag

But this will still be re-tested under SWC-1236.

[github-actions]

📚 Branch Preview

• Documentation Site
• Storybook

🔍 Visual Regression Test Results

When a visual regression test fails (or has previously failed while working on this branch), its results can be found in the following URLs:

• Spectrum | Light | Medium | LTR
• Spectrum | Dark | Large | RTL
• Express | Light | Medium | LTR
• Express | Dark | Large | RTL
• Spectrum-two | Light | Medium | LTR
• Spectrum-two | Dark | Large | RTL
• High Contrast Mode | Medium | LTR

Deployed to Azure Blob Storage: pr-5821

If the changes are expected, update the current_golden_images_cache hash in the circleci config to accept the new images. Instructions are included in that file.
If the changes are unexpected, you can investigate the cause of the differences and update the code accordingly.