🚀 Release v0.3.0

CONTRIBUTING.md

@@ -168,7 +168,7 @@ The following is a small collection of ways you can test Marker right now:
 
 <!-- region replace-version stable -->
     ```sh
-    cargo marker --lints "marker_lints = '0.2.1'"
+    cargo marker --lints "marker_lints = '0.3.0'"
     ```
 <!-- endregion replace-version stable -->
 

Cargo.toml

@@ -24,19 +24,19 @@ license    = "MIT OR Apache-2.0"
 repository = "https://github.com/rust-marker/marker"
 
 # region replace-version dev
-version = "0.3.0-dev"
+version = "0.3.0"
 # endregion replace-version dev
 
 # The MSRV is applied to the public library crates published to crates.io
 rust-version = "1.66"
 
 [workspace.dependencies]
 # region replace-version dev
-marker_adapter = { path = "./marker_adapter", version = "0.3.0-dev" }
-marker_api     = { path = "./marker_api", version = "0.3.0-dev" }
-marker_error   = { path = "./marker_error", version = "0.3.0-dev" }
+marker_adapter = { path = "./marker_adapter", version = "0.3.0" }
+marker_api     = { path = "./marker_api", version = "0.3.0" }
+marker_error   = { path = "./marker_error", version = "0.3.0" }
 marker_uitest  = { path = "./marker_uitest", features = ["dev-build"] }
-marker_utils   = { path = "./marker_utils", version = "0.3.0-dev" }
+marker_utils   = { path = "./marker_utils", version = "0.3.0" }
 # endregion replace-version dev
 
 bumpalo            = "3.14"

README.md

@@ -51,15 +51,15 @@ Select one of the installation scripts below according to your platform. The scr
 
 **Linux or MacOS (Bash)**:
 ```bash
-curl -fsSL https://raw.githubusercontent.com/rust-marker/marker/v0.2/scripts/release/install.sh | bash
+curl -fsSL https://raw.githubusercontent.com/rust-marker/marker/v0.3/scripts/release/install.sh | bash
 ```
 
 **Windows (PowerShell)**:
 ```ps1
-curl.exe -fsSL https://raw.githubusercontent.com/rust-marker/marker/v0.2/scripts/release/install.ps1 | powershell -command -
+curl.exe -fsSL https://raw.githubusercontent.com/rust-marker/marker/v0.3/scripts/release/install.ps1 | powershell -command -
 ```
 
-The provided scripts use a sliding git tag `v0.2`, to allow for automatic patch version updates, however a fixed tag `v0.2.1` is also available.
+The provided scripts use a sliding git tag `v0.3`, to allow for automatic patch version updates, however a fixed tag `v0.3.0` is also available.
 
 <!-- endregion replace-version stable -->
 
@@ -81,13 +81,13 @@ Marker provides a Github Action that downloads the pre-compiled binaries and run
 <!-- region replace-version stable -->
 
 ```yml
-- uses: rust-marker/marker@v0.2
+- uses: rust-marker/marker@v0.3
 ```
 
 If you want to only install Marker, and not run it, there is an option for that.
 
 ```yml
-- uses: rust-marker/marker@v0.2
+- uses: rust-marker/marker@v0.3
   with:
     install-only: true
 
@@ -111,7 +111,7 @@ marker_lints = { path = './marker_lints' }
 # An external crate via git
 marker_lints = { git = "https://github.com/rust-marker/marker" }
 # An external crate from a registry
-marker_lints = "0.2.1"
+marker_lints = "0.3.0"
 ```
 <!-- endregion replace-version stable -->
 

cargo-marker/src/backend/driver.rs

@@ -18,8 +18,8 @@ pub(crate) fn default_driver_info() -> DriverVersionInfo {
     DriverVersionInfo {
         toolchain: "nightly-2023-08-24".to_string(),
         // region replace-version dev
-        version: "0.3.0-dev".to_string(),
-        api_version: "0.3.0-dev".to_string(),
+        version: "0.3.0".to_string(),
+        api_version: "0.3.0".to_string(),
         // endregion replace-version dev
     }
 }

cargo-marker/src/error.rs

@@ -70,9 +70,9 @@ marker_lints = { path = './marker_lints' }
 # An external crate via git
 marker_lints = { git = "https://github.com/rust-marker/marker" }
 # An external crate from a registry
-marker_lints = "0.2.1""#
+marker_lints = "0.3.0""#
         ),
-        cli_example = display::cli(r#"cargo marker --lints "marker_lints = '0.2.1'""#),
+        cli_example = display::cli(r#"cargo marker --lints "marker_lints = '0.3.0'""#),
         lints = "--lints".blue(),
     )
 }

docs/book/src/usage/ci.md

@@ -11,18 +11,18 @@ Marker provides a GitHub Action that downloads the pre-compiled binaries and run
 <!-- region replace-version stable -->
 
 ```yml
-- uses: rust-marker/marker@v0.2
+- uses: rust-marker/marker@v0.3
 ```
 
 ### Git tags
 
 The git tag specified in the GitHub Action indicates which version of Marker should be installed. There are several tag flavors available:
 
-- **Sliding tags, like `v0.2` *(recommended)*:**
+- **Sliding tags, like `v0.3` *(recommended)*:**
 
   Use this to get automatic patch updates.
 
-- **Fixed tags, like `v0.2.1`:**
+- **Fixed tags, like `v0.3.0`:**
 
   Use this to pin a specific patch version. If you find a regression in a patch version, please create a [new issue]. Patch versions must never break anything!
 
@@ -111,7 +111,7 @@ curl \
     --show-error \
     --retry 5 \
     --retry-connrefused \
-    https://raw.githubusercontent.com/rust-marker/marker/v0.2/scripts/release/install.sh \
+    https://raw.githubusercontent.com/rust-marker/marker/v0.3/scripts/release/install.sh \
     | bash
 ```
 
@@ -124,7 +124,7 @@ curl.exe `
     --show-error `
     --retry 5 `
     --retry-connrefused `
-    https://raw.githubusercontent.com/rust-marker/marker/v0.2/scripts/release/install.ps1 `
+    https://raw.githubusercontent.com/rust-marker/marker/v0.3/scripts/release/install.ps1 `
     | powershell -command -
 ```
 

docs/book/src/usage/installation.md

@@ -23,15 +23,15 @@ Select one of the installation scripts below according to your platform. The scr
 
 **Linux or MacOS (Bash)**:
 ```bash
-curl -fsSL https://raw.githubusercontent.com/rust-marker/marker/v0.2/scripts/release/install.sh | bash
+curl -fsSL https://raw.githubusercontent.com/rust-marker/marker/v0.3/scripts/release/install.sh | bash
 ```
 
 **Windows (PowerShell)**:
 ```ps1
-curl.exe -fsSL https://raw.githubusercontent.com/rust-marker/marker/v0.2/scripts/release/install.ps1 | powershell -command -
+curl.exe -fsSL https://raw.githubusercontent.com/rust-marker/marker/v0.3/scripts/release/install.ps1 | powershell -command -
 ```
 
-The provided scripts use a sliding git tag `v0.2`, to allow for automatic patch version updates, however a fixed tag `v0.2.1` is also available.
+The provided scripts use a sliding git tag `v0.3`, to allow for automatic patch version updates, however a fixed tag `v0.3.0` is also available.
 
 <!-- endregion replace-version stable -->
 

docs/book/src/usage/lint-crate-declaration.md

@@ -12,7 +12,7 @@ The main way to declare lint crates, is to add them to the `Cargo.toml` file und
 ```toml
 [workspace.metadata.marker.lints]
 # An external crate from a registry
-marker_lints = "0.2.1"
+marker_lints = "0.3.0"
 
 # An external crate from git
 marker_lints = { git = "https://github.com/rust-marker/marker" }
@@ -31,7 +31,7 @@ A lint crate can be specified with the `--lints` option. The string is expected
 <!-- region replace-version stable -->
 ```sh
 # An external crate from a registry
-cargo marker --lint "marker_lints = '0.2.1'"
+cargo marker --lint "marker_lints = '0.3.0'"
 
 # An external crate from git
 cargo marker --lint "marker_lints = { git = 'https://github.com/rust-marker/marker' }"

docs/internal/release.md

@@ -31,7 +31,7 @@ GitHub is very generous with the releases storage limits. They are [almost unlim
 The `sha256` sum is a small file that users may optionally download together with the archive itself to verify the integrity of the archive. It serves as a signature of the artifact to make sure it was downloaded as expected bit-by-bit with what was published effectively detecting corruptions during the download and making it harder to forge artifacts for malicious actors.
 
 <!-- region replace-version stable -->
-This [`install.sh`](https://raw.githubusercontent.com/rust-marker/marker/v0.2.1/scripts/release/install.sh) script, can be used to automatically download and verify Marker's binaries.
+This [`install.sh`](https://raw.githubusercontent.com/rust-marker/marker/v0.3.0/scripts/release/install.sh) script, can be used to automatically download and verify Marker's binaries.
 <!-- endregion replace-version stable -->
 
 ### Operating system versions coverage

marker_api/README.md

@@ -46,8 +46,8 @@ To get started, create a new Rust crate that compiles to a library (`cargo init
 crate-type = ["cdylib"]
 
 [dependencies]
-marker_api = "0.2.1"
-marker_utils = "0.2.1"
+marker_api = "0.3.0"
+marker_utils = "0.3.0"
 ```
 <!-- endregion replace-version stable -->
 

marker_lints/README.md

@@ -28,7 +28,7 @@ To use `marker_lints` in your project, simply add it to your `Cargo.toml` under
 <!-- region replace-version stable -->
 ```toml
 [workspace.metadata.marker.lints]
-marker_lints = "0.2.1"
+marker_lints = "0.3.0"
 ```
 <!-- endregion replace-version stable -->
 

marker_uitest/README.md

@@ -31,7 +31,7 @@ First add `marker_utils` to the dev-dependencies of the lint crate, and specify
 <!-- region replace-version stable -->
 ```toml
 [dev-dependencies]
-marker_uitest = "0.2.1"
+marker_uitest = "0.3.0"
 
 [[test]]
 name = "uitest"

marker_utils/README.md

@@ -22,14 +22,14 @@ To get started, just include *marker_utils* as a dependency:
 <!-- region replace-version stable -->
 ```toml
 [dependencies]
-marker_api = "0.2.1"
+marker_api = "0.3.0"
 ```
 
 You can also add [marker_lints] as a lint crate, designed for this crate:
 
 ```toml
 [workspace.metadata.marker.lints]
-marker_lints = "0.2.1"
+marker_lints = "0.3.0"
 ```
 <!-- endregion replace-version stable -->
 

scripts/release/install.ps1

@@ -46,7 +46,7 @@ $ErrorActionPreference = "Stop"
 # This script isn't meant to be run from `master`, but if it is, then
 # it will install the latest version be it a stable version or a pre-release.
 # region replace-version unstable
-$version = "0.2.1"
+$version = "0.3.0"
 # endregion replace-version unstable
 
 $toolchain = "nightly-2023-08-24"

scripts/release/install.sh

@@ -17,7 +17,7 @@ set -euo pipefail
 # This script isn't meant to be run from `master`, but if it is, then
 # it will install the latest version be it a stable version or a pre-release.
 # region replace-version unstable
-version=0.2.1
+version=0.3.0
 # endregion replace-version unstable
 
 toolchain=nightly-2023-08-24