Skip to content

Latest commit

 

History

History
16 lines (12 loc) · 1011 Bytes

RELEASE_PROCESS.md

File metadata and controls

16 lines (12 loc) · 1011 Bytes

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 GitHub actions 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 triggers a new build automatically (login with GH account)

  5. The conda-forge package automatically creates a PR 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 pipelines built successfully.