bump version 0.7.0dev

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. <[email protected]>"]

release_checklist.rst

@@ -1,9 +1,13 @@
-* 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
+* Update the version check in test_metadata.py
 * Revert to released version of dpf core in the pyproject.toml file
+* Update lock file: poetry lock
 * 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.
+* on the main branch, bump the version in the pyproject.toml file to the next dev version and commit

tests/test_metadata.py

@@ -24,4 +24,4 @@
 
 
 def test_pkg_version():
-    assert __version__ == "0.6.dev0"
+    assert __version__ == "0.7.dev0"