🚀 Release v0.4.3

Author: rust-marker-ci

CONTRIBUTING.md

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

Cargo.lock

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

Cargo.toml

@@ -59,7 +59,7 @@ curl -fsSL https://raw.githubusercontent.com/rust-marker/marker/v0.4/scripts/rel
 curl.exe -fsSL https://raw.githubusercontent.com/rust-marker/marker/v0.4/scripts/release/install.ps1 | powershell -command -
 ```
 
-The provided scripts use a sliding git tag `v0.4`, to allow for automatic patch version updates, however a fixed tag `v0.4.2` is also available.
+The provided scripts use a sliding git tag `v0.4`, to allow for automatic patch version updates, however a fixed tag `v0.4.3` is also available.
 
 <!-- endregion replace marker version stable -->
 
@@ -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.4.2"
+marker_lints = "0.4.3"
 ```
 <!-- endregion replace marker version stable -->
 

README.md

@@ -21,8 +21,8 @@ pub(crate) fn default_driver_info() -> DriverVersionInfo {
         toolchain: "nightly-2023-11-16".to_string(),
         // endregion replace rust toolchain dev
         // region replace marker version dev
-        version: "0.4.3-dev".to_string(),
-        api_version: "0.4.3-dev".to_string(),
+        version: "0.4.3".to_string(),
+        api_version: "0.4.3".to_string(),
         // endregion replace marker version dev
     }
 }

cargo-marker/src/backend/driver.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.4.2""#
+marker_lints = "0.4.3""#
         ),
-        cli_example = display::cli(r#"cargo marker --lints "marker_lints = '0.4.2'""#),
+        cli_example = display::cli(r#"cargo marker --lints "marker_lints = '0.4.3'""#),
         lints = "--lints".blue(),
     )
 }

cargo-marker/src/error.rs

@@ -22,7 +22,7 @@ The git tag specified in the GitHub Action indicates which version of Marker sho
 
   Use this to get automatic patch updates.
 
-- **Fixed tags, like `v0.4.2`:**
+- **Fixed tags, like `v0.4.3`:**
 
   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!
 

docs/book/src/usage/ci.md

@@ -31,7 +31,7 @@ curl -fsSL https://raw.githubusercontent.com/rust-marker/marker/v0.4/scripts/rel
 curl.exe -fsSL https://raw.githubusercontent.com/rust-marker/marker/v0.4/scripts/release/install.ps1 | powershell -command -
 ```
 
-The provided scripts use a sliding git tag `v0.4`, to allow for automatic patch version updates, however a fixed tag `v0.4.2` is also available.
+The provided scripts use a sliding git tag `v0.4`, to allow for automatic patch version updates, however a fixed tag `v0.4.3` is also available.
 
 <!-- endregion replace marker version stable -->
 

docs/book/src/usage/installation.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.4.2"
+marker_lints = "0.4.3"
 
 # 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 marker version stable -->
 ```sh
 # An external crate from a registry
-cargo marker --lint "marker_lints = '0.4.2'"
+cargo marker --lint "marker_lints = '0.4.3'"
 
 # An external crate from git
 cargo marker --lint "marker_lints = { git = 'https://github.com/rust-marker/marker' }"

docs/book/src/usage/lint-crate-declaration.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 marker version stable -->
-This [`install.sh`](https://raw.githubusercontent.com/rust-marker/marker/v0.4.2/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.4.3/scripts/release/install.sh) script, can be used to automatically download and verify Marker's binaries.
 <!-- endregion replace marker version stable -->
 
 ### Operating system versions coverage