getting-started: update tinygo version number for upcoming release

Signed-off-by: deadprogram <ron@hybridgroup.com>

Author: deadprogram

content/getting-started/linux.md

@@ -28,15 +28,15 @@ You must have Go already installed on your machine in order to install TinyGo. W
 If you are using Ubuntu or another Debian based Linux on an Intel processor, download the DEB file from Github and install it using the following commands:
 
 ```shell
-wget https://github.com/tinygo-org/tinygo/releases/download/v0.14.1/tinygo_0.14.1_amd64.deb
-sudo dpkg -i tinygo_0.14.1_amd64.deb
+wget https://github.com/tinygo-org/tinygo/releases/download/v0.15.0/tinygo_0.15.0_amd64.deb
+sudo dpkg -i tinygo_0.15.0_amd64.deb
 ```
 
 If you are on a Raspberry Pi or other ARM-based Linux computer, you should use this command instead:
 
 ```shell
-wget https://github.com/tinygo-org/tinygo/releases/download/v0.14.1/tinygo_0.14.1_arm.deb
-sudo dpkg -i tinygo_0.14.1_arm.deb
+wget https://github.com/tinygo-org/tinygo/releases/download/v0.15.0/tinygo_0.15.0_arm.deb
+sudo dpkg -i tinygo_0.15.0_arm.deb
 ```
 
 You will need to ensure that the path to the `tinygo` executable file is in your `PATH` variable.
@@ -49,7 +49,7 @@ You can test that the installation is working properly by running this code whic
 
 ```shell
 $ tinygo version
-tinygo version 0.14.1 linux/amd64 (using go version go1.15 and LLVM version 10.0.1)
+tinygo version 0.15.0 linux/amd64 (using go version go1.15 and LLVM version 10.0.1)
 ```
 
 If you are only interested in compiling TinyGo code for WebAssembly then you are now done with the installation.
@@ -212,7 +212,7 @@ This results in a `tinygo` binary in the `build` directory:
 
 ```shell
 $ ./build/tinygo version
-tinygo version 0.14.1 linux/amd64 (using go version go1.15 and LLVM version 10.0.1)
+tinygo version 0.15.0 linux/amd64 (using go version go1.15 and LLVM version 10.0.1)
 ```
 
 ### Additional Requirements for Microcontrollers

content/getting-started/macos.md

@@ -28,7 +28,7 @@ You can test that the installation is working properly by running this code whic
 
 ```shell
 $ tinygo version
-tinygo version 0.14.1 darwin/amd64 (using go version go1.15 and LLVM version 10.0.1)
+tinygo version 0.15.0 darwin/amd64 (using go version go1.15 and LLVM version 10.0.1)
 ```
 
 If you are only interested in compiling TinyGo code for WebAssembly then you are done with the installation.
@@ -120,7 +120,7 @@ This results in a `tinygo` binary in the `build` directory:
 
 ```shell
 $ ./build/tinygo version
-tinygo version 0.14.1 darwin/amd64 (using go version go1.15 and LLVM version 10.0.1)
+tinygo version 0.15.0 darwin/amd64 (using go version go1.15 and LLVM version 10.0.1)
 ```
 
 ### Additional Requirements for Microcontrollers

content/getting-started/using-docker.md

@@ -7,7 +7,7 @@ You can use our Docker image to be able to run the TinyGo compiler on your compu
 
 ## Installing
 
-    docker pull tinygo/tinygo:0.14.1
+    docker pull tinygo/tinygo:0.15.0
 
 ## Using
 
@@ -16,24 +16,24 @@ For your own code, you will probably want to use absolute paths.
 
 A docker container exists for easy access to the TinyGo CLI. For example, to compile `wasm.wasm` for the WebAssembly export example:
 
-    docker run --rm -v $(pwd):/src tinygo/tinygo:0.14.1 tinygo build -o wasm.wasm -target=wasm examples/wasm/export
+    docker run --rm -v $(pwd):/src tinygo/tinygo:0.15.0 tinygo build -o wasm.wasm -target=wasm examples/wasm/export
 
 See the [WebAssembly page](../../webassembly) for more information on executing the compiled
 WebAssembly.
 
 To compile `blinky1.hex` targeting an ARM microcontroller, such as the PCA10040:
 
-    docker run --rm -v $(pwd):/src tinygo/tinygo:0.14.1 tinygo build -o /src/blinky1.hex -size=short -target=pca10040 examples/blinky1
+    docker run --rm -v $(pwd):/src tinygo/tinygo:0.15.0 tinygo build -o /src/blinky1.hex -size=short -target=pca10040 examples/blinky1
 
 To compile `blinky1.hex` targeting an AVR microcontroller such as the Arduino:
 
-    docker run --rm -v $(pwd):/src tinygo/tinygo:0.14.1 tinygo build -o /src/blinky1.hex -size=short -target=arduino examples/blinky1
+    docker run --rm -v $(pwd):/src tinygo/tinygo:0.15.0 tinygo build -o /src/blinky1.hex -size=short -target=arduino examples/blinky1
 
 For projects that have remote dependencies outside of the standard library and
 go code within your own project, you will need to map your entire `$GOPATH`
 into the docker image for those dependencies to be found:
 
-    docker run -v $GOPATH:/go -e "GOPATH=/go" tinygo/tinygo:0.14.1 tinygo build -o /go/src/github.com/myuser/myrepo/wasm.wasm -target wasm --no-debug /go/src/github.com/myuser/myrepo/wasm-main.go
+    docker run -v $GOPATH:/go -e "GOPATH=/go" tinygo/tinygo:0.15.0 tinygo build -o /go/src/github.com/myuser/myrepo/wasm.wasm -target wasm --no-debug /go/src/github.com/myuser/myrepo/wasm-main.go
 
 **note: At this time, tinygo does not resolve dependencies from the /vendor/ folder within your project.**
 

content/getting-started/windows.md

@@ -38,7 +38,7 @@ You can test that the installation was successful by running the `version` comma
 
 ```shell
 > tinygo version
-tinygo version 0.14.1 windows/amd64 (using go version go1.15 and LLVM version 10.0.1)
+tinygo version 0.15.0 windows/amd64 (using go version go1.15 and LLVM version 10.0.1)
 ```
 
 Upgrading to the latest TinyGo version can be done via scoop with:
@@ -55,7 +55,7 @@ Upgrading to the latest TinyGo version can be done via scoop with:
 
     - Choose the download link for Microsoft Windows, Windows 7 or later, Intel 64-bit processor.
 
-- Download the TinyGo binary for Windows file from https://github.com/tinygo-org/tinygo/releases/download/v0.14.1/tinygo0.14.1.windows-amd64.zip
+- Download the TinyGo binary for Windows file from https://github.com/tinygo-org/tinygo/releases/download/v0.15.0/tinygo0.15.0.windows-amd64.zip
 
 - Decompress the file like this:
 
@@ -75,7 +75,7 @@ Upgrading to the latest TinyGo version can be done via scoop with:
 
     ```
     > tinygo version
-    tinygo version 0.14.1 windows/amd64 (using go version go1.15 and LLVM version 10.0.1)
+    tinygo version 0.15.0 windows/amd64 (using go version go1.15 and LLVM version 10.0.1)
     ```
 
 ### Flashing boards
@@ -189,7 +189,7 @@ This results in a `tinygo.exe` binary in the `build` directory:
 
 ```text
 $ ./build/tinygo version
-tinygo version 0.14.1 windows/amd64 (using go version go1.15 and LLVM version 10.0.1)
+tinygo version 0.15.0 windows/amd64 (using go version go1.15 and LLVM version 10.0.1)
 ```
 
 ### Additional Requirements for Microcontrollers

content/webassembly/webassembly.md

@@ -57,13 +57,13 @@ Note the `--no-debug` flag, which reduces the size of the final binary by removi
 debug symbols from the output. Also note that you must change the path to your Wasm file from `/go/src/github.com/myuser/myrepo/wasm-main.go` to whatever the actual path to your file is:
 
 ```
-docker run -v $GOPATH:/go -e "GOPATH=/go" tinygo/tinygo:0.14.1 tinygo build -o /go/src/github.com/myuser/myrepo/wasm.wasm -target wasm --no-debug /go/src/github.com/myuser/myrepo/wasm-main.go
+docker run -v $GOPATH:/go -e "GOPATH=/go" tinygo/tinygo:0.15.0 tinygo build -o /go/src/github.com/myuser/myrepo/wasm.wasm -target wasm --no-debug /go/src/github.com/myuser/myrepo/wasm-main.go
 ```
 
 Make sure you copy `wasm_exec.js` to your runtime environment:
 
 ```
-docker run -v $GOPATH:/go -e "GOPATH=/go" tinygo/tinygo:0.14.1 /bin/bash -c "cp /usr/local/tinygo/targets/wasm_exec.js /go/src/github.com/myuser/myrepo/
+docker run -v $GOPATH:/go -e "GOPATH=/go" tinygo/tinygo:0.15.0 /bin/bash -c "cp /usr/local/tinygo/targets/wasm_exec.js /go/src/github.com/myuser/myrepo/
 ```
 
 More complete examples are provided in the [wasm examples](https://github.com/tinygo-org/tinygo/tree/master/src/examples/wasm).