feat: upgraded score-go to 1.1.0 and call upgrade function #50
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
astromechza
force-pushed
the
wal-9376-update-score-spec
branch
2 times, most recently
from
db6f434
to
067d205
Compare
astromechza
requested review from
Nilsty,
johanneswuerbach,
delca85 and
sujaya-sys
…or deprecated fields Signed-off-by: Ben Meier <[email protected]>
astromechza
force-pushed
the
wal-9376-update-score-spec
branch
from
067d205
to
d93f94f
Compare
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.
This upgrades score-compose to score-go 1.1.0 (https://github.com/score-spec/score-go/releases/tag/v1.1.0). The only real change affecting score compose is some fixes to the service protocol strings and the fixed naming of volume read only. The old form of read_only will continue to work due to the call to
ApplyCommonUpgradeTransforms.The example files and tutorials have been updated in score docs.
We also start adding CLI unit tests that are hopefully more easy to run than the robot e2e tests.