Open cicoyle opened 9 months ago
Automating here for listening for dapr/dapr tag pushes are going to be a bit tricky ... As from prior PRs, it always involves some change to be done in terms of logs that we look at or methods that we use etc.
But for this case, can we look into automating a PR for changing the upgrade_test.go
testing the upgrade path specifically for any new RCs of dapr.
Essentially update the upgrade path tests with the relevant information of the previous stable and current RC minor/patch versions. And then create a PR for the same.
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 thego.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 thedapr/kit
repo &&dapr/components-contrib
&&dapr/dapr
and auto creates a Pull Request that updates that line in thego.mod
file 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.