-
Notifications
You must be signed in to change notification settings - Fork 2
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
Robustly discover packages for any tool #8
Robustly discover packages for any tool #8
Conversation
src/configuration.ts
Outdated
} | ||
|
||
function getPackages(rootPath: string): { name: string; path: string }[] { | ||
let { packages } = getPackagesSync(rootPath) as PackagesResult; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I couldn't find types for manypkg, so I just made a rough minimal set, based on what I was seeing as output
type: 'pnpm' | 'yarn' | 'npm'; | ||
}; | ||
packages: Package[] | ||
rootPackage: Package; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the rootPackage is included in packages
, so this is what will allow release-plan to work for single-package monorepos (or monorepos with nested workspaces, like https://github.com/universal-ember/kolay/).
…r-release-plan Use fix for release-plan from: embroider-build/github-changelog#8
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm feeling a bit iffy on this one because we don't have fixture based tests with all the different types of monorepos and non-monorepos 🤔 but I'm not going to hold this PR back, we can add that next time a bug is reported and we try to fix something
manypkg gets all packages, including the root workspace.
This means release-plan does not need to care about the "singlePackage" thing and that code can be removed.
(tho, release-plan will probably need a similar change)
Can test on your own repo with an override: