Version Bump Control for Concerto packages

[muhabdulkadir]

Discussion 🗣

The current process of publishing workspaces in the GitHub Actions pipeline only updates the package.json version. This limited version bump approach leaves the responsibility of updating all package occurrences to the developer. As a result, there is a risk of version discrepancies across the repository, leading to the need for manual updates and potential inconsistencies.

Context

When a new version of a package is published, it’s common to expect all references to that package in the repository to be updated to match. However, our current approach only updates the version in package.json, which means that other instances of the package—whether in dependency declarations, or other project files—remain unchanged. This can lead to situations where different parts of the codebase reference different versions of a package, creating potential compatibility issues and making future updates more cumbersome.

Detailed Description

To improve this process, we propose enhancing the GitHub Actions workflow to automatically bump the version in package.json as well as all other references of the packages throughout the repository. This will ensure consistency in versioning and eliminate the need for manual updates whenever the package version changes.

Updating the script would involve:

• Scanning and updating the package.json files.
• Identifying and modifying all occurrences of the updated package in other files (e.g., code dependencies).
• Ensuring that version updates are applied within the same pull request.