Skip to content

ci: run the changesets version command through a shell #56

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Akshay-2007-1 merged 1 commit into from
Jul 9, 2026
Merged

ci: run the changesets version command through a shell #56

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion .github/workflows/on_push.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,14 @@ jobs:
# fails CI's immutable install on the resulting "Version Packages" PR. Re-running
# install here keeps the lockfile in sync in the same commit; it's a no-op when
# nothing changed.
version: yarn changeset version && yarn install
#
# changesets/action runs this command directly (not through a shell), splitting it on
# spaces and exec'ing the first token with the rest as literal argv — so a bare
# `yarn changeset version && yarn install` sends `&&`, `yarn`, `install` to the
# changeset CLI itself as extra positional args, which it rejects ("Too many arguments
# passed to changesets"). Wrapping in `bash -c "..."` makes bash the exec'd command and
# hands it the whole compound command as one argument, so `&&` is interpreted correctly.
version: bash -c "yarn changeset version && yarn install"
env:
NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
# changesets/action's own README recommends this for the yarn-install-after-version
Expand Down