Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v1.1 not published to nuget #3

Closed
SethDG opened this issue Dec 12, 2018 · 6 comments
Closed

v1.1 not published to nuget #3

SethDG opened this issue Dec 12, 2018 · 6 comments
Assignees

Comments

@SethDG
Copy link

SethDG commented Dec 12, 2018

Can you do me a favor and publish v1.1 to nuget? I had downloaded the current nuget package (v1.0) and couldn't figure out why the Name property wouldn't work. I realize now that functionality was added in v1.1 but it took me awhile to figure that out.

Thanks!

@SethDG
Copy link
Author

SethDG commented Dec 12, 2018

I apologize, I realize now that the person publishing the code to nuget is likely a different person than the maintainer of this repository. I have contacted the owner of the nuget package through the nuget site. I'm going to close this issue.

@SethDG SethDG closed this as completed Dec 12, 2018
@jasond-s jasond-s reopened this Dec 12, 2018
@jasond-s
Copy link
Member

Appveyor should have released the new version after building. Seems there is an error in the Appveyor build.

Will take a look ASAP. Seems some issue with tags. It's all a bit black magic to me and from what I know, should have worked.

@jasond-s
Copy link
Member

There was an erroneous tag 1.0.0 created that seems to have been causing an issue. I have cleaned up the tags and releases and appveyor is now correctly building.

However, the nuget package is failing to upload from appveyor as there seems to be an issue with the certificate at https://nuget.smbsrc.net.... again.

NuGet/Home#6082

Will close once the cert issue is fixed and appveyor can release the code correctly. If there is a desperate need for this version to be available might consider manually pushing the package.

@jasond-s jasond-s self-assigned this Dec 13, 2018
@SethDG
Copy link
Author

SethDG commented Dec 13, 2018

Thank you so much for digging into this problem

I don't know about anyone else, but there is no desperate need from me. It is up to you when and how you want to solve this problem. I am doing fine just compiling from source and using v1.1 that way.

@jasond-s
Copy link
Member

Seems that the certificate issue has been fixed. Have released the new version to nuget.

@SethDG
Copy link
Author

SethDG commented Dec 19, 2018

Thanks a lot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants