Skip to content

Latest commit

 

History

History
18 lines (14 loc) · 1.21 KB

RELEASE_PROCESS.md

File metadata and controls

18 lines (14 loc) · 1.21 KB
Raw

Release process

  1. If the REST API docs changed: Run /scripts/build_rest_api_docs.py and commit the result.

  2. Add release notes to docs/whatsnew.rst

  3. Create a new release with tag and name (no leading v): x.x.x

    This kicks off the appveyor pipeline that will:

    • Build the dlls, the xlwings.xlam, the standalone files and xlwings.bas (they depend on the version number) and the Python package
    • Upload the Python package to pypi and xlwings.xlam to the GitHub release page
    • Trigger a rebuild of https://www.xlwings.org so it is updated with latest version/date

  4. readthedocs.org is triggering a rebuild of the latest (i.e. master) docs with every commit, but sadly it seems to fail to do so for the stable version i.e. tagged/released version, so for now login to readthedocs (using GH account) and build the stable version manually.

  5. The conda-forge package seems to automatically create a PR these days shortly after uploading the package to pypi, so the only tasks left here is to check back after a few hours and merge it if all build pipelines built successfully.