Skip to content
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.

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

Move version from YYYY.0M.MICRO to YYYY.MINOR.MICRO #1089

Merged
merged 3 commits into from
Feb 8, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion core/Project.toml
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@ name = "Ribasim"
uuid = "aac5e3d9-0b8f-4d4f-8241-b1a7a9632635"
authors = ["Deltares and contributors <ribasim.info@deltares.nl>"]
manifest = "../Manifest.toml"
version = "2024.02.0"
version = "2024.2.0"

[deps]
Accessors = "7d9f7c33-5ae7-4f3b-8dc6-eff91059b697"
Expand Down
6 changes: 3 additions & 3 deletions docs/contribute/release.qmd
Original file line number Diff line number Diff line change
Expand Up @@ -21,8 +21,8 @@ Before starting the release process, ensure that all tests are passing and that

## Update version numbers of the components

Determine the new version number like `2023.08.0`, filling in the current year, month and a sequential "MICRO" number.
This follows `YYYY.0M.MICRO` from [calver](https://calver.org/).
Determine the new version number like `2023.1.0`, filling in the current year, a bumped `MINOR` number for normal releases and a bumped `MICRO` number for non-breaking, hotfix releases.
This follows `YYYY.MINOR.MICRO` from [calver](https://calver.org/).

Update the version numbers in the repository to the new version number.
A single find and replace can update all 5 locations:
Expand All @@ -39,7 +39,7 @@ Now submit a pull request to update the version numbers.

When the pull request is merged to main, checkout the commit that updates the version numbers.

Create a new tag, which is the letter `v` followed by the version number, like, `v2023.08.0`.
Create a new tag, which is the letter `v` followed by the version number, like, `v2023.8.0`.

This can be done by executing:
```bash
Expand Down
2 changes: 1 addition & 1 deletion pixi.toml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[project]
name = "Ribasim"
version = "2024.02.0"
version = "2024.2.0"
description = "Water resources modeling"
authors = ["Deltares and contributors <ribasim.info@deltares.nl>"]
channels = ["conda-forge"]
Expand Down
2 changes: 1 addition & 1 deletion python/ribasim/ribasim/__init__.py
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
__version__ = "2024.02.0"
__version__ = "2024.2.0"


from ribasim import models, utils
Expand Down
2 changes: 1 addition & 1 deletion python/ribasim_api/ribasim_api/__init__.py
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
__version__ = "2024.02.0"
__version__ = "2024.2.0"

from ribasim_api.ribasim_api import RibasimApi

Expand Down
2 changes: 1 addition & 1 deletion ribasim_qgis/metadata.txt
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@
name=Ribasim-QGIS
qgisMinimumVersion=3.0
description=QGIS plugin to setup Ribasim models
version=2024.02.1
version=2024.2.0
author=Deltares and contributors
email=ribasim.info@deltares.nl

Expand Down
Loading