It would be nice to have an automated process that listens for a new tag to be pushed to the dapr/kit repo && dapr/components-contrib && dapr/dapr that updates the go.mod version accordingly so we are always up to date on changes and can automate our release candidate testing. This should be automated to minimize the manual steps in the release process.
I propose adding a GitHub Action Workflow to dapr/cli that listens for a new tag on the dapr/kit repo && dapr/components-contrib && dapr/dapr and auto creates a Pull Request that updates that line in the go.mod file and other relevant changes (go.sum) as a result of go mod tidy. As well as updates the version in the e2e tests & other relevant tests.
It would be nice to have an automated process that listens for a new tag to be pushed to the
dapr/kitrepo &&dapr/components-contrib&&dapr/daprthat updates thego.modversion accordingly so we are always up to date on changes and can automate our release candidate testing. This should be automated to minimize the manual steps in the release process.I propose adding a GitHub Action Workflow to
dapr/clithat listens for a new tag on thedapr/kitrepo &&dapr/components-contrib&&dapr/daprand auto creates a Pull Request that updates that line in thego.modfile and other relevant changes (go.sum) as a result ofgo mod tidy. As well as updates the version in the e2e tests & other relevant tests.