-
Notifications
You must be signed in to change notification settings - Fork 86
chore(release): bump to 2.1.3. #156
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
Changes from 2 commits
d3fc749
61db46a
1c85faf
7f36279
84cca27
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -9,6 +9,13 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0. | |
| ### Deprecated | ||
| * The UMD build of the SDK now assigns the SDK namespace object to `window.optimizelySdk` rather than to `window.optimizelyClient`. The old name still works, but on its first access a deprecation warning is logged to the console. The alias will be removed in the 3.0.0 release. | ||
|
|
||
| ## [2.1.2] - August 21, 2018 | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think this release is 2.2.0. The current release on npm is 2.1.2.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. :( this means the current production package is sending the wrong version. Nice catch though. I'd argue for 2.1.3 because we aren't introducing any new features, at least that's what we've been using as a basis for minor version bumps.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think I bumped the version in v2.1.x branch only (#126), since that's the only place the patch version is relevant.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Does that mean that the changelog entry for 2.1.2 never escapes the v2.1.x branch? That's not good :\
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The changelog is correct/complete on all released tags, at least (none of which are defined in master). I can see the argument for keeping master up-to-date with the "current" branch though, so we can change it. |
||
|
|
||
| ### Fixed | ||
| - Send all decisions for the same event in one snapshot. ([#155](https://github.com/optimizely/javascript-sdk/pull/155)) | ||
| - Give Node.js consumers the unbundled package ([#133](https://github.com/optimizely/javascript-sdk/pull/133)) | ||
| - Prevent crash when `http`/`https` emits an error by adding an 'error' listener ([#123](https://github.com/optimizely/javascript-sdk/pull/123)) | ||
|
|
||
| ## 2.1.1 | ||
| June 19, 2018 | ||
|
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please move the stuff under
Unreleasedinto the new 2.2.0 entry.