Skip to content

Latest commit

 

History

History
39 lines (24 loc) · 1.21 KB

RELEASES.md

File metadata and controls

39 lines (24 loc) · 1.21 KB
Raw

Release Procedure

Building and releasing integrations is accomplished with GitHub actions where each library or integration has its own workflow.

For example, the dagster-contrib-modal integration has a workflow defined at .github/workflows/release-dagster-contrib-modal.yml.

Releases are triggered by creating a git tag of the pattern <integration-name>-X.X.X. For example:

git tag dagster_modal-0.1.3
git push origin dagster_modal-0.1.3

Where the tag must match the prefix of the files generated in the dist/ folder:

ls libraries/dagster-contrib-modal/dist/

total 16
-rw-r--r--@ 2.0K Oct 23 14:06 dagster_modal-0.0.1-py3-none-any.whl
-rw-r--r--@ 1.6K Oct 23 14:06 dagster_modal-0.0.1.tar.gz

Variables

The GitHub action uses the uv deploy command, and requires the UV_PUBLISH_TOKEN and UV_PUBLISH_URL variables to be set.

For production deployment, UV_PUBLISH_URL must be set to:

  • https://upload.pypi.org/legacy/

For test deployments, it can be set to:

  • https://test.pypi.org/simple/

Maintainers are to ensure the variables are present in the production environment of the repository settings.