diff --git a/CHANGELOG.md b/CHANGELOG.md index b2a8d02..78c318f 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,6 +2,10 @@ ## [Unreleased] +## 0.2.0 + +Date: 2024-06-24 + - 💄📯 — Improve notifications and result(s) pages - 🔊 — Add level of log before the log message — 🔊 — Add a warning messages in the logs if there is no tasks in database. (fix #41) diff --git a/argos/__init__.py b/argos/__init__.py index 7d7c7c3..6c5007c 100644 --- a/argos/__init__.py +++ b/argos/__init__.py @@ -1 +1 @@ -VERSION = "0.1.1" +VERSION = "0.2.0" diff --git a/docs/developer/release.md b/docs/developer/release.md index 0a3500e..db780cc 100644 --- a/docs/developer/release.md +++ b/docs/developer/release.md @@ -26,6 +26,13 @@ make test # Bump the version, according to semantic versionning hatch version minor # or `hatch version major` +# Modify the changelog +editor CHANGELOG.md + +# Commit the change +git add argos/__init__.py CHANGELOG +git commit -m "🏷 — Bump version ($(hatch version))" + # Create a tag on the git repository and push it git tag "$(hatch version)" && git push @@ -38,6 +45,9 @@ hatch publish Aditionnaly, ensure it works well in a new environment. +Then go to https://framagit.org/framasoft/framaspace/argos/-/releases to create a new release for the new tag. +Use CHANGELOG.md content for that. + ## Bumping the version number We follow semantic versionning conventions, and the version is specified in the `argos.__init__.py` file.