none
This page documents details of the cmake-format release process.
- Push release candidate to the staging branch
- travis will build and test the commit and then push the
pseudo-staging
tag - travis will build and test the commit, and will also create a new
psuedo-staging
release (see here), pushing the binary artifacts (wheel, vsix, etc). Travis will also push a new commit to thecmake-format-rtd
repository (link) under thestaging
branch. - read-the-docs will build the documentation under the
staging
version, with status here and result here - Download and install the python wheel and vsix packages. Test them manually to make sure everything looks good.
- Push the same commit with that modification to the
master
branch. The same pipeline as above will execute. Double check there are no errors
- Add one commit on top of the
HEAD
of master, removing thedev#
version suffix. Push to a tag. - The same pipeline above will execute, but this time the artifacts will belong to the real realease number. The release message text will be taken from the release notes document.
- Download the python source and wheel distributions and vsix packages.
Push the python packages to test.pypi.org with:
twine upload -r test cmake-format.*
- Push the python packages to
pypi.org
withtwine upload cmake-format.*
Push the vscode package with:
vsce publish --baseImagesUrl \ https://raw.githubusercontent.com/cheshirekow/cmakelang/master/cmakelang/vscode_extension