Release to NuGet

[ZRajko]

Hi,

Originally I use the latest NuGet version (3.0.0.0) from this package, but then I realized that that one using this deprecated API call to get the configuration instead of this latest.

Then I found that the support already built into this repository, just not get deployed to NuGet. Is there a planned release date for this change ?

[ashishdhingra]

Hi @ZRajko,

Good morning.

Thanks for bringing this to our attention. I agree that new version should be released to use the latest API. However, this is not currently planned work for the team. The best way to get traction is to submit a new feature request that could be prioritized by the team.

Thanks,
Ashish

[normj]

The release hold up has been on me. I had wanted to write a blog post announcing the v4 but for a variety reasons that hasn't happen. I decided to push the v4 and will hopefully get a blog post as a quick follow up. If you check NuGet now you will 4.0.0 is out.

[ZRajko]

Wow. That was fast. Thanks for the update.

…

On Tue, Jun 28, 2022, 19:17 Norm Johanson ***@***.***> wrote: The release hold up has been on me. I had wanted to write a blog post announcing the v4 but for a variety reasons that hasn't happen. I decided to push the v4 and will hopefully get a blog post as a quick follow up. If you check NuGet now you will 4.0.0 is out. — Reply to this email directly, view it on GitHub <#116 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZ2QNWK7SPRLO6YSSRJLHFTVRMXQZANCNFSM52BN7S6Q> . You are receiving this because you were mentioned.Message ID: <aws/aws-dotnet-extensions-configuration/repo-discussions/116/comments/3042025 @github.com>

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.