WS10 - version upgrade leads to "Binary format version mismatch"

[mawifr]

I have a project that references several internal NuGet packages. Some of these packages include frontend-related code and are distributed as WebSharper libraries, with the following configuration:

{
  "$schema": "https://websharper.com/wsconfig.schema.json",
  "project": "library",
  "javascript": true,
  "useJavaScriptSymbol": true
}

When I upgrade the WebSharper version in the main project, I receive the following error for each referenced library:

8>WebSharper error WS9001: Error Failed to deserialize metadata for <packagename>, Version=6.4.4.0, Culture=neutral, PublicKeyToken=null.: Binary format version mismatch, found '10.0', expecting '10.1-rev1'

Is there a way to suppress or ignore this error?

At the moment, the only workaround I have found is to first update every referenced library to the latest WebSharper version, and only then update the main project. This makes the package update process quite difficult to manage.

[granicz]

If you depend on WebSharper libraries, they themselves need to reference the same major.minor WebSharper as the consuming project, unfortunately. This means that you'll need to update the dependencies and bring WebSharper up to date in the whole stack. This can get super confusing from a versioning perspective, this is why we always use major.minor in each WS library matching the version of WebSharper used.

(BTW, as I see, 10.1-rev1 is a metadata version label used in 10.1.5.674 but it should really be 10.1 as we bump minor version on each metadata change anyhow.)

[Jand42]

This is a format tag when metadata changes and other breaking changes are introduced, to protect against incompatible builds being used together. (10.1 was only used in internal feed builds, with the debugger keyword support it was changed to 10.1-rev1 to differentiate, so this is the only tag for 10.1 public Nuget versions)