Releases: jet/equinox
Stable Release
Thanks to @ameier38 @AndrewRublyov @asetda @CumpsD @DSilence @eiriktsarpalis @jakzale @jgardella @Kelvin4702 @Rajivhost @Szer for notable contributions since 1.x
See CHANGELOG.
Some notable highlights:
Core
- The
Cache
type and relatedICache
interface now lives inEquinox.Core
rather than being store-specific 🙏 @DSilence Stream
now admits an optional'Context
to facilitatecorrelationId
/causationId
wiringStream
now admits aResolverOption.AllowStale
to facilitate stale/optimistic cached readsFsCodec
repository now hostsIEventCodec
interface,StreamName
helper and concrete serializer bindings- Various items exposed and polished for usage from Propulsion and dotnet-templates
- new
Propulsion
repository now hostsProjection
Streaming / Feed management logic that has rested in here in recent times - new
eqx dump
supports dumping events and/or [decompressed] snapshots to the screen
NEW SqlStreamStore support
Cosmos
- Interoperable with v1 storage formats - i.e. it's intended to be safe to use 1.x and 2.x libs in any combination
- Added
RollingState
andCustom
modes, enabling one to use event sourcing facilities to manage a single rolling document state efficiently - Renaming (using Cosmos SDK terms from V3, i.e. Collection -> Container) and medium density renamespacing hence v2
eqx init
supports updating RU allocations, and database level assignments- new
eqx stats
dumps event counts for Cosmos
Circling drain for final V2 release
Thanks to @ameier38 @AndrewRublyov @asetda @DSilence @eiriktsarpalis @jakzale @jgardella @Kelvin4702 @Rajivhost @Szer for notable contributions since 1.x
The V2 code is complete and resilient, with no known issues or planned hardening work.
However, we're not actually baking a 2.0.0
non-preview release until the last responsible moment which will be before 20 March, 2020 - the next geo-equinox.
See CHANGELOG.
Some notable highlights:
Core
- The
Cache
type and relatedICache
interface now lives inEquinox.Core
rather than being store-specific 🙏 @DSilence Stream
now admits an optional'Context
to facilitatecorrelationId
/causationId
wiringStream
now admits aResolverOption.AllowStale
to facilitate stale/optimistic cached readsFsCodec
repository now hostsIEventCodec
interface,StreamName
helper and concrete serializer bindings- Various items exposed and polished for usage from Propulsion and dotnet-templates
- new
Propulsion
repository now hostsProjection
Streaming / Feed management logic that has rested in here in recent times - new
eqx dump
supports dumping events and/or [decompressed] snapshots to the screen
NEW SqlStreamStore support
Cosmos
- Interoperable with v1 storage formats - i.e. it's intended to be safe to use 1.x and 2.x libs in any combination
- Added
RollingState
andCustom
modes, enabling one to use event sourcing facilities to manage a single rolling document state efficiently - Renaming (using Cosmos SDK terms from V3, i.e. Collection -> Container) and medium density renamespacing hence v2
eqx init
supports updating RU allocations, and database level assignments- new
eqx stats
dumps event counts for Cosmos
Dependencies tidyup, small fixes
C# interop fixes, Relax DocDb dependency version
- Various tweaks to make C# calling code less messy, see #81
- Relax version requirements for DocDb to 1.17 on
net461
and 2.0.0 onnetstandard2.0
#84 - Add
Equinox.Cosmos.Core.EventData
#85
Code is identical to 1.0.3-rc3
Related release: Equinox.Templates
1.1.1
Pre-release with improved C# support
- Preview release of #81 to facilitate cleanup of C# sample in jet/dotnet-templates#5
Initial with minor bugfix to remove accidental transitive dependency
Remove accidental transitive dependency on MinVer @eiriktsarpalis
Initial release with Cosmos support
Clean release including Cosmos support - single known minor issue is that there's an unintended transitive dependency on MinVer, which will be removed in 1.0.2
1.0.1-rc1
Pre-merge validation release for Cosmos branch
0.0.3-rc2 Cleanup
0.0.3-rc1
Dry-run release to validate ability to cleanly publish Equinox.Cosmos
NB included Equinox.Cosmos package denoted 1.0.0, which is equivalent to 1.0.1 series but does should not be used as the related components are versioned per the tag.