Import of v0.32.2 (#2083)

CHANGES.md

@@ -3,6 +3,14 @@
 
 All notable changes to this program are documented in this file.
 
+## 0.32.2  (2023-02-08, `602aa16c20d4`)
+
+### Fixed
+
+- With the release of geckodriver 0.32.1 the marionette crate was inappropriately
+  bumped to a semver incompatible version and caused `cargo install geckodriver`
+  to fail for older releases.
+
 ## 0.32.1  (2023-02-02, `b7f075124503`)
 
 ### Fixed

Cargo.toml

@@ -1,7 +1,7 @@
 [package]
 edition = "2018"
 name = "geckodriver"
-version = "0.32.1"
+version = "0.32.2"
 authors = ["Mozilla"]
 include = [
     "/.cargo",
@@ -27,11 +27,11 @@ clap = { version = "~3.1", default-features = false, features = ["cargo", "std",
 hyper = "0.14"
 lazy_static = "1.0"
 log = { version = "0.4", features = ["std"] }
-marionette = "0.2.1"
+marionette = "0.3.0"
 mozdevice = "0.5.1"
 mozprofile = "0.9.1"
-mozrunner = "0.15.0"
-mozversion = "0.5.0"
+mozrunner = "0.15.1"
+mozversion = "0.5.1"
 regex = { version="1.0", default-features = false, features = ["perf", "std"] }
 serde = "1.0"
 serde_derive = "1.0"

doc/Releasing.md

@@ -45,23 +45,31 @@ you can skip them:
 
 For each crate:
 
-1. Bump the version number in `Cargo.toml` based on [semantic versioning rules],
+1. Change into the crates folder.
+2. Bump the version number in `Cargo.toml` based on [semantic versioning rules],
    and also update the version dependency for other in-tree crates using the
    currently modified crate. Note that running `cargo update` (see next step)
-   will fail if you missed updating a crate's dependency.
-2. Update the crate: `cargo update -p <crate name>`
-3. We also publish audit information for the crates based on Mozilla's
+   will fail if you missed updating a crate's dependency. Also use the
+   [cargo-semver-checks] command to validate the version change:
+
+    ```shell
+    % cargo semver-checks check-release
+    ```
+
+3. Update the crate: `cargo update -p <crate name>`
+4. We also publish audit information for the crates based on Mozilla's
    [audit criteria], and that must be updated for each release. To do that run:
 
     ```shell
     % ./mach cargo vet certify <name> <version> --force
     ```
 
-4. Commit the changes for the modified [Cargo.toml] files, [Cargo.lock] and the
+5. Commit the changes for the modified [Cargo.toml] files, [Cargo.lock] and the
    [supply-chain/] folder, which can be found in the repositories root folder.
    Use a commit message like `Bug XYZ - [rust-<name>] Release version <version>`.
 
 [semantic versioning rules]: https://semver.org/
+[cargo-semver-checks]: https://crates.io/crates/cargo-semver-checks
 [audit criteria]: https://mozilla.github.io/cargo-vet/audit-criteria.html
 [Cargo.toml]: https://searchfox.org/mozilla-central/source/testing/geckodriver/Cargo.toml
 [Cargo.lock]: https://searchfox.org/mozilla-central/source/Cargo.lock

doc/Support.md

@@ -22,6 +22,11 @@ and required versions of Selenium and Firefox:
     <th>max
   </tr>
  </thead>
+ <tr>
+  <td>0.32.2
+  <td>≥ 3.11 (3.14 Python)
+  <td>102 ESR
+  <td>n/a
  <tr>
   <td>0.32.1
   <td>≥ 3.11 (3.14 Python)

marionette/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "marionette"
-version = "0.2.1"
+version = "0.3.0"
 authors = ["Mozilla"]
 description = "Library implementing the client side of Gecko's Marionette remote automation protocol."
 edition = "2018"