No commits between main and changeset-release/main

[Lazylllama]

I have been trying for hours upon hours to fix this issue but I'm getting nowhere.

Reproduction steps (atleast for me)

1. Add a changeset and then commit to main branch.
2. Github Action proceeds to do as supposed and makes a pull-request like it should.
3. Merge versioning pull request.

Result: Action throws error because there are no new changes on the changeset branch?

Expected Result: Create new release and doesnt fail the workflow.

My repository: https://github.com/LCHoldings/beacon-types

[vmendele]

Hey @Lazylllama, I encountered the same issue, and it turns out that I overridden the version parameter like this:

      - name: Create Release Pull Request
        uses: changesets/action@v1
        with:
          title: Prepare version update
          commit: "[release] update version"
          version: npm run version

And the version script in my package.json didn't call @changesets/cli version:

{
  // ...
  "scripts": {
    "version": "npx --no-install synclockver"
  }
  // ...
}

It works after fixing the version script:

{
  // ...
  "scripts": {
    "version": "npx @changesets/cli version && npx --no-install synclockver"
  }
  // ...
}

I don't know if it solves your issue, but I think it is a good idea to post my solution here in case someone makes the same silly mistake as I did.

Also, your repository is private, so we can't see what's wrong with your workflow.

[Lazylllama]

Hey @Lazylllama, I encountered the same issue, and it turns out that I overridden the version parameter like this:

      - name: Create Release Pull Request
        uses: changesets/action@v1
        with:
          title: Prepare version update
          commit: "[release] update version"
          version: npm run version

And the version script in my package.json didn't call @changesets/cli version:

{
  // ...
  "scripts": {
    "version": "npx --no-install synclockver"
  }
  // ...
}

It works after fixing the version script:

{
  // ...
  "scripts": {
    "version": "npx @changesets/cli version && npx --no-install synclockver"
  }
  // ...
}

I don't know if it solves your issue, but I think it is a good idea to post my solution here in case someone makes the same silly mistake as I did.

Also, your repository is private, so we can't see what's wrong with your workflow.

Hey! Thanks for responding, I will try out what you have sent and see if it works for me. The repository isn't private, I deleted it and moved to a monorepo. 🙂

https://github.com/lcholdings/beacon-npm

[jbltx]

I have a similar issue today, trying to release my-package@2.1.0 but changesets/action tries to create a release PR endlessly, while there is no change to commit.
Note that the tag my-package@2.1.0 does not exist yet. I was expecting it to create the tag, the Github release, and publish packages.

Run changesets/action@v1
  with:
    commit: chore: Update version for release
    title: chore: Update version for release
    publish: pnpm ci:publish
    version: pnpm ci:version
    createGithubReleases: true
    setupGitUser: true
    commitMode: git-cli
  env:
    HUSKY: 0
    PNPM_HOME: /home/runner/setup-pnpm/node_modules/.bin
    STORE_PATH: /home/runner/_work/.pnpm-store/v10
    GITHUB_TOKEN: ***
setting git user
/usr/bin/git config user.name "github-actions[bot]"
/usr/bin/git config user.email ***
setting GitHub credentials
/usr/bin/git checkout changeset-release/release/2.1.x
Switched to a new branch 'changeset-release/release/2.1.x'
branch 'changeset-release/release/2.1.x' set up to track 'origin/changeset-release/release/2.1.x'.
/usr/bin/git reset --hard ***
HEAD is now at 6aa423ff2 chore(release): fix Changeset config base branch
/home/runner/setup-pnpm/node_modules/.bin/pnpm ci:version
> my-repo@0.0.0 ci:version /home/runner/_work/my-repo/my-repo
> changeset version && pnpm install --lockfile-only && pnpm ci:g:postversion && pnpm -r ci:postversion
🦋  All files have been updated. Review them and commit at your leisure
Scope: all 8 workspace projects
Done in 709ms using pnpm v10.13.1
> my-repo@0.0.0 ci:g:postversion /home/runner/_work/my-repo/my-repo
> node scripts/postversion.js
Scope: 7 of 8 workspace projects
packages/my-package ci:postversion$ node ./scripts/postversion.js
packages/my-package ci:postversion: Done (No changes to commit)
packages/my-other-package ci:postversion$ node ./scripts/postversion.js
packages/my-other-package ci:postversion: Done (No changes to commit)
Existing pull requests: []
/usr/bin/git status --porcelain
/usr/bin/git push origin HEAD:changeset-release/release/2.1.x --force
To https://github.com/Unity-Technologies/my-repo
   70138f4c1..6aa423ff2  HEAD -> changeset-release/release/2.1.x
creating pull request
Error: HttpError: Validation Failed: {"resource":"PullRequest","code":"custom","message":"No commits between release/2.1.x and changeset-release/release/2.1.x"} - https://docs.github.com/rest/pulls/pulls#create-a-pull-request
Error: Validation Failed: {"resource":"PullRequest","code":"custom","message":"No commits between release/2.1.x and changeset-release/release/2.1.x"} - https://docs.github.com/rest/pulls/pulls#create-a-pull-request

{ 
  "scripts" : {
    "ci:version": "changeset version && pnpm install --lockfile-only && pnpm ci:g:postversion && pnpm -r ci:postversion",
    "ci:g:postversion": "node scripts/postversion.js",
    "ci:publish": "changeset publish && pnpm ci:g:postpublish",
    "ci:g:postpublish": "node scripts/postpublish.js"
  }
}

I tried pnpm ci:version script locally and there is indeed no change to commit.

[bluwy]

I believe the reason of the reported cases here are because the version script isn't calling the changeset version command, or called by somehow reverted again which becomes no changes. The flow currently expects changes when it sees changesets existing, so to fix this, make sure you have changes after running your custom version script.