Update to aas-core-meta, codegen, testgen 77d3442, 4433d092, 61106b572 #48
Conversation
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
We update the development requirements to and re-generate everything with: * [aas-core-meta 77d3442], * [aas-core-codegen 4433d092] and * [aas-core3.0-testgen 61106b572]. Notably, we propagate the fix for V3.0 in the meta-model which reverted the order of ``data_specification`` and ``data_specification_content``. This was necessary so that the XML schemas for V3.0 remain backwards compatible. [aas-core-meta 77d3442]: aas-core-works/aas-core-meta@77d3442 [aas-core-codegen 4433d092]: aas-core-works/aas-core-codegen@4433d092 [aas-core3.0-testgen 61106b572]: aas-core-works/aas-core3.0-testgen@61106b572
mristin
deleted the
Update-to-aas-core-meta-codegen-testgen-77d3442-4433d092-61106b572
branch
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.
We update the development requirements to and re-generate everything with:
Notably, we propagate the fix for V3.0 in the meta-model which reverted the order of
data_specificationanddata_specification_content. This was necessary so that the XML schemas for V3.0 remain backwards compatible.