Nuget was not published

[laurentkempe]

The build for #214 fixing #213 merged in master failed and the nuget was not published with the following error The specified API key is invalid

Publishing DotNetZip.1.15.0.nupkg to https://www.nuget.org/api/v2/package...
Error publishing package. NuGet server returned 403: The specified API key is invalid, has expired, or does not have permission to access the specified package.

@haf do you have access to nuget to get a new API key to update it here? which is highly unsecured!

[haf]

@laurentkempe It's encrypted with an appveyor-specific key to my account, so it's not insecure. But I need to update it. MSFT has started cycling keys, despite them being "safe enough", because they don't think they are safe enough. I'll see what time I can spend on this in the next couple of days.

[laurentkempe]

Oh I see @haf you are using Secure variables 👍 Thanks for the clarification!
No stress from my side for the update, we are not going to .NET 5 at least before December or January, nevertheless I hope you get the time to update the key so that it can be deployed to nuget.

[haf]

I've updated the env var. Please try again.

[haf]

The main lib is now published, but the sublibs I need to reset the account for; they are using an old NuGet account that the nuget team has expired.