Monorepo support in Light-Release

[VincenzoManto]

🚀 Monorepo support in Light-Release

With the growing use of monorepos—repositories housing multiple projects or packages—developers often face unique challenges in release management. light-release aims to be a lightweight, flexible tool for versioning and release automation, and expanding its functionality to fully support monorepo workflows is a priority on our roadmap.

Keys

• Versioning packages separately: In a monorepo, each package may need to be versioned independently based on the changes relevant to that package. This avoids bumping versions unnecessarily across the entire repo.
• Detecting changes per package: A successful monorepo release tool should identify which packages have been modified and trigger version updates and releases accordingly.
• Minimizing configuration: One goal with light-release is to keep configurations lean. With monorepos, ensuring simplicity in configuration while supporting each package’s unique needs is a balance we want to achieve.

Proposed Solution Path for Light-Release

To implement monorepo support in light-release, I’m considering these key features:

• Independent tracking: By tracking changes per package, light-release can independently version only the packages with modifications, while skipping those without changes.

• Scoped conf: We could introduce scoped configurations so that each package can have custom release settings if needed, while still following the overall repo-level settings for simplicity.

Feedbacks

If you have any specific features you’d find helpful in light-release for monorepos, feel free to suggest them here or even contribute via a PR.

Looking forward to your thoughts and feedback!