NuGet deploy failing since merging #369

[fgreinacher]

The NuGet deploy through AppVeyor is failing since I merged #369. It complains about an invalid or expired API key which I didn't actually change in the PR I have no idea how that happened.

Build: https://ci.appveyor.com/project/tathamoddie/system-io-abstractions/builds/19794098
Diff of AppVeyor.yml: https://github.com/System-IO-Abstractions/System.IO.Abstractions/pull/369/files#diff-180360612c6b8c4ed830919bbb4dd459

@tathamoddie @jpreese Any ideas?

[tathamoddie]

Fixed by #382, but now the GitHub key isn't valid

[tathamoddie]

@fgreinacher Where does the GitHub key come from?

[tathamoddie]

Based on the build sequence, whilst the build is failing, NuGet packages are being published again at least

[tathamoddie]

And the package version just jumped from 2.1.0.256 to 2.2.2-beta

[fgreinacher]

Thanks!

The GitHub key - I created one and encrypted through my AppVeyor account - that’s probably the problem. I assume you need to do that @tathamoddie

[fgreinacher]

Maybe it might be better to add @jpreese and myself as Collaborators on your AppVeyor account, seems to be possible somehow though I’m not sure how much you can restrict this role to the SIO project.

[fgreinacher]

@tathamoddie The easiest way would probably be to add us as owners for the packages on NuGet.org - then we take care of all the remaining things without bothering you for each and every change :)

[tathamoddie]

@jpreese is already a collaborator on the AppVeyor project. Adding you now @fgreinacher.

[tathamoddie]

You (@jpreese and @fgreinacher) should now both be co-owners of the GitHub org (https://github.com/System-IO-Abstractions/) and the AppVeyor project (https://ci.appveyor.com/project/tathamoddie/system-io-abstractions)

[fgreinacher]

Thanks, stuff is working great now!