Skip to content

chore: fix the CI build by adding yarn#8

Open
AaravMalani wants to merge 2 commits into
mainfrom
chore/fix-ci
Open

chore: fix the CI build by adding yarn#8
AaravMalani wants to merge 2 commits into
mainfrom
chore/fix-ci

Conversation

@AaravMalani

Copy link
Copy Markdown
Member

No description provided.

@gemini-code-assist

Copy link
Copy Markdown

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

@changeset-bot

changeset-bot Bot commented Jun 10, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 39518c2

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

@Akshay-2007-1 Akshay-2007-1 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One thing before merge though: the action only overrides publish, so version still falls back to the default bare changeset version. That'll hit the exact same "command not found" the first time there's a changeset to process. Can we add it in the same step so the fix is complete?

with:

  version: yarn changeset version
  publish: yarn changeset publish

Otherwise looks good.

@AaravMalani

Copy link
Copy Markdown
Member Author

Yep, I'll make the update

One thing before merge though: the action only overrides publish, so version still falls back to the default bare changeset version. That'll hit the exact same "command not found" the first time there's a changeset to process. Can we add it in the same step so the fix is complete?

with:

  version: yarn changeset version
  publish: yarn changeset publish

Otherwise looks good.

Updated! I didn't realise the default was changeset version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants