From be80ec59cf6c3ef64c2958b5da09dc5707ec8eb9 Mon Sep 17 00:00:00 2001 From: "Kernchen, Sophie" Date: Fri, 4 Sep 2026 16:32:59 +0200 Subject: [PATCH 1/2] Close up release process --- CITATION.cff | 6 ++++++ docs/source/dev/releasing.md | 10 ++++++---- pyproject.toml | 2 +- 3 files changed, 13 insertions(+), 5 deletions(-) diff --git a/CITATION.cff b/CITATION.cff index 223d4bb8..dca3918b 100644 --- a/CITATION.cff +++ b/CITATION.cff @@ -73,3 +73,9 @@ identifiers: - type: doi value: 10.5281/zenodo.21643617 description: Version 0.9.1 + - type: doi + value: 10.5281/zenodo.22303781 + description: Version 0.9.2 + - type: doi + value: 10.5281/zenodo.22306252 + description: Version 0.10.0 diff --git a/docs/source/dev/releasing.md b/docs/source/dev/releasing.md index dc2bcf6e..8db5959e 100644 --- a/docs/source/dev/releasing.md +++ b/docs/source/dev/releasing.md @@ -10,7 +10,7 @@ To release a new version of HERMES when a new set of features and/or fixes have To edit the version in `pyproject.toml`, there are two ways: - Manually edit the file with an editor. - Use `poetry version `. See also [Poetry Docs](https://python-poetry.org/docs/cli/#version) -2. Merge and delete the release `release/v` branch. +2. Merge the release `release/v` branch, you can keep the branch for updating `develop` later again. 2. Create a pull request from `develop` to `main`. 3. Check if all the CI pipelines for that PR succeed. 3. Let the named maintainer (see GOVERNANCE.md) merge the PR into `main`. @@ -22,7 +22,9 @@ To release a new version of HERMES when a new set of features and/or fixes have - Publish the release. Note: this will also ensure usage of *annotated* tags, making Software Heritage archive the release. -5. On `develop`, update the version in `pyproject.toml` to `..0.dev0` in another pull request. +5. On `develop`: + 1. Update the version in `pyproject.toml` to `..0.dev0` in another pull request. To edit the version, you can use two ways: - - Manually edit the file with an editor. - - Use `poetry version "..0.dev0"` + - Manually edit the file with an editor. + - Use `poetry version "..0.dev0"` + 2. Append in `CITATION.cff` the new identifier to `identifiers` (if postprocess did not do it) diff --git a/pyproject.toml b/pyproject.toml index a425799c..be550151 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -8,7 +8,7 @@ [project] name = "hermes" -version = "0.10.0" +version = "0.11.0.dev0" description = "Workflow to publish research software with rich metadata" license = "Apache-2.0 AND LicenseRef-BSD-Caltech" authors = [ From 20b0dc6063a7f63611eecfcb98fe48a70bac0ddf Mon Sep 17 00:00:00 2001 From: "Kernchen, Sophie" Date: Mon, 7 Sep 2026 12:26:16 +0200 Subject: [PATCH 2/2] Changed wording --- docs/source/dev/releasing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/dev/releasing.md b/docs/source/dev/releasing.md index 8db5959e..59b37d09 100644 --- a/docs/source/dev/releasing.md +++ b/docs/source/dev/releasing.md @@ -22,7 +22,7 @@ To release a new version of HERMES when a new set of features and/or fixes have - Publish the release. Note: this will also ensure usage of *annotated* tags, making Software Heritage archive the release. -5. On `develop`: +5. Using a pull request from release/v, update develop: 1. Update the version in `pyproject.toml` to `..0.dev0` in another pull request. To edit the version, you can use two ways: - Manually edit the file with an editor.