Skip to content
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.

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

Error when validating changeset config with root level package #82

Open
lukasIO opened this issue Mar 8, 2024 · 1 comment
Open

Error when validating changeset config with root level package #82

lukasIO opened this issue Mar 8, 2024 · 1 comment

Comments

@lukasIO
Copy link

lukasIO commented Mar 8, 2024

The error the GH bot posts is:

Some errors occurred when validating the changesets config:
The package or glob expression "my-package-name" specified in the `fixed` option does not match any package in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch.

The repo structure looks like

  • root ("my-package-name") with a package.json set to private
    • packages/javascript ("my-other-package") with a package.json set to public

PNPM workspaces is used in the repo where this issue occurs (https://github.com/livekit/protocol)
When running changesets CLI commands locally (e.g. changeset add) it accurately detects both packages in the repo. However the changeset bot seems to choke with this setup.

config:

{
  "$schema": "https://unpkg.com/@changesets/config@3.0.0/schema.json",
  "changelog": [
    "@livekit/changesets-changelog-github",
    { "repo": "livekit/protocol" }
  ],
  "commit": false,
  "fixed": [["my-package-name", "my-other-package"]],
  "linked": [],
  "access": "public",
  "baseBranch": "main",
  "updateInternalDependencies": "patch",
  "ignore": [],
  "privatePackages": { "version": true, "tag": true }
}
@okinawaa
Copy link

okinawaa commented Apr 5, 2024

any solution? I got same issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants