Skip to content

changelog: false throws ENOENT error when CHANGELOG.md doesn't exist in packages at pnpm monorepo (contradicts documentation) #569

Closed as duplicate

Description

@sho-he

Hi there.

When changelog is set to false in .changeset/config.json, the documentation states that "no changelogs will be generated." However, the action throws an ENOENT error when CHANGELOG.md files don't exist in packages, attempting to read them despite the configuration.

According to the official documentation:

If it is false, no changelogs will be generated.

Error

🦋  All files have been updated. Review them and commit at your leisure
node:internal/fs/promises:642
  return new FileHandle(await PromisePrototypeThen(
                        ^                                                            
Error: ENOENT: no such file or directory, open '/packages//CHANGELOG.md'
    at async open (node:internal/fs/promises:642:25)
    at async Object.readFile (node:internal/fs/promises:1279:14)
    at async
file:///home/runner/work/_actions/changesets/action/v1/dist/index.js:55:49267
    at async Promise.all (index 0) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/packages//CHANGELOG.md'
}
Node.js v24.12.0

Configuration

.changeset/config.json:

{
  "changelog": false,
  ...
}
                                                     
Expected Behavior

When changelog: false, the action should not attempt to read CHANGELOG.md files and  should complete successfully without them

Environment
- changesets/action: v1
- @changesets/cli: 2.29.8
- Node.js: v24.12.0

Workaround

Setting "changelog": "@changesets/cli/changelog" resolves the error, but this
contradicts the purpose of disabling changelog generation.

Activity

  1. thomaslovaslokoy-ui commented on Mar 23, 2026

    @thomaslovaslokoy-ui
  2. thomaslovaslokoy-ui commented on Mar 23, 2026

    @thomaslovaslokoy-ui
  3. thomaslovaslokoy-ui commented on Mar 23, 2026

    @thomaslovaslokoy-ui
  4. thomaslovaslokoy-ui commented on Mar 23, 2026

    @thomaslovaslokoy-ui
  5. thomaslovaslokoy-ui commented on Mar 23, 2026

    @thomaslovaslokoy-ui
  6. thomaslovaslokoy-ui commented on Mar 23, 2026

    @thomaslovaslokoy-ui
  7. thomaslovaslokoy-ui commented on Mar 23, 2026

    @thomaslovaslokoy-ui
  8. thomaslovaslokoy-ui commented on Mar 23, 2026

    @thomaslovaslokoy-ui
  9. thomaslovaslokoy-ui commented on Mar 23, 2026

    @thomaslovaslokoy-ui
  10. thomaslovaslokoy-ui commented on Mar 23, 2026

    @thomaslovaslokoy-ui
  11. thomaslovaslokoy-ui commented on Mar 23, 2026

    @thomaslovaslokoy-ui
  12. thomaslovaslokoy-ui commented on Mar 23, 2026

    @thomaslovaslokoy-ui
  13. thomaslovaslokoy-ui commented on Mar 23, 2026

    @thomaslovaslokoy-ui
  14. thomaslovaslokoy-ui commented on Mar 23, 2026

    @thomaslovaslokoy-ui
  15. thomaslovaslokoy-ui commented on Mar 23, 2026

    @thomaslovaslokoy-ui
  16. thomaslovaslokoy-ui commented on Mar 23, 2026

    @thomaslovaslokoy-ui
  17. thomaslovaslokoy-ui commented on Mar 23, 2026

    @thomaslovaslokoy-ui
  18. thomaslovaslokoy-ui commented on Mar 23, 2026

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

Metadata

Metadata

Assignees

No one assigned

    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