From e39678d081bc266f15fdd0c87abdcc53a9be8fd9 Mon Sep 17 00:00:00 2001 From: Brian Hardock Date: Tue, 26 Aug 2025 14:26:26 -0600 Subject: [PATCH] Bump version for v0.4.0 release Signed-off-by: Brian Hardock --- Cargo.lock | 4 ++-- Cargo.toml | 4 ++-- release-process.md | 10 +++++----- spin-pluginify.toml | 2 +- 4 files changed, 10 insertions(+), 10 deletions(-) diff --git a/Cargo.lock b/Cargo.lock index 2658e2d..dc19d65 100644 --- a/Cargo.lock +++ b/Cargo.lock @@ -1,6 +1,6 @@ # This file is automatically @generated by Cargo. # It is not intended for manual editing. -version = 3 +version = 4 [[package]] name = "addr2line" @@ -5851,7 +5851,7 @@ dependencies = [ [[package]] name = "trigger-command" -version = "0.3.2" +version = "0.4.0" dependencies = [ "anyhow", "clap", diff --git a/Cargo.toml b/Cargo.toml index 74833b7..d3a919c 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -3,10 +3,10 @@ name = "trigger-command" version = { workspace = true } authors = { workspace = true } edition = { workspace = true } -rust-version = "1.81" +rust-version = "1.86" [workspace.package] -version = "0.3.2" +version = "0.4.0" authors = ["Radu Matei "] edition = "2021" diff --git a/release-process.md b/release-process.md index 2175564..e544d63 100644 --- a/release-process.md +++ b/release-process.md @@ -2,7 +2,7 @@ To cut a new release of the command trigger plugin, you will need to do the following: -1. Confirm that [CI is green](https://fermyon/spin-trigger-command/actions) for the commit selected to be tagged and released. +1. Confirm that [CI is green](https://github.com/spinframework/spin-trigger-command/actions) for the commit selected to be tagged and released. 1. Change the version number in [Cargo.toml](./Cargo.toml) and [spin-pluginify.toml](./spin-pluginify.toml) and run `cargo build --release`. @@ -18,15 +18,15 @@ To cut a new release of the command trigger plugin, you will need to do the foll # Create a GPG-signed and annotated tag git tag -s -m "Spin Command Trigger v0.1.0" v0.1.0 - # Push the tag to the remote corresponding to fermyon/spin-trigger-command (here 'origin') + # Push the tag to the remote corresponding to spinframework/spin-trigger-command (here 'origin') git push origin v0.1.0 ``` -1. Pushing the tag upstream will trigger the [release action](https://github.com/fermyon/spin-trigger-command/actions/workflows/release.yml). +1. Pushing the tag upstream will trigger the [release action](https://github.com/spinframework/spin-trigger-command/actions/workflows/release.yml). - The release build will create the packaged versions of the plugin, the updated plugin manifest and a checksums file - These assets are uploaded to a new GitHub release for the pushed tag - Release notes are auto-generated but edit as needed especially around breaking changes or other notable items -1. Create a PR in the [fermyon/spin-plugins](https://github.com/fermyon/spin-plugins) repository with the [updated manifest](https://github.com/fermyon/spin-plugins/tree/main/manifests/command-trigger). +1. Create a PR in the [spinframework/spin-plugins](https://github.com/spinframework/spin-plugins) repository with the [updated manifest](https://github.com/spinframework/spin-plugins/tree/main/manifests/command-trigger). -1. If applicable, create PR(s) or coordinate [documentation](https://github.com/fermyon/developer) needs, e.g. for new features or updated functionality. \ No newline at end of file +1. If applicable, create PR(s) or coordinate [documentation](https://github.com/spinframework/spin-docs) needs, e.g. for new features or updated functionality. \ No newline at end of file diff --git a/spin-pluginify.toml b/spin-pluginify.toml index 011da26..abb916c 100644 --- a/spin-pluginify.toml +++ b/spin-pluginify.toml @@ -1,6 +1,6 @@ name = "trigger-command" description = "A Spin trigger that executes the WASI main function of a component." -version = "0.3.2" +version = "0.4.0" spin_compatibility = ">=2.0" license = "Apache-2.0" package = "./target/release/trigger-command"