Skip to content

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

Description

@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.

Activity

  1. matthew-gladman-oua commented on Aug 12, 2025

    @matthew-gladman-oua

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

  2. m3hari commented on Aug 12, 2025

    @m3hari
    Author

    @matthew-gladman-oua commitMode: git-cli

  3. jacksonneal commented on Sep 9, 2025

    @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.

  4. daniel-richter commented on Sep 16, 2025

    @daniel-richter

    +1 on the executable files issue.

    See #523

  5. self-assigned this
    on Apr 16, 2026
  6. s0 commented on Apr 16, 2026

    @s0
    Member

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

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions