Repository navigation
chore: Bump Autofac from 9.3.2 to 9.3.4 - #158
Conversation
--- updated-dependencies: - dependency-name: Autofac dependency-version: 9.3.4 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
🚀 Benchmark ResultsDetails
Details
Details
|
…#158) by dependabot[bot]
…#158) by dependabot[bot]
Updated Autofac from 9.3.2 to 9.3.4.
Release notes
Sourced from Autofac's releases.
9.3.4
What's Changed
Do not build a held registration's pipeline early by @tillig in autofac/Autofac#1504 (fixes #1503) - a regression introduced in 9.3.3. Registering an open generic for several services (
.As(typeof(IFirstService<>)).As(typeof(ISecondService<>))) threwInvalidOperationException: Component pipeline has already been built, and cannot be modified.on first resolve whenever anything attached toPipelineBuildingfrom the component registry'sRegisteredevent.Autofac.Extensions.DependencyInjectionattaches exactly that way on every registration, so ASP.NET Core applications using a multi-service open generic registration hit it deterministically. The fix restores the ordering 9.3.2 had, where the pipeline is built only afterRegisteredhas been raised.If you are on 9.3.3 and register an open generic against more than one service, upgrade. Thanks to @hjalle for the report and for pinning it to the exact line.
Full Changelog: autofac/Autofac@v9.3.3...v9.3.4
9.3.3
What's Changed
KeyedService.AnyKeyfallback adapter was cached and handed to every registry that asked for it, so the first scope to receive it built and disposed its pipeline out from under the rest. Other scopes then failed to add middleware, resolved through a disposed activator, or adapted another scope's registration. Multitenant containers hit this most often.System.Diagnostics.DiagnosticSourceandMicrosoft.Bcl.AsyncInterfaces(netstandard2.0 only) move to 10.0.12.Full Changelog: autofac/Autofac@v9.3.2...v9.3.3
Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)