Release packages (#1518)

> [!IMPORTANT]
> Merging this pull request will create these releases

# knope 0.21.3 (2025-08-16)
## Fixes

### Fix pre-release versioning when there are no previous stable
versions

Previously, if there was not a Git tag containing a previous stable
version, Knope would default to "0.0.0".
Because of the special 1.0.0 rules, this also meant there was _no_ way
to start a project at a pre-release of 1.0.0
with no prior releases.

Now, if there are no previous stable releases, Knope will use the
version in your files instead of calculating a version
based on "0.0.0".

Fixes #1515, thanks for the report @hazre!
# versioning 0.5.2 (2025-08-16)
## Fixes

### Fix pre-release versioning when there are no previous stable
versions

Previously, if there was not a Git tag containing a previous stable
version, Knope would default to "0.0.0".
Because of the special 1.0.0 rules, this also meant there was _no_ way
to start a project at a pre-release of 1.0.0
with no prior releases.

Now, if there are no previous stable releases, Knope will use the
version in your files instead of calculating a version
based on "0.0.0".

Fixes #1515, thanks for the report @hazre!

Co-authored-by: knope-bot-test[bot] <150975753+knope-bot-test[bot]@users.noreply.github.com>

Author: knope-bot-test[bot]

.changeset/fix_pre_release_versioning_when_there_are_no_previous_stable_versions.md

@@ -10,6 +10,21 @@ The results are changes to the current directory, calls to external commands, an
 Notably, anything written to standard output or standard error
 (what you see in the terminal) is _not_ considered part of the public API and may change between any versions.
 
+## 0.21.3 (2025-08-16)
+
+### Fixes
+
+#### Fix pre-release versioning when there are no previous stable versions
+
+Previously, if there was not a Git tag containing a previous stable version, Knope would default to "0.0.0".
+Because of the special 1.0.0 rules, this also meant there was _no_ way to start a project at a pre-release of 1.0.0
+with no prior releases.
+
+Now, if there are no previous stable releases, Knope will use the version in your files instead of calculating a version
+based on "0.0.0".
+
+Fixes #1515, thanks for the report @hazre!
+
 ## 0.21.2 (2025-08-10)
 
 ### Features

CHANGELOG.md

@@ -10,7 +10,7 @@ strip = true
 changesets = "0.4.0"
 indexmap = { version = "2", features = ["serde"] }
 itertools = "0.14.0"
-knope-versioning = { path = "crates/knope-versioning", version = "0.5.1" }
+knope-versioning = { path = "crates/knope-versioning", version = "0.5.2" }
 miette = "7.2.0"
 relative-path = { version = "2.0.0", features = ["serde"] }
 serde = { version = "1.0.200", features = ["derive"] }

Cargo.lock

@@ -1,3 +1,18 @@
+## 0.5.2 (2025-08-16)
+
+### Fixes
+
+#### Fix pre-release versioning when there are no previous stable versions
+
+Previously, if there was not a Git tag containing a previous stable version, Knope would default to "0.0.0".
+Because of the special 1.0.0 rules, this also meant there was _no_ way to start a project at a pre-release of 1.0.0
+with no prior releases.
+
+Now, if there are no previous stable releases, Knope will use the version in your files instead of calculating a version
+based on "0.0.0".
+
+Fixes #1515, thanks for the report @hazre!
+
 ## 0.5.1 (2025-08-10)
 
 ### Features

Cargo.toml

@@ -1,7 +1,7 @@
 [package]
 name = "knope-versioning"
 description = "A library for handling all the versioned files supported by Knope"
-version = "0.5.1"
+version = "0.5.2"
 authors = ["Dylan Anthony <[email protected]>"]
 edition = "2024"
 license = "MIT"

crates/knope-versioning/CHANGELOG.md

@@ -1,7 +1,7 @@
 [package]
 name = "knope"
 description = "A command line tool for automating common development tasks"
-version = "0.21.2"
+version = "0.21.3"
 authors = ["Dylan Anthony <[email protected]>"]
 edition = "2024"
 license = "MIT"