Paket 5.207.4 broke the FAKE release process and creates empty packages #3599

Description

You can see how I managed to pin it to that particular Paket release: fsprojects/FAKE#2341

In fact, I cannot even reproduce this locally, this only seems to happen in CI and in particular only Azure DevOps and sometimes in GitLab, but only Azure DevOps reproduces 100%

The diff is quite small and only a single PR was involved: 5.207.3...5.207.4

/cc @enricosada

What's really bad is that the packaging process works but creates corrupt packages. The release process did catch the issue, because we bootstrap some of the packages.

You can download and inspect the packages from the build: https://dev.azure.com/fakebuild/FSProjects/_build/results?buildId=1123&view=results

I tried to figure out what the problem is as only a single line changed, for example with this commit, but I couldn't figure it out.

So I boiled it down to a single line change in the targets file but I have no clue why or how it leads to broken packages.

Repro steps

Update to 5.207.4 (or newer), see this commit

Expected behavior

Release process should work as it did before

Actual behavior

Paket-change leads to broken packages, which might be detected only after the package has been released without proper validation.

Known workarounds

• Stay on 5.207.3 or lower
• Use previous targets file (and force paket to use it, by not calling paket restore or by checking out the old targets afterwards)