After a new release of build-chain-configuration reader, we always have to come and update the package here and then make a new release of this package ourselves. Can we automate this?
We can potentially use repository_dispatch events to trigger a workflow run here, whenever we publish a new version of build-chain-configuration-reader. Using peter-evans/repository-dispatch we dispatch an event from build-chain-configuration-reader after we successfully publish the package. We will define a new workflow that will listen for such events in this repository. Upon receiving the event, the workflow will create a pull request that will change the package version as well as build-chain-configuration-reader version
After a new release of build-chain-configuration reader, we always have to come and update the package here and then make a new release of this package ourselves. Can we automate this?
We can potentially use
repository_dispatchevents to trigger a workflow run here, whenever we publish a new version of build-chain-configuration-reader. Using peter-evans/repository-dispatch we dispatch an event from build-chain-configuration-reader after we successfully publish the package. We will define a new workflow that will listen for such events in this repository. Upon receiving the event, the workflow will create a pull request that will change the package version as well as build-chain-configuration-reader version