I think the next major version is a good breakpoint to do some additional housekeeping.

Strong naming this lib has caused way more harm than good, and turned out to be a real maintenance issue. See for example #452 #371 - it even required me asking one of the libs we depend on to adopt strong naming (giraffe-fsharp/Giraffe.ViewEngine#23), and after they declined, re-packaging the repo and distributing a signed version.

I do not want to maintain all of this this and will drop strong naming support on the next major version. A more detailed writeup on all the problems of strong named assemblies can be seen on this >6 (!) year old issue here: StephenCleary/AsyncEx#129 (comment) . People that rely on strong named assemblies can (1) be assured of my sympathy and (2) try to use tooling that gets around this: https://github.com/brutaldev/StrongNameSigner