From e1eff6ad080465aaee578a3bdbdaf6fca700dab9 Mon Sep 17 00:00:00 2001 From: Dor-bl Date: Wed, 16 Sep 2026 20:48:28 +0000 Subject: [PATCH 1/2] docs: add v9 section for strong-name signing Document the Appium.Net strong-name signing change from #1118 as its own versioned section, matching the existing v8/v5 pattern. Also dedupe the shorter blurb that already lived under NuGet by pointing it at the new v9 section instead of repeating the same notice. --- README.md | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 3c406ff0..1ad5a406 100644 --- a/README.md +++ b/README.md @@ -43,6 +43,14 @@ For example, some changes in the Selenium binding could break the Appium client. > If you need deterministic builds, we recommend pinning the Selenium.WebDriver version in your own project. +## v9 + +Starting with `9.0.0`, the `Appium.Net` assembly shipped by the `Appium.WebDriver` package is strong-name signed with public key token `8b7475dcfe6734d4`, so it can be referenced by strongly-signed .NET assemblies. This aligns with [Selenium 4.44.0](https://github.com/SeleniumHQ/selenium/releases/tag/selenium-4.44.0), which introduced the same change to its own .NET client. See [#1066](https://github.com/appium/dotnet-client/issues/1066) and [#1118](https://github.com/appium/dotnet-client/pull/1118) for background. + +> [!IMPORTANT] +> Strong naming changes the assembly identity from the previously unsigned `Appium.Net` assembly. Consumers compiled against an unsigned release, especially .NET Framework applications, should rebuild after upgrading to `9.0.0`. +> The signing key is intentionally public — it provides a stable assembly identity, not a trust or tamper-evidence guarantee. + ## v8 To keep compatibility with Appium v3, most deprecated endpoint method calls have been replaced with compatible [extension command](https://appium.io/docs/en/latest/guides/execute-methods/) with [this PR](https://github.com/appium/dotnet-client/pull/939). Old drivers which still haven't implemented extension commands might not have proper implementation. Then, you will need to update Appium driver versions first. @@ -113,11 +121,8 @@ Dependencies: - [Selenium.WebDriver](http://www.nuget.org/packages/Selenium.WebDriver/) - [System.Drawing.Common](https://www.nuget.org/packages/System.Drawing.Common/) -The `Appium.Net` assembly shipped by the `Appium.WebDriver` package is strong-name signed with public key token `8b7475dcfe6734d4`, so it can be referenced by strongly-signed .NET assemblies. - -> [!IMPORTANT] -> Strong naming changes the assembly identity from the previously unsigned `Appium.Net` assembly. Consumers compiled against an unsigned release, especially .NET Framework applications, should rebuild after upgrading to the first strong-named release. - +> [!NOTE] +> Starting with `9.0.0`, this assembly is strong-name signed — see [v9](#v9) below. ## Usage From d314c14d011004f991d63f953587becc788eee49 Mon Sep 17 00:00:00 2001 From: Dor-bl Date: Wed, 16 Sep 2026 20:57:30 +0000 Subject: [PATCH 2/2] docs: fix v9 cross-reference direction in NuGet note --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 1ad5a406..c27b1037 100644 --- a/README.md +++ b/README.md @@ -122,7 +122,7 @@ Dependencies: - [System.Drawing.Common](https://www.nuget.org/packages/System.Drawing.Common/) > [!NOTE] -> Starting with `9.0.0`, this assembly is strong-name signed — see [v9](#v9) below. +> Starting with `9.0.0`, this assembly is strong-name signed — see [v9](#v9) above. ## Usage