Repository navigation
pnpm: prefill with "@fake-scope/fake-pkg" #96
Description
Activity
Any update on this, this is indeed an issue.
@rubencallewaert could you tell me how does your
pnpm-workspace.yamllook like? does it havepackages:field?No, we don’t have a
packagesfield because this is a single-package project. It's a private package that lives at the repository root. pnpm itself recognizes the root package (pnpm -r list). We do have a pnpm-workspace.yaml file which contains minimumReleaseAgeExclude policies etc...Hm, I feel that #111 resolved the original reported issue here. I investigated further the cases around lock file without
packages:and that seems to work OK. And I couldn't find any broken case right now. If you could provide me with more data about your situation and maybe even provide a failing test case... that would be certainly helpful in resolving this.My apologies, that fix makes sense, I use the changesets-gitlab variant, and mistakenly thought this was an issue here due to the above ticket existing and being open and the fact that changesets-gitlab is based on changesets.
It seems like the actual issue is in changesets-gitlab:
un-ts/changesets-gitlab#254
Hi, thanks for the work.
I am switching from
npmtopnpmand I notice that the changeset-bot is autofilling changeset with@fake-scope/fake-pkgwhen creating a changeset directly from the bot comment, inside a PR.It works fine with
npm(didn't triedyarn).Any idea why?