From 4fb4b1547554d310f1f47d0f9aa84c717904082e Mon Sep 17 00:00:00 2001 From: Andrey Kononykhin Date: Mon, 18 Oct 2021 17:23:49 +0300 Subject: [PATCH 1/2] bumps version to 0.5.0 Signed-off-by: Andrey Kononykhin --- peerdid/__init__.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/peerdid/__init__.py b/peerdid/__init__.py index 6a9beea..3d18726 100644 --- a/peerdid/__init__.py +++ b/peerdid/__init__.py @@ -1 +1 @@ -__version__ = "0.4.0" +__version__ = "0.5.0" From ef1476eb6de2b44114599232861407eef5450f4f Mon Sep 17 00:00:00 2001 From: Andrey Kononykhin Date: Mon, 18 Oct 2021 17:24:35 +0300 Subject: [PATCH 2/2] adds release docs Signed-off-by: Andrey Kononykhin --- docs/release.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 docs/release.md diff --git a/docs/release.md b/docs/release.md new file mode 100644 index 0000000..4095040 --- /dev/null +++ b/docs/release.md @@ -0,0 +1,14 @@ +## Release + +Assumptions: + +* `main` branch can wait until release PR is merged + +The steps: + +1. **release**: + 1. **review adjust if needed the release version in `main`** to match the changes from the latest release following the [SemVer rules](https://semver.org/#summary). + 2. [create](https://github.com/sicpa-dlab/peer-did-python/compare/stable...main) a **PR from `main` to `stable`** (you may likely want to name it as `release-`) + 3. once merged [release pipeline](https://github.com/sicpa-dlab/peer-did-python/actions/workflows/release.yml) will publish the release to [PyPI](https://pypi.org/project/peerdid) +2. **bump next release version in `main`** + * **Note** decision about the next release version should be based on the same [SemVer](https://semver.org/) rules and the expected changes. Usually it would be either a MINOR or MAJOR (if incompatible changes are planned) release.