[backport] PR #7490 to 4.x - Build artifact names for unified release process #7809
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
--------- **Commit 1:** Build artifact names for unified release process These changes are necessary for Kibana to be compatible with Elastic's unified release process from 5.0 onward. The way artifacts get created has not changed, but the naming conventions have. * Original sha: c550bbc * Authored by Court Ewing <court@epixa.com> on 2016-06-16T11:58:31Z **Commit 2:** README is 5.0.0-alpha4 to match package.json We bumped the version in package.json, but we never changed it in the readme. * Original sha: 55c4993 * Authored by Court Ewing <court@epixa.com> on 2016-06-16T20:52:58Z
epixa
force-pushed
the
jasper/backport/7490/4.x
branch
from
8f8ed0e
to
2abfc65
Compare
epixa
changed the title
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.
Backport PR #7490
Commit 1:
Build artifact names for unified release process
These changes are necessary for Kibana to be compatible with Elastic's
unified release process from 5.0 onward. The way artifacts get created
has not changed, but the naming conventions have.
Commit 2:
README is 5.0.0-alpha4 to match package.json
We bumped the version in package.json, but we never changed it in the
readme.