Release v0.3.0

- Changed all occurrences of "0.2.1"
- Changed hashes in Scoop manifest and Homebrew formula

.github/ISSUE_TEMPLATE.md

@@ -41,7 +41,7 @@ Example:
 ### Info
 
 Example:
-> - Version: 0.2.1
+> - Version: 0.3.0
 > - Operating system: Ubuntu 16.04
 
 ### Possible solution

README.md

@@ -202,7 +202,7 @@ So now you can only build the Snap package on Linux, using the following steps:
 1. `snap install snapcraft --classic`
 2. `snapcraft`
 
-Depending on the current `serve` version and your CPU's architecture it will create a file like `serve_0.2.1_amd64.snap`, which can manually be installed with `snap install --dangerous serve_0.2.1_amd64.snap`.
+Depending on the current `serve` version and your CPU's architecture it will create a file like `serve_0.3.0_amd64.snap`, which can manually be installed with `snap install --dangerous serve_0.3.0_amd64.snap`.
 
 The Chocolatey packages need to be uploaded manually to Chocolatey [here](https://chocolatey.org/packages/upload). The package can be built with this script:
 

RELEASES.md

@@ -8,6 +8,9 @@ The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/) a
 vNext
 -----
 
+v0.3.0 (2019-05-04)
+-------------------
+
 - Added: Optional generation and use of a self signed certificate to serve files via HTTPS instead of HTTP ([issue #9](https://github.com/philippgille/serve/issues/9))
 - Added: Optional basic authentication ([issue #10](https://github.com/philippgille/serve/issues/10))
 - Added: Option to bind to a specific network interface ([issue #19](https://github.com/philippgille/serve/issues/19))

VERSION

@@ -1 +1 @@
-0.2.1
+0.3.0

build/build.sh

@@ -41,7 +41,7 @@ fi
 declare -a arr=("Windows" "macOS" "Linux")
 for MYOS in "${arr[@]}"
 do
-    # Sleep to prevent: tar: serve_v0.2.1_macOS_x64: file changed as we read it
+    # Sleep to prevent: tar: serve_v0.3.0_macOS_x64: file changed as we read it
     sleep 1s
     tar -czf "${ARTIFACTSDIR}/serve_v${VERSION}_${MYOS}_x64.tar.gz" -C "${ARTIFACTSDIR}" "serve_v${VERSION}_${MYOS}_x64"
 done

chocolatey/serve.nuspec

@@ -9,7 +9,7 @@
     <!-- version should MATCH as closely as possible with the underlying software -->
     <!-- Is the version a prerelease of a version? https://docs.nuget.org/create/versioning#creating-prerelease-packages -->
     <!-- Note that unstable versions like 0.0.1 can be considered a released version, but it's possible that one can release a 0.0.1-beta before you release a 0.0.1 version. If the version number is final, that is considered a released version and not a prerelease. -->
-    <version>0.2.1</version>
+    <version>0.3.0</version>
     <!-- Markdown okay -->
     <description>`serve` starts a simple temporary static file server in your current directory and prints your IP address to share with colleagues</description>
     <authors>Philipp Gillé</authors>
@@ -45,7 +45,7 @@
 
     <!-- Dependency element for meta package -->
     <dependencies>
-      <dependency id="serve.portable" version="[0.2.1]" />
+      <dependency id="serve.portable" version="[0.3.0]" />
     </dependencies>
   </metadata>
   <!-- this section controls what actually gets packaged into the Chocolatey package -->

chocolatey/serve.portable.nuspec

@@ -9,7 +9,7 @@
     <!-- version should MATCH as closely as possible with the underlying software -->
     <!-- Is the version a prerelease of a version? https://docs.nuget.org/create/versioning#creating-prerelease-packages -->
     <!-- Note that unstable versions like 0.0.1 can be considered a released version, but it's possible that one can release a 0.0.1-beta before you release a 0.0.1 version. If the version number is final, that is considered a released version and not a prerelease. -->
-    <version>0.2.1</version>
+    <version>0.3.0</version>
     <!-- Markdown okay -->
     <description>`serve` starts a simple temporary static file server in your current directory and prints your IP address to share with colleagues</description>
     <authors>Philipp Gillé</authors>

chocolatey/tools/VERIFICATION.txt

@@ -4,4 +4,4 @@ in verifying that this package's contents are trustworthy.
 
 I'm the author of the software, but if further verification is necessary you can create a SHA256 checksum of the binary file in this package. It should match the ones in https://github.com/philippgille/serve/releases.
 
-For example, when this NuGet package is version 0.2.1, you can create a SHA256 checksum of serve.exe and check if it matches https://github.com/philippgille/serve/releases/download/v0.2.1/serve_v0.2.1_Windows_x64.exe.sha256.
+For example, when this NuGet package is version 0.3.0, you can create a SHA256 checksum of serve.exe and check if it matches https://github.com/philippgille/serve/releases/download/v0.3.0/serve_v0.3.0_Windows_x64.exe.sha256.

docs/README.md

@@ -23,7 +23,7 @@ Follow these steps manually, or jump below for the PowerShell commands:
     - Create a function that calls the binary in your shell's profile
         - The PowerShell profile is located at `$profile`
             - Example: `C:\Users\John\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1`
-        - Example function: `function serve { $env:USERPROFILE\Downloads\serve_v0.2.1_Windows_x64\serve.exe $args }`
+        - Example function: `function serve { $env:USERPROFILE\Downloads\serve_v0.3.0_Windows_x64\serve.exe $args }`
         - Don't forget to load your profile afterwards with `. $profile`
 
 As PowerShell commands:

homebrew/serve.rb

@@ -1,9 +1,9 @@
 class Serve < Formula
     desc "`serve` starts a simple temporary static file server in your current directory and prints your IP address to share with colleagues"
     homepage "https://github.com/philippgille/serve"
-    url "https://github.com/philippgille/serve/releases/download/v0.2.1/serve_v0.2.1_macOS_x64.zip"
-    sha256 "5C4FEDEA1D6DB0F59DFFFA60986B3E12B4DDD64CDDF9394E15CA94F5635B9FE8"
-    version "0.2.1"
+    url "https://github.com/philippgille/serve/releases/download/v0.3.0/serve_v0.3.0_macOS_x64.zip"
+    sha256 "4DA48BD9B8DDC6CE30189B8E06D968954C56F3FE31BFCABB12DA265D1EF07C24"
+    version "0.3.0"
 
     bottle :unneeded
 

scoop/serve.json

@@ -1,10 +1,10 @@
 {
-    "version": "0.2.1",
-    "url": "https://github.com/philippgille/serve/releases/download/v0.2.1/serve_v0.2.1_Windows_x64.zip",
+    "version": "0.3.0",
+    "url": "https://github.com/philippgille/serve/releases/download/v0.3.0/serve_v0.3.0_Windows_x64.zip",
     "bin": "serve.exe",
     "homepage": "https://github.com/philippgille/serve",
-    "hash": "1CEF8B0D6CE7F8F4E2116F5471D1B299B6852AF109B8E6F397C70FFC2C37A910",
     "description": "Starts a simple temporary static file server in your current directory and prints your IP address to share with colleagues",
+    "hash": "267DCA3A0394C0D6030D1BFC90D12578903151FE2BA3E6CBB6ECE6D963A28446",
     "checkver": {
         "github": "https://github.com/philippgille/serve"
     },

serve.go

@@ -36,7 +36,7 @@ import (
 
 // Increment and remove "+" in release commits.
 // Add "+" after release commits.
-const version = "v0.2.1"
+const version = "v0.3.0"
 
 // Flags in alphabetical order, just like "-h" prints them
 var (

snap/snapcraft.yaml

@@ -1,5 +1,5 @@
 name: serve
-version: "0.2.1"
+version: "0.3.0"
 # The summary must not exceed 78 characters.
 summary: serve starts a simple temporary static file server in your current directory
 description: |
@@ -47,7 +47,7 @@ parts:
     # Either use a source-depth of 1 for the latest commit, OR a source-tag
     source-depth: 1
     source-branch: master
-    #source-tag: v0.2.1
+    #source-tag: v0.3.0
 
 apps:
   serve: