[npm] update grunt-esvm to fix cache-conflict bug#7795
Merged
spalger merged 1 commit intoelastic:4.1from Jul 25, 2016
Merged
Conversation
3e70edf to
08f7e2c
Compare
Contributor
|
LGTM |
1 similar comment
Contributor
|
LGTM |
spalger
pushed a commit
to spalger/kibana
that referenced
this pull request
Jul 25, 2016
spalger
pushed a commit
to spalger/kibana
that referenced
this pull request
Jul 25, 2016
spalger
pushed a commit
to spalger/kibana
that referenced
this pull request
Jul 25, 2016
spalger
pushed a commit
to spalger/kibana
that referenced
this pull request
Jul 25, 2016
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
when running 4.1 next to recent versions, grunt-esvm is provided the same temporary directory to store is cache values. Unfortunately the version of grunt-esvm used in 4.1 has a different caching format that modern versions, so an update is required. The
3.2.23.2.3 patch update of grunt-esvm from today uses the version grunt-esvm version number in the cache file path so that these collisions will not occur again.Ultimately, the API is the same between the 1.x and 3.x version. The updates that warranted major version bumps had more to do with questions of stability rather than API changes.