Skip to content

Latest commit

 

History

History
54 lines (40 loc) · 1.36 KB

RELEASE.md

File metadata and controls

54 lines (40 loc) · 1.36 KB

Here's how to issue a new release.

  1. Bump the version number in uaa_client/__init__.py.

  2. Move the "unreleased" section to a new version entry in CHANGELOG.md.

  3. Run the following to ensure that everything builds and installs OK in an isolated environment:

    rm -rf dist build
    python build
    python test.py manualtest
    

    You should be able to visit http://localhost:8000 and log in as [email protected] without any problems.

  4. Commit and push your changes with a commit message like "Bump version to v1.0.4."

  5. Tag your version and push it to GitHub. For instance, if you're releasing v1.0.4, do:

    git tag -a v1.0.4
    git push origin v1.0.4
    

    When running git tag, you'll be prompted for a tag message. Consider copy-pasting the version notes from CHANGELOG.md for this, as whatever you enter will show up on the GitHub releases page.

  6. If you haven't already done so, create a ~/.pypirc file with the following content:

    [distutils]
    index-servers =
        pypi
    
    [pypi]
    repository: https://www.python.org/pypi
    username: 18f
    password: <your password>
    
  7. Run python -m twine upload dist/*. The new release should now be visible on pypi.