-
Notifications
You must be signed in to change notification settings - Fork 287
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
Timeline for 2.22.0 release #2792
Comments
Hi @oleksandr-didyk, I will follow up on this. Can you help me understand why this is a blocker for your team? |
Not to mention the fix for CVE-2021-24112 that sits in 2.22 as well. |
Hey @TimothyMothra, thank you for taking care of this!
Currently the package is part of the VMR -> https://github.com/dotnet/dotnet Due to source-build limitations we are carrying a submodule of Application.Insights, pointing to the version that repositories in .NET utilize - https://github.com/dotnet/dotnet/tree/main/src/source-build-externals/src. We can only point to the version that is used by the repos & the repos would only use a release version. As such, we would need the fix in question to be released for it to take effect in the VMR |
@TimothyMothra - Any update on this? |
No ETA at the moment. |
This is released now (PR #2832). New version is at: https://www.nuget.org/packages/Microsoft.ApplicationInsights/2.22.0. The fix for CVE-2021-24112 in |
Given that the existing
2.22.0
GitHub milestone is 20+ days behind schedule, is there any planned release date for this version that can be shared?This is mostly in regards to a fix for a licensing issue - #2670
As mentioned in the issue above, the project is used in .NET source-code and having a proprietary license would mean that .NET is not allowed to use it. The fix is currently present in a
beta
release of the project, but .NET would not take a dependency on abeta
package, thus the need for a full release to be publicly available for us to be able to consume the fix.The text was updated successfully, but these errors were encountered: