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

Nuget does not match Github #212

Open
mgaffigan opened this issue Dec 14, 2023 · 8 comments
Open

Nuget does not match Github #212

mgaffigan opened this issue Dec 14, 2023 · 8 comments

Comments

@mgaffigan
Copy link

Great library - but we can't find the source for https://www.nuget.org/packages/SmtpServer/10.0.0

Can you push to github or provide the new source repo? Ideally, github would be updated before nuget.

@BrewingCoder
Copy link

I have been building against a local fork of the Develop branch, which is what I was assuming was getting packaged out to nuget; I could be wrong though but the timing of the last commit loosely matches generally with the 10.0.0 package release.

@mgaffigan
Copy link
Author

Ok. I agree that seems to match. Without the tag it is hard to correlate. Have you considered using Github Actions to ensure consistent release practices? I'm happy to send a PR (or post in the issue) if you are open to it.

@BrewingCoder
Copy link

that would be up to cosullivan the repo owner. I work from a local fork only because I have added some specific features in the past though I admit the two I really needed have been added into that branch over time. The library is fairly mature and stable and has been around quite a while; I don't think the author spends much time maintaining it as he had in the past.

@mgaffigan
Copy link
Author

@cosullivan, would you be open to a Github Actions PR ensuring nuget and github releases come from git tags?

@cosullivan
Copy link
Owner

@cosullivan, would you be open to a Github Actions PR ensuring nuget and github releases come from git tags?

Yes, I would be open to that.

@tinohager
Copy link
Contributor

tinohager commented Sep 20, 2024

@tinohager
Copy link
Contributor

fixed with 11.0.0-beta1

@mgaffigan
Copy link
Author

Excellent! Thanks.

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

4 participants