search

dapr / python-sdk

Dapr SDK for Python
Apache License 2.0
221 stars 125 forks source link

Release SDK 1.13 #684

Closed berndverst closed 5 months ago

berndverst commented 5 months ago

Description

Release SDK 1.13.0 -[x] All dependencies do not use the -dev name (e.g. we do not use dapr-dev or dapr-ext-grpc-dev)

This was done previously for the RC. When we cut a release branch we have to switch from the main branch builds (-dev) packages, to our real release packages.

grep -rol "dapr\-dev" . --include "setup.cfg" --include "requirements.txt" --include "Readme.md" --include "README.md" --exclude-dir ".tox" | xargs sed -i '' "s/dapr\-dev/dapr/g"
grep -rol "dapr\-ext\-workflow\-dev" . --include "setup.cfg" --include "requirements.txt" --exclude-dir ".tox" | xargs sed -i '' "s/dapr\-ext\-workflow\-dev/dapr\-ext\-workflow/g"

We have to do the same for any examples that use dapr-ext-grpc, dapr-ext-fastapi and flask_dapr.

-[x] Version updated from RC version to release version

This command happens to work right now, but be careful not to update packages which didn't get a version bump (like dapr-ext-grpc and dapr-ext-fastapi and flask_dapr)

export OLD="1\.13\.0rc1" && export NEW="1\.13\.0" && grep -rol "$OLD" . --include "version.py" --include "setup.cfg" --include "requirements.txt" --include "Readme.md" --include "README.md" --exclude-dir ".tox" | xargs sed -i '' "s/$OLD/$NEW/"

The release will only occur after we push a tag, but the version used comes from the source files - not the tag.

Different tags trigger releases: workflow-v* like workflow-v0.4.0 triggers the workflow SDK release (this is already released) grpc-v* triggers the dapr-ext-grpcrelease - this is not necessary at this time since we are not releasing this. Same for fastapi-v* and flask-v*.

We only will push the v* style tag (here v1.13.0) for the regular SDK release to be triggered.