Release Trino Gateway chart 1.15.0 #315
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
|
This needs to be in one PR with #310, you won't get a green build otherwise |
So should I pull in the commit from that PR or add a commit to the other PR or do something else .. also do they need to be ordered in some specific way as separate commits .. like app update first and then the other stuff? And maybe the chart release as a separate PR? |
|
Closing in favour of #310 |
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.
To be merged after trinodb/trino-gateway#620 and the 15 release and #310
Not sure how we best order these merges .. any idea @willmostly @nineinchnick and @oneonestar ?