From 82c11806c51424e432a81bf6efba8de7ff4b1edb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ren=C3=A9=20Roos?= Date: Wed, 14 Aug 2024 16:37:39 +0200 Subject: [PATCH] bump version 0.7.0dev --- pyproject.toml | 2 +- release_checklist.rst | 3 ++- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/pyproject.toml b/pyproject.toml index 9d19c77fe..4c5212a87 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -6,7 +6,7 @@ build-backend = "poetry.core.masonry.api" # Check https://python-poetry.org/docs/pyproject/ for all available sections name = "ansys-dpf-composites" # Switch to released version of dpf core releasing pydpf-composites! -version = "0.6.dev0" +version = "0.7.dev0" description = "Post-processing of composite structures based on Ansys DPF" license = "MIT" authors = ["ANSYS, Inc. "] diff --git a/release_checklist.rst b/release_checklist.rst index ec39f5cf9..3488e0655 100644 --- a/release_checklist.rst +++ b/release_checklist.rst @@ -1,9 +1,10 @@ -* Check the release_checklist in the dpf_composites repo +* Check the README_release_new_version in the dpf_composites repo * As soon as the docker image with the version tag is available, add explicit tests for the new version. This should happen when a release branch is created for normal releases and once the image is tagged manually for pre-releases. * Add docker pull for the container with the new version tag in ci_cd.yml * Add pytest run for the new version in tox.ini * Update the compatibility in the docs: intro.rst / Compatibility +* Update the version of THIS package in the pyproject.toml file * Revert to released version of dpf core in the pyproject.toml file * Follow this guide (https://dev.docs.pyansys.com/how-to/releasing.html) to create a release branch and release. Also bump version in test_metadata.py test.