-
Notifications
You must be signed in to change notification settings - Fork 274
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
[release]: One-click release process for opensearch-net #3194
Comments
I just realized this is a dupe of #3141 |
Reopening as #3141 was closed. |
For context: this depends on #2965 , which was completed. |
Yeah the dependent issue is complete. We just need to onboard .net repository to this process. Will work on this next week and update the issue once its done. |
We have a handful of features, bug-fixes & dependency updates waiting to be released in the .NET client, it would be awesome to be able to release these with the new automated process, biggest name one being support for Amazon OpenSearch Serverless: https://github.com/opensearch-project/opensearch-net/blob/main/CHANGELOG.md#unreleased |
Closing this issue as opensearch-net is onboarded to 1-click release process. Please re-open in case of any issues. |
Reopening until a release is successful. |
🎉 OpenSearch DotNet client is released successfully on Nuget: https://www.nuget.org/profiles/opensearchproject |
What is the name of your component?
The component is the .Net client
What is the link to your GitHub repo?
https://github.com/opensearch-project/opensearch-net
Targeted release date
Feb 23, 2023
Where should we publish this component?
Nuget.org
What type of artifact(s) will be generated for this component?
Nuget package
Have you completed the required reviews including security reviews, UX reviews?
Yes
Have you on-boarded automated security scanning for the GitHub repo associated with this component?
Not sure. What is considered the baseline for this?
Additional context
No response
The text was updated successfully, but these errors were encountered: