TIKA-4725 - updates to docker release workflow#2807
Open
tballison wants to merge 3 commits into
Open
Conversation
…ika-server for parity with work in tika-docker repo today
Contributor
Author
|
There are multiple ways to go about this. Let me know what you think. This only touches 4.x, and we still have some time to course-correct. |
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
1 participant
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.
make release manual (after the vote)
Change versioning from 4.0.0.0 to 4.0.0-1
Add labels 4.0.0-1 is labeled 4.0.0, and then when 4.0.0-2 comes out we update the label to point to 4.0.0.
Other clean ups we found we needed when pushing 4.0.0-alpha-1.0 from tika-docker.