Reason/Context

Internal AsyncAPI dependencies are for example a dependency that Generator has to Parser. So we want to automatically bump version of Parser in package.json for Generator, in Generator repo, once Parser is released.

To have best user experience we should not manually maintain dependency tree between repos and use action only in the repository that runs release

Description

How would it work

• you use this action only in the project that should be updated in other projects
• it is part of release workflow, you just trigger it if there was a change in the version of the package

Configuration Options

• Specify GH token
• Specify where package.json is located in case it is not root
• Specify list of repos that would be ignored and not receive update
• Committer details
• commit message for devDependency, so you can always start it with chore
• commit message for dependency, so you can always start it with fix

• we should also expose on output a kind of information about dependency and it dependents. With another action we can push it somewhere, aggregate it from all the repos and have an application that reads it and builds dependency graph of all repos in the organization