Update docker-compose-pro.yaml - MariaDB update#190
Closed
schopenhauer wants to merge 1 commit intopassbolt:masterfrom
schopenhauer:patch-2
Closed
Update docker-compose-pro.yaml - MariaDB update#190schopenhauer wants to merge 1 commit intopassbolt:masterfrom schopenhauer:patch-2
schopenhauer wants to merge 1 commit intopassbolt:masterfrom
schopenhauer:patch-2
Conversation
Would you consider bumping the MariaDB container to a recent version (e.g. 10.10 or latest) instead of pinning it to the 10.3 release?
Member
|
Hi! Thanks for the contribution! Before merging we will run some tests with it as it is not part of our test matrix at the moment. |
Member
|
This has been merged here 1384af8 Thanks for your contribution! |
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
2 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.
Would you consider bumping the MariaDB container to a recent version (e.g. 10.10 or latest) instead of pinning it to the 10.3 release?