Add --enable-pnpm-catalog flag to opt into pnpm workspace catalog detection

[cyril-sf]

When using pnpm workspaces with the catalog feature, updating a dependency version in the catalog section of pnpm-workspace.yaml is detected as a change by changesets.

Allow changeset add and changeset status to include updates from pnpm workspace catalogs when requested via the new flag.

Fixes #1707

[changeset-bot]

🦋 Changeset detected

Latest commit: 3f7aac5

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 6 packages

Name	Type
@changesets/cli	Minor
@changesets/git	Minor
@changesets/apply-release-plan	Patch
@changesets/read	Patch
@changesets/release-utils	Patch
@changesets/get-release-plan	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[codecov]

Codecov Report

❌ Patch coverage is 83.33333% with 9 lines in your changes missing coverage. Please review.
⚠️ Please upload report for BASE (main@ca0be26). Learn more about missing BASE report.
⚠️ Report is 3 commits behind head on main.

Files with missing lines	Patch %	Lines
packages/git/src/index.ts	89.13%	5 Missing ⚠️
packages/cli/src/run.ts	0.00%	4 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1714   +/-   ##
=======================================
  Coverage        ?   80.87%           
=======================================
  Files           ?       54           
  Lines           ?     2311           
  Branches        ?      703           
=======================================
  Hits            ?     1869           
  Misses          ?      437           
  Partials        ?        5           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[chriswiggins]

Found out about pnpm catalogs yesterday (awesome feature!) and this is the only blocker stopping us from adopting them. Anything we can do to help with merging this PR?

[cyril-sf]

I'm happy to work on any change that would be necessary to get this through the finish line.

[Andarist]

Is catalog: useful mainly for external packages outside of the monorepo? If yes, then it seems we should make the auto-bumps based on its changes an option. If you think about catalog: as being just a sugar over inlined versions from the catalog then Changesets would, traditionally, not bump your monorepo packages based on changes to external dependencies. There were requests to make that work though so perhaps this would be a good occasion to implement this as a flag if you have already implemented the core sinceRef~ logic for the catalog anyway.

[cyril-sf]

Thanks for the reply!

Changesets would, traditionally, not bump your monorepo packages based on changes to external dependencies

This doesn't seem right. If my package depends on React 17 and I bump it to 18, it requires a version bump of my package.

But happy to have a flag if that's what it takes. I can try to take a stab at it next week.

[chriswiggins]

Changesets will generate a change for any files in a normal (flat) repository right? In the monorepo catalog case, there could be no file changes under each of the packages, but the workspace file (and associated catalog entries) IS modified, which would mean a change, which is what @cyril-sf has implemented I think?

[cyril-sf]

@chriswiggins correct!