Merge pull request #977 from michelleN/release-0.7.0

chore(*): update versions to v0.7.0

Cargo.toml

@@ -7,7 +7,7 @@ license = "Apache-2.0 WITH LLVM-exception"
 rust-version = "1.64"
 
 [workspace.package]
-version = "0.6.0"
+version = "0.7.0"
 authors = [ "Fermyon Engineering <engineering@fermyon.com>" ]
 edition = "2021"
 

docs/content/release-process.md

@@ -3,31 +3,32 @@ template = "spin_main"
 date = "2022-03-14T00:22:56Z"
 [extra]
 url = "https://github.com/fermyon/spin/blob/main/docs/content/release-process.md"
+
 ---
 
 To cut a release of Spin, you will need to do the following:
 
 1. Create a pull request that changes the version number for your new version
- (e.g. `0.6.0` becomes `0.6.1`)
+ (e.g. `0.7.0` becomes `0.7.1`)
  - Bump the version in Spin's `Cargo.toml`
- - Bump the version in the Rust SDK as well (`sdk/rust/Cargo.toml`)
+ - Update SDK_VERSION in `templates/Makefile`
  - Check the docs for hard-coded version strings
 1. Merge the PR created in #1 (Such PRs are still required to get approvals, so
  make sure you get signoff on the PR)
 1. Before proceeding, verify that the merge commit on `main` intended to be
  tagged is green, i.e. CI is successful
-1. Create a new tag with a `v` and then the version number (`v0.6.1`)
-1. The Go SDK tag `sdk/go/v0.6.1` will be created in the [release action].
+1. Create a new tag with a `v` and then the version number (`v0.7.1`)
+1. The Go SDK tag `sdk/go/v0.7.1` will be created in the [release action].
 1. When the [release action] completes, binary artifacts and checksums will be
  automatically uploaded to the GitHub release.
 1. A Pull Request will also be created by `fermybot` containing changes to the
  templates per the updated SDK version. Once CI completes, approve this PR and
  merge via a merge commit. This will trigger the `push-templates-tag` job in
- the [release action], pushing the `spin/templates/v0.6` tag. (Note
+ the [release action], pushing the `spin/templates/v0.7` tag. (Note
  that this tag may be force-pushed for all patch releases of a given minor release.)
 1. Go to the GitHub [tags page](https://github.com/fermyon/spin/releases),
  edit a release, add the release notes.
 
 At this point, you can verify in the GitHub UI that the release was successful.
 
-[release action]: https://github.com/fermyon/spin/actions/workflows/release.yml
+[release action]: https://github.com/fermyon/spin/actions/workflows/release.yml

docs/downloads/install.sh

@@ -28,7 +28,7 @@ print_help() {
  fancy_print 2 "This script installs Spin in the current directory."
  fancy_print 2 ""
  fancy_print 2 "Comand line arguments"
- fancy_print 2 "--version or -v : Provide what version to install e.g. \"v0.6.0\" or \"canary\"."
+ fancy_print 2 "--version or -v : Provide what version to install e.g. \"v0.7.0\" or \"canary\"."
  fancy_print 2 "--help or -h : Shows this help message"
 }
 
@@ -48,7 +48,7 @@ while [[ $# -gt 0 ]]; do
  if [[ $# -ne 0 ]]; then
  VERSION="${1}"
  else
- fancy_print 1 "Please provide the desired version. e.g. --version v0.6.0 or -v canary"
+ fancy_print 1 "Please provide the desired version. e.g. --version v0.7.0 or -v canary"
  exit 0
  fi
  ;;

templates/Makefile

@@ -1,4 +1,4 @@
-SDK_VERSION ?= v0.6.0
+SDK_VERSION ?= v0.7.0
 
 bump-versions: bump-go-versions bump-rust-versions