Release version 2.0.0

Author: ctrueden

build.gradle.kts

@@ -4,7 +4,7 @@ plugins {
 }
 
 group = "org.apposed"
-version = "2.0.0-SNAPSHOT"
+version = "2.0.0"
 
 repositories {
     mavenCentral()

doc/MACOS.md

@@ -164,7 +164,7 @@ The next section offers step-by-step instructions for the second path: signing a
 6. Run Jaunch's code-signing script:
    ```shell
    export DEV_ID="Penelope Realperson (XY1Q234ABC)"
-   ~/jaunch-1.0.4/bin/sign.sh /path/to/MyApp.app
+   ~/jaunch-2.0.0/bin/sign.sh /path/to/MyApp.app
    ```
    Where your actual `DEV_ID` value is your developer ID info from step 3, and
    `/path/to/MyApp.app` is the location of the .app bundle generated in step 1.

doc/SETUP.md

@@ -2,8 +2,8 @@
 
 1. OPTION 1: Download and unpack the
    [latest Jaunch release](https://github.com/apposed/jaunch/releases).
-   The rest of this guide will assume you unpacked the Jaunch v1.0.4
-   release into your home directory at `~/jaunch-1.0.4`.
+   The rest of this guide will assume you unpacked the Jaunch v2.0.0
+   release into your home directory at `~/jaunch-2.0.0`.
 
 2. OPTION 2: You can [build Jaunch from source](BUILD.md). But if you
    want launchers for all supported platforms (Linux, macOS, and Windows),
@@ -51,7 +51,7 @@
 7. Use Jaunch's app-generation script to copy Jaunch's various bits
    into the correct places within your application base directory:
    ```shell
-   ~/jaunch-1.0.4/bin/appify.sh \
+   ~/jaunch-2.0.0/bin/appify.sh \
      --app-exe fizzbuzz \
      --app-icon-linux fizzbuzz.svg \
      --app-icon-macos fizzbuzz.icns \
@@ -88,14 +88,14 @@ Or maybe you don't, in which case you can ask for help on the
 Next steps:
 
 1. Optionally, compress the launcher executables using
-   `~/jaunch-1.0.4/bin/pack.sh`, which uses [UPX](https://upx.github.io/) to
+   `~/jaunch-2.0.0/bin/pack.sh`, which uses [UPX](https://upx.github.io/) to
    reduce their file sizes. Be warned that while it is nice to reduce Jaunch
    to the smallest possible size, we have received reports of Windows
    anti-malware tools misidentifying Jaunch binaries as infected by
    [various malware](https://github.com/apposed/jaunch/commit/3ecb2a215f6601cd09ef8985597bb1e85ed5e240).
    So caveat emptor on the binary shrinking!
 
 2. Code-sign your macOS and/or Windows binaries using
-   `~/jaunch-1.0.4/bin/sign.sh`. See these guides for detailed instructions:
+   `~/jaunch-2.0.0/bin/sign.sh`. See these guides for detailed instructions:
    - [Code-signing on macOS](MACOS.md#code-signing)
    - [Code-signing on Windows](WINDOWS.md#code-signing)

doc/WINDOWS.md

@@ -194,7 +194,7 @@ The next section offers step-by-step instructions for the second path: re-signin
 8. Run Jaunch's code-signing script:
    ```shell
    export THUMBPRINT="effaced0abcdef12345678900987654321fedcba"
-   ~/jaunch-1.0.4/bin/sign.sh /path/to/myapp/*.exe /path/to/myapp/jaunch/*.exe
+   ~/jaunch-2.0.0/bin/sign.sh /path/to/myapp/*.exe /path/to/myapp/jaunch/*.exe
    ```
    Where your actual `THUMBPRINT` value is the one from step 6, and the
    `/path/to/...` expressions reference the EXE files constructed in step 1.