Skip to content

Conversation

@SlapBassist
Copy link
Contributor

This includes the necessary changes to support the latest version of Elasticsearch. It required updating the npm package as well as updating how searches are performed.

fixes #127
fixes #123

Copy link
Member

@nimbinatus nimbinatus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

semver update

},
"author": "Ken Perkins <[email protected]>",
"license": "MIT",
"dependencies": {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Version bump needed on line 3. As I think this is a release that will break previous versions, this release would bump to 2.0.0. See https://semver.org/#summary for more info.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So we have another PR where the version goes to 1.1.0, and this to 2.0.0, and then we have that mongo bump. What makes sense to version for each of these?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After discussion, decided to go to 2.0.0 for both ES and MongoDB updates (breaking changes, but can go under the same version).

@nimbinatus nimbinatus merged commit ace981b into deconst:master Apr 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Upgrade to latest elasticsearch version latch call seems broken at es 6.2

2 participants