Repository navigation
chore(release): prepare v0.6.10 - #70
Merged
Merged
Conversation
Version 0.6.9 -> 0.6.10 on the same 20 version lines in 14 files as v0.6.9. Dockiva Engine stays pinned at af13b2b (no engine changes since v0.6.9).
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
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.
Release v0.6.10
dockivacontext and makes it current. It gives back the previous context when you choose another engine.Version 0.6.9 -> 0.6.10 on the same 20 version lines in 14 files as v0.6.9.
DOCKIVA_ENGINE_REFis unchanged (af13b2b): engine main has had no merges since v0.6.9, and engine PR #33 (the docker version stamp) is still open.This is the first two-digit patch number. The in-app updater compares versions with
golang.org/x/mod/semver, so 0.6.10 counts as newer than 0.6.9.After merge: tag
v0.6.10on the squash commit.