Problem:
In the package architecture that uses gitmodules, when a new dependency is installed using --no-workspaces in a nested module (dependent repository without workspaces), the main metapackage is not updated with this new dependency. This leads to inconsistencies, causing the metapackage to use outdated dependencies while nested modules have newer versions.
Proposed solution:
Create a GitHub Action that detects when a new dependency has been installed with --no-workspaces in any nested module and then updates the same dependency in the main metapackage.
Steps to Implement:
Create a GitHub Action workflow file (.github/workflows/sync-dependencies.yml).
Set up triggers for the action when package.json files in the nested modules are updated.
Define steps to update the dependencies in the main metapackage accordingly.
Commit and push the changes to keep both the nested modules and the metapackage in sync.
Problem: In the package architecture that uses gitmodules, when a new dependency is installed using --no-workspaces in a nested module (dependent repository without workspaces), the main metapackage is not updated with this new dependency. This leads to inconsistencies, causing the metapackage to use outdated dependencies while nested modules have newer versions.
Proposed solution: Create a GitHub Action that detects when a new dependency has been installed with --no-workspaces in any nested module and then updates the same dependency in the main metapackage.
Steps to Implement: