Paket.Push showing inconsistent behaviour

After publishing dotnet-fable 1.3.0-beta-003 when I tried to use the package, after downloading it normally with Paket and running dotnet fable I get the following message:

No executable found matching command "dotnet-fable"

After several tries, and thanks to Enrico's help I noticed the dotnet-fable 1.3.0-beta-003 package didn't contain a lib folder. You can check that by manually downloading the package and uncompressing it (that's the same for the same version of Fable.Core and Fable.Compiler packages). I pushed a couple of packages more making some changes in the .fsproj file without luck, finally I created and pushed the package manually using the dotnet nuget push command and that time it worked. The PublishPackages target in Fable's build.fsx calls Paket.Push so I'm assuming the problem is there, but I don't know what exactly triggered it as it as working for 1.3.0-beta-002 and before.

Some things that changed when publishing 1.3.0-beta-003:

• Paket version: 5.119.9
• Fable dependencies are managed now by Paket
• Additional MSBuild properties have been added to the project files

The same day I pushed Fable.Import.Browser which also invokes Paket.Push but in this case it worked 🤔

Start with Fable's build.fsx around the PublishPackages target and its Paket.Push call. Compare the 1.3.0-beta-003 publication path with 1.3.0-beta-002 and the working Fable.Import.Browser push, focusing on why the package lacks a lib folder. Done means Paket.Push produces packages usable by dotnet fable, like those pushed with dotnet nuget push.