[DO NOT MERGE] Upgrade to 4.1.10 #54
Closed
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
The actual token itself does not need to be random since we send it via headers and cors will prevent destructive cross-domain xhr requests, but the random behavior that did exist would actually break client interactions whenever the server restarted, which is less than ideal. Fixes elastic#5639
Updates What's New for 4.1.4
[forward port] Backport XSS fix for 4.1
Bump node to 0.10.42 for security fixes
Bump node to 0.10.43
Signed-off-by: Tyler Smalley <[email protected]>
[4.1] Bump node to 4.3.2
Unfortunately, the old version of bunyan we were depending on has a compilation failure during npm install, so we need to upgrade it in order to get more builds out of 4.1.
[4.1] Bump bunyan version to 1.7.1
--------- **Commit 1:** [node] Bump node.js to 4.4.4 * Original sha: 470404f * Authored by Jonathan Budzenski <[email protected]> on 2016-05-06T18:31:36Z ------------------------------- **Backported based on diff from PR elastic#7164**
--------- **Commit 1:** Bump .node-version to 4.4.4 * Original sha: 20eaca2 * Authored by Court Ewing <[email protected]> on 2016-05-10T17:47:43Z
We have 8 total zoom levels availabel in the mapping service, but they are zero-indexed.
This can be useful information to log to help determine usage info for different versions of Kibana.
…u keep zooming out. - Restrict tilemap_min_zoom config value to be no less than 1.
We don't need to document every single possible config value in here.
The kibana version is now set in the tile map url directly in the default config logic rather than being appended to all urls. This means that if someone uses a custom map provider, we will not automatically append the kibana version to the url.
[tilemap] Bound zoom
version 4.1.10
|
👍 |
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.
DON'T MERGE THIS BRANCH!! REVIEW ONLY!!
Once we are ready to merge, I will push up a new branch for 4.1.10_NM@alexweltman @sammccord Please review this and see if there is anything I shouldn't have brought in.