Skip to content

Close up release process #511

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
SKernchen merged 2 commits into from
Sep 7, 2026
Merged

Close up release process #511

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
be80ec5
Close up release process
SKernchen Sep 4, 2026
20b0dc6
Changed wording
SKernchen Sep 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions CITATION.cff
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
10 changes: 6 additions & 4 deletions docs/source/dev/releasing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <rule>`. See also [Poetry Docs](https://python-poetry.org/docs/cli/#version)
2. Merge and delete the release `release/v<version>` branch.
2. Merge the release `release/v<version>` 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`.
Expand All @@ -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 `<major>.<minor+1>.0.dev0` in another pull request.
5. On `develop`:

@zyzzyxdonta zyzzyxdonta Sep 4, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should say something like

Using a pull request from release/v<version>, update develop:

Right?

@SKernchen SKernchen Sep 7, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes I adapted it

1. Update the version in `pyproject.toml` to `<major>.<minor+1>.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 "<major>.<minor+1>.0.dev0"`
- Manually edit the file with an editor.
- Use `poetry version "<major>.<minor+1>.0.dev0"`
2. Append in `CITATION.cff` the new identifier to `identifiers` (if postprocess did not do it)
2 changes: 1 addition & 1 deletion pyproject.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 = [
Expand Down
Loading