-
Notifications
You must be signed in to change notification settings - Fork 275
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 .NET Clients version 1.0.0 to NuGet #2051
Comments
@zelinh @prudhvigodithi Please proceed with publishing the client |
[Triage] @zelinh already have some progress with nuget account setup, need a way to sign and publish the package |
@prudhvigodithi , @zelinh what are the next steps on this ? thanks |
Hey @anirudha and @joshuali925 let me know if you are ok with reserved prefixed as |
@prudhvigodithi That should work. Since there are two prefixes, is it still possible to see them together in one place on NuGet? maybe by going to the owner/publisher profile, or search for |
Hey @joshuali925 yes |
Hi Team, Please let us know if you need any help. |
Hey thanks @anandbprem, working closely on this issue with Microsoft(nuget.org) and awsdotnet teams to get a reserved prefixes for OpenSearch and OSC, this includes getting three Glob patterns OpenSearch.* OSC.* OSC and creating a release flow to sign the generated dll's and update the nukpg packages securely. Multiple phases :) |
Thanks for your response, also we need to plan to upgrade from .net 5.0 to 6.0 :) :) |
Hey @joshuali925, following are the dll files generated when i run
or just the following that actually get packed into the nuget packages ?
|
From the existing .nupkg files i see just these ones:
but I'm not sure, @MaxKsyunz could you check which ones are needed? thanks |
@prudhvigodithi only the DLLs that get packed need to be signed -- your second list. |
thanks @MaxKsyunz and @joshuali925 |
I think I got the error |
Update: we renamed |
Hey @joshuali925 and @MaxKsyunz published the clients to nuget.org, please test/validate the clients, if required we can still unlist them from |
@prudhvigodithi , the URL shared does not have any packages listed. |
any dates are we targeting @joshuali925 |
the packages were taken down as there were some issues found during testing and validation. @prudhvigodithi could you provide an update on current status please? thanks |
@prudhvigodithi all we wanted to know is if the publish will happen in next couple of days or it would take more than a month to help us plan our dev work |
Hey @INeerav @anandbprem the published packages were unlisted due to reported validation tests failure, @anirudha @joshuali925 are we good to republish the packages again? if so can you please share the 1.x version branch information. |
pending release processes for a final publish. thanks @prudhvigodithi |
@anirudha What do you mean by pending release process? Are you still validating the packages? Can you provide a brief overview of the current status? |
Looks like OpenSearch 2.0.x release has broken compatibility with elasticsearch-net library, so this is going to be needed soon for some people. |
@joshuali925 any updates? |
@joshuali925 Any updates? |
@prudhvigodithi, @anirudha, @joshuali925 is there any update on when the nuget packages will be re-released please? |
Hey @anirudha @joshuali925 just wanted to follow up again, can you post an update when you get a chance? |
currently in progress of security review |
How long does it take to get this nuget package published? We really need this nuget package published. |
@joshuali925, @prudhvigodithi, @anirudha - is there anything I can do to help this process along? |
All done! last friday :) finally! planning release activites to nuGet. we should have this posted in under week now. |
I posted the current status above, but I also want to acknowledge, and apologize for failing to provide a regular status update earlier. Thank you for your patience. |
Thanks @anirudha! Can you share what the remaining steps are before we can release? |
We just shipped OpenSearch 1.0.0 .NET clients to nuget repo https://www.nuget.org/profiles/opensearchproject. |
Thanks everyone. Much appreciated 🥳 |
Closing this issue as we have released .Net client 1.0.0 to NuGet. |
Is your feature request related to a problem? Please describe
Since NuGet account is created, we would like to release the .NET clients from opensearch-net repo. Here is the list of packages and descriptions:
OpenSearch.Client
-- Strongly typed interface to OpenSearch. Fluent and classic object initializer mappings of requests and responses. Uses and exposes OpenSearch.Net.OpenSearch.Net
-- Exposes all the OpenSearch API endpoints but leaves you in control of building the request and response bodies. Comes with built in cluster failover/connection pooling support.OpenSearch.Net.VirtualizedCluster
-- Provides a way to assert client behavior through a rule engine backed VirtualClusterConnection.OpenSearch.Client.JsonNetSerializer
-- OpenSearch.Client uses an internal serializer. This package enables serialization for your documents using your own custom Json.NET serializerThe artifacts are generated by this workflow: https://github.com/opensearch-project/opensearch-net/actions/workflows/release.yml
Describe the solution you'd like
Infra's help to release the packages to NuGet, please let me know if something is required
Describe alternatives you've considered
No response
Additional context
Linking release issue opensearch-project/opensearch-net#14
The text was updated successfully, but these errors were encountered: