Releasing 0.1.5

Author: ifeoluwaale

.github/workflows/create_git_release.yml

@@ -6,7 +6,7 @@ on:
     types:
       - completed
     branches:
-      - v0.1.4
+      - v0.1.5
 
 jobs:
   publish:
@@ -17,7 +17,7 @@ jobs:
       - name: Checkout source
         uses: actions/checkout@v3
         with:
-          ref: v0.1.4
+          ref: v0.1.5
       - name: Set up Python 3.11
         uses: actions/setup-python@v4
         with:
@@ -31,3 +31,15 @@ jobs:
         with:
           user: __token__
           password: ${{ secrets.DPLPY_PYPI }}
+      - name: Create Release
+        id: create_release
+        uses: actions/create-release@v1
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} # This token is provided by Actions, you do not need to create your own token
+        with:
+          tag_name: v0.1.5
+          release_name: v0.1.5
+          body: |
+            Testing auto deployment to pypi and git.
+          draft: false
+          prerelease: true

.github/workflows/pypi_release.yml

@@ -2,7 +2,7 @@
 
 __author__ = "Tyson Lee Swetnam"
 __email__ = "[email protected]"
-__version__ = "0.1.4"
+__version__ = "0.1.5"
 
 __copyright__ = """
    dplPy for tree ring width time series analyses

dplpy/__init__.py

@@ -9,7 +9,7 @@ build-backend = "setuptools.build_meta"
 name="dplpy"
 description="Dendrochronology Program Library for Python"
 readme="README.md"
-version="0.1.4"
+version="0.1.5"
 authors=[
     {name='Tyson Lee Swetnam', email='[email protected]'},
     {name='Ifeoluwa Ale', email='[email protected]'},

pyproject.toml

@@ -9,6 +9,4 @@ In the main branch of the dplpy github repository, update the following files in
 - In the `pyproject.toml` file, update the version number in the `[project]` section to match the new version number set in `__init__.py`.
 - In the `.github/workflows` folder, find `pypi_release.yml` and update the branch name for the workflow to run in to v + the new version number(i.e., v0.1.1 if the version number is 0.1.1).
 - Still in `pypi_release.yml`, ensure that the first step of the workflow uses code from the branch name you just set the workflow to run in (which should be named v + the version number).
-- In the `.github/workflows` folder, find `create_git_release.yml` and update the `branches` field of the workflow_run trigger to v + the new version number (e.g., v0.1.1 if the version number is 0.1.1).
-- Still in `create_git_release.yml`, update the name of the tag being created to v + the new version number, and change the release name to the new version number.
-- Still in `create_git_release.yml`, update the description of the git release using the `body` field located under the tag name and release name. You can also set the release as a draft or prerelease using the remaining fields.
+- Still in `pypi_release.yml`, update the name of the tag being created in the create release step to v + the new version number, and change the release name to the new version number. Finally, update the description of the git release using the `body` field located under the tag name and release name. You can also set the release as a draft or prerelease using the remaining fields.