feat: Add global dependency overrides

[jtdLab]

Description

Support global dependency_overrides (#439)

This allows to define dependency overrides for each workspace package in melos.yaml like:

name: foo

packages:
  - packages/**

globalDependencyOverrides:
  my_dependency: 1.2.3

Type of Change

• [x] ✨ feat -- New feature (non-breaking change which adds functionality)
• [ ] 🛠️ fix -- Bug fix (non-breaking change which fixes an issue)
• [ ] ❌ ! -- Breaking change (fix or feature that would cause existing functionality to change)
• [ ] 🧹 refactor -- Code refactor
• [ ] ✅ ci -- Build configuration change
• [ ] 📝 docs -- Documentation
• [ ] 🗑️ chore -- Chore

[docs-page[bot]]

To view this pull requests documentation preview, visit the following URL:

melos.invertase.dev/~520

Documentation is deployed and generated using docs.page.

[CLAassistant]

All committers have signed the CLA.

[jtdLab]

Hint:

The added globalDependencyOverrides and the existing dependencyOverridePaths do add the dependency override(s) to all workspace packages. This means packages that do not have a regular or dev dependency also get the override(s) which seems to be bad. Is this behaviour intended?

[blaugold]

@jtdLab Thanks for this contribution!

We already have dependencyOverridePaths . Could you make the new option a sibling of that one? I think dependencyOverrides would be enough as its name. Please also document the new option.

Is this behaviour intended?

Yes. Often, dependency overrides are used to override transitive dependencies.

[jtdLab]

@blaugold i am no sure about the docs is it only the overview page which needs an update?

[jtdLab]

Any updates on this?

[jtdLab]

@blaugold @Salakar can some check this pr?

[spydon]

@jtdLab this is offering the same functionality as #594 right?

[spydon]

I'll close this since the functionality will be implemented with the new system in 594, thanks for the effort though!