New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CHANGELOG #22
Comments
0.0.25 CHANGELOGBreaking Changes
New features
|
0.0.26 CHANGELOGBreaking ChangesNone Bugs
|
0.0.27 CHANGELOGBreaking changesNone Improvements
|
0.0.28 CHANGELOGBreaking changesNone Bugs |
0.0.29 CHANGELOGBugs
|
0.0.30 CHANGELOGBugs
|
0.0.31 CHANGELOGImprovements#30 Set return type for PersistentSubscriptionSettings.create() so it doesn't break tslint validations. |
0.0.32 CHANGELOGImprovements
|
0.1.0 CHANGELOGNo changes from last release
|
0.1.2 CHANGELOGBreaking changesNone New feature
|
0.1.2 CHANGELOG - project renameNo changesNew project name/package name: node-eventstore-client Sorry for the annoyance but the project name was bugging me for a while. Also I will probably start a go version of the port soon. This naming scheme is more clear. |
0.1.3 CHANGELOGBreaking changesNone Bugs
|
0.1.4 CHANGELOGBugs |
0.1.5 CHANGELOGBreaking changes
Improvements
|
0.1.6 CHANGELOGBreaking changesNone Improvements
|
0.1.7 CHANGELOGBreaking changesNone Improvements
|
0.1.8 CHANGELOGBreaking changesNone Bugs
|
0.1.9 CHANGELOGBreaking changesNone New features
|
0.1.10 CHANGELOGBreaking changesNone Improvements
|
0.2.0 CHANGELOGBreaking changes
|
0.1.11 / 0.2.1 CHANGELOGBug fixes
NotesPackage were pushed in the wrong order, so latest version is 0.1.11 instead of 0.2.1. This should have no impact on the existing users. New users will get 0.1.11. Difference between 0.1.x and 0.2.x
|
0.2.2 CHANGELOGEnhancement
|
0.2.3 CHANGELOGNew feature
|
0.2.4 CHANGELOGImprovements
|
0.2.5 CHANGELOG0.1.12 CHANGELOGBugs
Also here's some important notes about the subscriptionDropped / reconnect behavior. CAVEAT: catchUpSubscriptions will only continue after reconnect if they reached their "live processing" phase, i.e. the liveProcessingStarted event was fired. If the subscription dropped during the catchUp phase the subscription will NOT continue automatically after a reconnect. |
0.2.7 CHANGELOGBugs
|
0.2.8 CHANGELOGBugs
|
0.2.9 CHANGELOGBugs
|
0.2.10 CHANGELOGBugs
|
0.2.13 CHANGELOGBugs#85 Fixed an issue where AppendToStream with expected version any and existing event did result in the event being saved. It was due to a protobufjs issue. Was fixed after updating it to latest version. |
0.2.14 CHANGELOGBugs#91 Isolate protobufjs library to work well with bad neighbor libraries |
0.2.15 CHANGELOGBugs
|
0.2.16 CHANGELOGBugs |
0.2.17 CHANGELOGBugs
|
0.2.18 CHANGELOGBugs |
In response to issue #21, I've decided to create this thread to track changes between released version of the npm package.
Make sure you subscribe to this issue if you want to be notified of changes in the API.
The text was updated successfully, but these errors were encountered: