Releases: csf-dev/CSF.ORM
v3.0.0
This is a non-backwards compatible release, primarily owing to the bumped dependency version caused by #43. It is not expected that the cost of upgrade from v2.x should be particularly high though. It is expected that for the majority of consumers, the package will upgrade seamlessly.
Changelog
- Resolve #41 - Crash bug when setting identity values using a 'compatible' (if not precisely matching) value type
- Resolve #42 - The transaction provider may now be interrogated to determine if a transaction is already active
- Resolve #43 - Crash bug when using the persistence tester with NHibernate, due to lazy-loading in a disposed session
- Resolve #44 - Correction to
async
methods (they must return aTask
and notvoid
)
v2.0.3
This is a backwards-compatible bugfix release. It solves two primary issues:
- #39 - a crash issue when using
Theorise
with the in-memory implementation - #40 - a crash when creating identity instances
It also attempts to address an intermittent issue relating to testing, whereby the AppVeyor build would fail sometimes. I'm not entirely sure that it is completely fixed, but the changes made (merging some test projects) will not be harmful.
Additionally, whilst working on this release, some excluded tests were found. These have been re-engineered and re-enabled so that they are now being executed again.
v2.0.2
This release is a single-issue fix for #38. Due to a project/packaging error, a class had been omitted from the package CSF.Entities.
This has been deemed a bugfix because although restoring it means that 2.0.2 contains more functionality than 2.0.1 - this was functionality which was expected/intended to be a part of 2.0.1. Only the CSF.Entities package has been published at a new version to NuGet; the other packages are unchanged from 2.0.1.
v2.0.1
This is a bugfix release, addressing a packaging error in 2.0.0 which meant that the NHibernate 4 and 5 packages could not be installed due to a 'phantom' dependency.
Changelog
v2.0.0
This is the first publicly-released version of the ORM abstractions and implementations library, since moving into this monorepo.
All of the NuGet packages contained within this repo are published at version 2.0.0.
Why not v1.0.0?
The reason for beginning at version 2.0.0 and not 1.0.0 is because some of the constituent packages have already been released under the same names, at version 1.x. In places where package names didn't need to change and were kept, this would have caused confusion if I had kept with a 1.x numbering scheme. Starting with 2 makes it clear that this is a major/breaking change.