Finbuckle.MultiTenant Version Policy #887
Labels
Comments
AndrewTriesToCode
added a commit
that referenced
this issue
Oct 12, 2024
BREAKING CHANGE: This commit brings the release into alignment with the new version policy. See #887 for details.
AndrewTriesToCode
added a commit
that referenced
this issue
Oct 12, 2024
BREAKING CHANGE: This commit brings the release into alignment with the new version policy. See #887 for details.
github-actions bot
pushed a commit
that referenced
this issue
Oct 12, 2024
# [8.0.0](v7.0.2...v8.0.0) (2024-10-12) * feat!: version policy update ([#888](#888)) ([487a3a6](487a3a6)) ### Bug Fixes * BasePathStrategy no longer breaks the strategy chain ([#884](#884)) ([3263eff](3263eff)) * prevent duplicate key annotation in AdjustKey() ([#883](#883)) ([f75ba2c](f75ba2c)) * removed unused parameter from WithPerTenantRemoteAuthenticationConvention ([#886](#886)) ([dd17ab5](dd17ab5)) ### Features * add GetAllAsync() support for HttpRemoteStore ([#848](#848)) ([4208149](4208149)) * added the Echo Store. ([#807](#807)) ([a3e5eee](a3e5eee)) * strategies return null on invalid context type ([#885](#885)) ([9834575](9834575)) ### BREAKING CHANGES * This commit brings the release into alignment with the new version policy. See #887 for details. * Included strategies for ASP.NET Core would throw an exception if the passed context was not an `HttpContext` type. Now they will return null indicating no identifier was found.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Beginning with Finbuckle.MultiTenant 8.0.0 major version releases align with .NET major version releases and target all
Microsoft supported major .NET versions at the time of initial release.
New development focuses on the latest Finbuckle.MultiTenant release version while critical security and severe bug
fixes will be released for prior versions which target .NET versions supported by Microsoft.
In general, you should target the version of Finbuckle.MultiTenant that matches your .NET version.
This mean 8.0.0 will support .NET 6, 7, and 8 since those were actively supported by Micrsofot when .NET 8 was released.
9.0.0 will be released when .NET 9 is released and will target .NET 8 and .NET 9 since both .NET 6 and 7 will no longer be actively supported by Microsoft.
The text was updated successfully, but these errors were encountered: