Bump Autofac from 8.4.0 to 9.3.4 - #185
dependabot[bot] wants to merge 1 commit into
Conversation
--- updated-dependencies: - dependency-name: Autofac dependency-version: 9.3.4 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Test Results630 tests 630 ✅ 37s ⏱️ Results for commit ae57794. |
|
Closing as redundant. This PR and #184 are the same Autofac 8.4.0 to 9.3.4 upgrade split across projects: #184 covers Connections.Api and Core, this one covers Connections.Sqlite. Applying either alone fails the build, verified locally: with only #184 applied, restore reports NU1605 Detected package downgrade: Autofac from 9.3.4 to 8.4.0 on Connections.Sqlite. That split is no longer possible on main. As of #186 (APIPUB-151) package versions live in a single src/Directory.Packages.props, so Autofac is one line rather than one per project. #184 has been asked to recreate against that file. |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Updated Autofac from 8.4.0 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
9.3.2
What's Changed
[ServiceKey]attribute by @npease18 (#1495, fixes #1480)New Contributors
Full Changelog: autofac/Autofac@v9.3.1...v9.3.2
9.3.1
What's Changed
Fix per-resolve closure allocation in resolve pipeline (#1493) by @tillig in autofac/Autofac#1494
Full Changelog: autofac/Autofac@v9.3.0...v9.3.1
9.3.0
What's Changed
Full Changelog: autofac/Autofac@v9.2.0...v9.3.0
9.2.0
What's Changed
IStartablethrows during Build (#1392) by @tillig in Dispose container when an IStartable throws during Build (#1392) autofac/Autofac#1485ExternallyOwnedownership for decorators (#1402) by @tillig in Honor ExternallyOwned ownership for decorators (#1402) autofac/Autofac#1486Moduleregistry events when hooks are overridden (#1446) by @tillig in Only subscribe Module registry events when hooks are overridden (#1446) autofac/Autofac#1487GetRegistrationIdextension to expose a registration's unique ID (#1327) by @tillig in Add GetRegistrationId extension to expose a registration's unique ID (#1327) autofac/Autofac#1490Full Changelog: autofac/Autofac@v9.1.0...v9.2.0
9.1.0
This is a pretty big release for Autofac with some major new functionality!
AnyKey Support
First, Autofac now natively supports the concept of
AnyKey. It behaves the same wayAnyKeyworks in Microsoft.Extensions.DependencyInjection, but it is native to Autofac directly. The unit tests here show some very detailed examples of usage, but on a high level:Inject Service Key Into Constructors
The new
[ServiceKey]attribute allows you to inject the service key provided during resolution. This is handy in conjunction withAnyKey. Again, this is similar to the construct in Microsoft.Extensions.DependencyInjection, but with native Autofac.First, mark up your class to take the constructor parameter.
Then when you resolve the class, the service key will automatically be injected.
You can also make use of this in a lambda registration.
Metrics
Some metrics have been introduced that can allow you to capture counters on how long middleware is taking, how often lock contention occurs, and so on.
Set the
AUTOFAC_METRICSenvironment variable in your process totrueor1to enable this feature. You can see the set of counters that will become available here.... (truncated)
9.0.0
Updated Autofac for .NET 10. New current set of target frameworks:
net10.0;net8.0;netstandard2.1;netstandard2.0Breaking Changes
Dropped support for
net6.0,net7.0.Additional Changes
net10.0.Full Changelog: autofac/Autofac@v8.4.0...v9.0.0
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)