Update pelias-config to the latest version 🚀 #231
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
This was changed in pelias/config#60 to match the Elasticsearch default. It helps people who use the defaults to be able to scale a little bit further out of the box.
orangejulius
force-pushed
the
greenkeeper/pelias-config-2.12.0
branch
from
a4ecb43
to
dc79675
Compare
orangejulius
approved these changes
Jul 28, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version 2.12.0 of pelias-config just got published.
The version 2.12.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of pelias-config.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
v2.12.0<a name"2.12.0">
2.12.0 (2017-07-27)
Features
Commits
The new version differs by 10 commits.
6276839Merge pull request #62 from pelias/elasticsearch-2.4-apia5bc5fcfeat: change default Elasticsearch API version to 2.4f77818fMerge pull request #60 from pelias/default_es_shards815b9c7Changed default elasticsearch num of shards to 525fb82afeat: Merge pull request #59 from pelias/default-libpostal06521bfDefault to enabling libpostal in the api9815c2efeat: Merge pull request #57 from pelias/return-joi-sanitized-config-from-schema5b7e1dfgenerated now returns validated config with defaults and types massagedab40917Merge pull request #56 from pelias/repo-crawler-add-dep-check8947b2aupdate npm-check to ignore updatesSee the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴