Skip to content
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
75 lines (47 sloc) 3.03 KB

Versioning guidelines

Dagster versions follow the guidelines in PEP 440.

To make dependency management easier in the context of a monorepo with many installable projects, package versions move in lockstep with each other and with git tags.

As the API is still in flux, we aren't following strict semantic versioning rules at this point, but roughly intend micro versions to reflect a regular release schedule and minor versions to reflect milestones in the framework's capabilities and the maturity of its internals.

Breaking API changes should be recorded in CHANGELOG.rst.

You must have wheel and twine installed.

Releasing a new version

Our release automation tools are contained in bin/ These tools are smart enough to guard against some kinds of mistakes, but could and should be smarter. Generally speaking, it's preferable to invest in these tools rather than to complicate the release process.

Run a pre-release before releasing a new version: it's good practice to run the release process for a pre-release version before releasing a new version, i.e., first for version 0.3.0.pre0, and then for version 0.3.0 only when you know that the process is going to succeed without issues. This ensures a clean release history.

WARNING: Keep in mind that there is no undo in some of the third-party systems (e.g., PyPI) we use to release software.

You should also run releases from a clean clone of the repository. This is to guard against any issues that might be introduced by local build artifacts.

  1. Check that you are on master, that there are no local changes or changes on the remote, and that you are at the root of the repository.

  2. Check that the current version of the projects is consistent and what you expect by running:

     python bin/ version
  3. Create a new release by running (e.g., for version 0.4.3.pre0):

     python bin/ release 0.4.3.pre0
  4. Check that the new version has been created successfully by again running:

     python bin/ version
  5. Push the new version to the remote. The new version tag will trigger a ReadTheDocs build.

     git push && git push origin 0.4.3.pre0
  6. Publish the new version to PyPI. Note that you must have PyPI credentials available to twine (see below), and you must be permissioned as a maintainer on the projects.

     python bin/ publish
  7. Manually switch the default ReadTheDocs version to the newly built docs:

    The new version will be below in the "Inactive Versions" section.

  8. Check that the ReadTheDocs and PyPI versions are as you expect.

PyPI credentials

Credentials must be available to twine in order to publish to PyPI. The best way to do this is with a ~/.pypirc file in the following format:

index-servers = pypi

username: <username>
password: <password>
You can’t perform that action at this time.