Only works for public packages

[djcouto]

Hi 👋

First of all, let me thank you in advance for your for making this a public npm package.

My question is probably better suited to the pull request that served as the basis for this package. Nevertheless, is there a reason why this package purposely drops private packages?

In my use case, I have a set of private packages from which I'd like to generate a changeset based on the conventional commits pattern.

[iamchathu]

I went some threads in Changesets and found this document https://github.com/changesets/changesets/blob/main/docs/versioning-apps.md. Maybe @djcouto also helps this one.

[djcouto]

Hi @iamchathu and @mblackrittr! 👋

As the document you mentioned points out, changesets can be used to manage private packages, all we need to set the private property to true in the .changesets/config.json. After digging into the code, I noticed that the package is just filtering out all private packages instead of looking for this property to decide if it should filter out these packages.

changeset-conventional-commits/src/index.ts

Lines 21 to 23 in b825ee5

	const packages = getPackagesSync(cwd).packages.filter(
	(pkg) => !pkg.packageJson.private && Boolean(pkg.packageJson.version),
	);

I can work on a pull request to fix this if you agree. Let me know what you think 👍

[iamchathu]

I'm okay with anyway that fits on changeset. I like if we can depends on their config and work on our logic based on it. As it they update their logic we have to update in here too. Let's check if they have a package where we can easily depends on