Skip to content

Commit e39678d

Browse files
committed
Bump version for v0.4.0 release
Signed-off-by: Brian Hardock <[email protected]>
1 parent 8fdcfa1 commit e39678d

File tree

4 files changed

+10
-10
lines changed

4 files changed

+10
-10
lines changed

Cargo.lock

Lines changed: 2 additions & 2 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

Cargo.toml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,10 +3,10 @@ name = "trigger-command"
33
version = { workspace = true }
44
authors = { workspace = true }
55
edition = { workspace = true }
6-
rust-version = "1.81"
6+
rust-version = "1.86"
77

88
[workspace.package]
9-
version = "0.3.2"
9+
version = "0.4.0"
1010
authors = ["Radu Matei <[email protected]>"]
1111
edition = "2021"
1212

release-process.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
To cut a new release of the command trigger plugin, you will need to do the following:
44

5-
1. Confirm that [CI is green](https://fermyon/spin-trigger-command/actions) for the commit selected to be tagged and released.
5+
1. Confirm that [CI is green](https://github.com/spinframework/spin-trigger-command/actions) for the commit selected to be tagged and released.
66

77
1. Change the version number in [Cargo.toml](./Cargo.toml) and [spin-pluginify.toml](./spin-pluginify.toml) and run `cargo build --release`.
88

@@ -18,15 +18,15 @@ To cut a new release of the command trigger plugin, you will need to do the foll
1818
# Create a GPG-signed and annotated tag
1919
git tag -s -m "Spin Command Trigger v0.1.0" v0.1.0
2020
21-
# Push the tag to the remote corresponding to fermyon/spin-trigger-command (here 'origin')
21+
# Push the tag to the remote corresponding to spinframework/spin-trigger-command (here 'origin')
2222
git push origin v0.1.0
2323
```
2424
25-
1. Pushing the tag upstream will trigger the [release action](https://github.com/fermyon/spin-trigger-command/actions/workflows/release.yml).
25+
1. Pushing the tag upstream will trigger the [release action](https://github.com/spinframework/spin-trigger-command/actions/workflows/release.yml).
2626
- The release build will create the packaged versions of the plugin, the updated plugin manifest and a checksums file
2727
- These assets are uploaded to a new GitHub release for the pushed tag
2828
- Release notes are auto-generated but edit as needed especially around breaking changes or other notable items
2929
30-
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).
30+
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).
3131
32-
1. If applicable, create PR(s) or coordinate [documentation](https://github.com/fermyon/developer) needs, e.g. for new features or updated functionality.
32+
1. If applicable, create PR(s) or coordinate [documentation](https://github.com/spinframework/spin-docs) needs, e.g. for new features or updated functionality.

spin-pluginify.toml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
name = "trigger-command"
22
description = "A Spin trigger that executes the WASI main function of a component."
3-
version = "0.3.2"
3+
version = "0.4.0"
44
spin_compatibility = ">=2.0"
55
license = "Apache-2.0"
66
package = "./target/release/trigger-command"

0 commit comments

Comments
 (0)