`commitMode: github-api` breaks changeset workflows with file deletion and executable file errors

[m3hari]

Summary

When using commitMode: github-api, the changeset action fails to properly delete changeset files after processing them, leading to infinite "Version Packages" PR loops. Additionally, repositories with executable files fail with "GitHub API only supports non-executable files" errors.

Environment

• changeset action version: v1.5.3
• Node version: 22.14.0
• Repository type: pnpm monorepo
• Platform: GitHub Actions (ubuntu-latest)

Expected Behavior

When a "Version Packages" PR is merged:

1. Changeset files should be deleted after processing
2. Next workflow run should detect no changesets and publish packages
3. Executable files should not cause workflow failures

Actual Behavior

When using commitMode: github-api:

1. Changeset files are processed (versions bumped, CHANGELOGs updated) but NOT deleted
2. Next workflow run creates another "Version Packages" PR (infinite loop)
3. Publishing never occurs because changesets are always detected
4. Executable files cause immediate workflow failure

Workaround

Switch to commitMode: git-cli (the default) - this resolves both issues:

Impact

This makes commitMode: github-api unusable for despite being documented as a feature with GPG signing benefits.

[matthew-gladman-oua]

We're running into this issue as well; has anyone found a workaround?

[m3hari]

@matthew-gladman-oua commitMode: git-cli

[jacksonneal]

+1 on the executable files issue. Our pipeline shouldn't have any diff on the executables so would be interested to know how to ignore them in the commit.

We are using github-api to allow for verified commits.

[daniel-richter]

+1 on the executable files issue.

See #523

[s0]

This should be fixed in v1.7.0 (#563 6af4a7e)