This repository has been archived by the owner on Nov 30, 2023. It is now read-only.
Implement image / dev container specific versioning #242
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Implements #209 which is required for #155 (VS Online image).
This adds a
definitionVersionproperty intodefinition-build.jsonthat, if specified, is used for the version of the image that is generated whenever a release is specified. (Specifying a branch like master still results in the 'dev' version.)If no
definitionVersionis specified, the release version is used instead. All current definitions will behave this way since #155 is the first one that would use definition specific versioning and that will be a separate PR.