Skip to content

Release Instructions

Jump to bottom
Varad Meru edited this page May 1, 2020 · 32 revisions

Release Instructions

Please follow these steps in order to make a release:

[ ] Ensure that buildbots in the dev branch are green. 2. Increase the version field in azure.functions.__init__.py. 3. Push the commit with the new version to the dev branch. 4. Make a TestPyPi release from the dev branch, this will be used in azure-functions-worker E2E test:

$ rm dist/*
$ python setup.py sdist bdist_wheel
$ twine upload --repository-url https://test.pypi.org/legacy/ dist/*

Twine is a PyPi upload tool that can be installed with pip

Wheel is used for generating bdist_wheel on packaging

$ pip install twine wheel

You may need to setup ~/.pypirc file for your test.pypi credentials. (Instruction Here) 5. Wait for the azure-functions-worker E2E to run with the new azure-functions library on test.pypi.

  • You can do this by creating a new worker release commit PR (e.g. updating the version field in setup.py).
  • Create a PR against this new version in Python Worker.
  • The E2E test will pick up the latest library change in TestPyPi.

  1. Push the version update commit to the master branch

  2. Tag the latest master branch commit with the version number (e.g. v1.1.0)

  3. Create a GitHub release according to the tag with the release note in it.

  4. Make an official PyPi release:

    $ rm dist/*
$ python setup.py sdist bdist_wheel
$ twine upload dist/*

Continue releasing the worker

  1. Change the azure-functions version in the worker repo and create a PR to the worker dev branch (e.g. Sample PR)
  2. Ensure that buildbots are green for step 4 (tests are currently coupled between the worker and library repos)
Clone this wiki locally