chore: Release rosenpass version 0.2.1

chore: Release rosenpass version 0.2.1-rc.3
refine ab085998bb
2025-12-18 21:34:37 +03:00 · 2023-11-18 23:16:22 +01:00 · 2023-11-18 22:58:57 +01:00 · 2023-11-18 22:57:53 +01:00 · 2023-11-18 22:48:35 +01:00 · 2023-11-18 22:43:47 +01:00
3 changed files with 5 additions and 2 deletions
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -1011,7 +1011,7 @@ checksum = "3582f63211428f83597b51b2ddb88e2a91a9d52d12831f9d08f5e624e8977422"

 [[package]]
 name = "rosenpass"
-version = "0.2.1-rc.1"
+version = "0.2.1"
 dependencies = [
 "anyhow",
 "base64",
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -5,3 +5,6 @@ members = [
    "rosenpass",
 ]

+[workspace.metadata.release]
+# ensure that adding `--package` as argument to `cargo release` still creates version tags in the form of `vx.y.z`
+tag-prefix = ""
--- a/rosenpass/Cargo.toml
+++ b/rosenpass/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "rosenpass"
-version = "0.2.1-rc.1"
+version = "0.2.1"
 authors = ["Karolin Varner <karo@cupdev.net>", "wucke13 <wucke13@gmail.com>"]
 edition = "2021"
 license = "MIT OR Apache-2.0"
Author	SHA1	Message	Date
wucke13	0b4b1279cf	chore: Release rosenpass version 0.2.1	2023-11-18 23:16:22 +01:00
wucke13	44264a7bb6	chore: Release rosenpass version 0.2.1-rc.3	2023-11-18 22:58:57 +01:00
wucke13	b095bdaa7c	refine `ab085998bb` This commit refines the above by making cargo release emit no prefix for release tags even if only a single package is released.	2023-11-18 22:57:53 +01:00
wucke13	9597e485bf	chore: Release rosenpass version 0.2.1-rc.2	2023-11-18 22:48:35 +01:00
wucke13	ab085998bb	add new trigger for release workflow The change to a multi crate cargo workspace makes `cargo release` behave differently. Now it prefixes the release tags (e.g. `v0.2.0`) with the package name, so for example `rosenpass-v0.2.0`. This change adds the	2023-11-18 22:43:47 +01:00