[main] Update dependencies from dotnet/extensions #645
Conversation
…0250207.9 Microsoft.AspNetCore.Diagnostics.Middleware , Microsoft.Extensions.AuditReports , Microsoft.Extensions.Compliance.Abstractions , Microsoft.Extensions.Compliance.Redaction , Microsoft.Extensions.Compliance.Testing , Microsoft.Extensions.Diagnostics.ExceptionSummarization , Microsoft.Extensions.Diagnostics.Testing , Microsoft.Extensions.Http.Diagnostics , Microsoft.Extensions.Telemetry , Microsoft.Extensions.Telemetry.Abstractions From Version 9.2.0-preview.1.25076.1 -> To Version 9.3.0-preview.1.25107.9
![dotnet-policy-service[bot]](https://avatars.githubusercontent.com/in/285228?s=60&v=4){kind=small}
|
@dotnet/dotnet-extensions-compliance can you please have a look at the failure here. We have never published Microsoft.Gen.MetadataExtractor package, and until recently it wasn't needed. Now it is.... |
|
Looks like the regression is caused by dotnet/extensions#5531 |
|
This breaks anyone that would use the AuditReports or MetricReports extensions since they will not be able to resolve the dependency on Microsoft.Gen.MetadataExtractor. It's being referenced directly as a ProjectReference, not an AnalyzerReference. |
|
Opened dotnet/extensions#5894 to fix the issue (hopefully) |
…0250214.10 Microsoft.AspNetCore.Diagnostics.Middleware , Microsoft.Extensions.AuditReports , Microsoft.Extensions.Compliance.Abstractions , Microsoft.Extensions.Compliance.Redaction , Microsoft.Extensions.Compliance.Testing , Microsoft.Extensions.Diagnostics.ExceptionSummarization , Microsoft.Extensions.Diagnostics.Testing , Microsoft.Extensions.Http.Diagnostics , Microsoft.Extensions.Telemetry , Microsoft.Extensions.Telemetry.Abstractions From Version 9.2.0-preview.1.25076.1 -> To Version 9.3.0-preview.1.25114.10
…0250216.2 Microsoft.AspNetCore.Diagnostics.Middleware , Microsoft.Extensions.AuditReports , Microsoft.Extensions.Compliance.Abstractions , Microsoft.Extensions.Compliance.Redaction , Microsoft.Extensions.Compliance.Testing , Microsoft.Extensions.Diagnostics.ExceptionSummarization , Microsoft.Extensions.Diagnostics.Testing , Microsoft.Extensions.Http.Diagnostics , Microsoft.Extensions.Telemetry , Microsoft.Extensions.Telemetry.Abstractions From Version 9.2.0-preview.1.25076.1 -> To Version 9.3.0-preview.1.25116.2
|
Ack. Taking a look |
The problem here is that Microsoft.Gen.MetadataExtractor is pulling in more than it needs from Microsoft.Gen.Metrics, causing a duplicate generator. I will push a fix for this ASAP. |
|
How do we trigger the update? I cannot find it in the workflows. |
…0250217.3 Microsoft.AspNetCore.Diagnostics.Middleware , Microsoft.Extensions.AuditReports , Microsoft.Extensions.Compliance.Abstractions , Microsoft.Extensions.Compliance.Redaction , Microsoft.Extensions.Compliance.Testing , Microsoft.Extensions.Diagnostics.ExceptionSummarization , Microsoft.Extensions.Diagnostics.Testing , Microsoft.Extensions.Http.Diagnostics , Microsoft.Extensions.Telemetry , Microsoft.Extensions.Telemetry.Abstractions From Version 9.2.0-preview.1.25076.1 -> To Version 9.3.0-preview.1.25117.3
The default workflow is whenever dotent/extensions main is published to a transport feed (as a result of the successful internal build), it gets pushed here based on a schedule. Previously the schedule was set to "weekly" and I just changed to "daily". That is, once a day the latest build artifacts from dotnet/extensions will get pushed to this repo. There are ways to trigger the inflow manually with darc trigger-subscriptions --id 80debde5-c49b-4a86-8145-3a9b9d7f5f82 |
|
Looks like we're good! Thank you @dariusclay for getting it fixed. |
2 participants
This pull request updates the following dependencies
From https://github.com/dotnet/extensions