From 4374ee73f087a38ed1a939abef2a2d3caa6b6215 Mon Sep 17 00:00:00 2001 From: Richard Bruskiewich Date: Fri, 1 Sep 2023 12:23:29 -0700 Subject: [PATCH] ditto --- DEVELOPER_NOTES.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/DEVELOPER_NOTES.md b/DEVELOPER_NOTES.md index 5d25400..6b0d580 100644 --- a/DEVELOPER_NOTES.md +++ b/DEVELOPER_NOTES.md @@ -34,5 +34,5 @@ Steps to properly issue a new project release: 8. Add the equivalent Git **tag** to **master**. This should be the Semantic Version string from step 4 with an added 'v' prefix, i.e. "v3.8.9". 9. Push **master** to remote (if not already done with by a pull request in step 6). 10. Check if Git Actions for testing and documentation complete successfully. -11. Create the release using the same release tag, i.e. "v3.8.3". -12. Check if Git Action for package deployment is successful and check if the new version (i.e. "3.8.3") is now visible on **[pypy.org](https://pypi.org/search/?q=reasoner-validator)** +11. Create the release using the same release tag, i.e. "v3.8.9". +12. Check if Git Action for package deployment is successful and check if the new version (i.e. "3.8.9") is now visible on **[pypy.org](https://pypi.org/search/?q=reasoner-validator)**