-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add property for supported runtime versions #146
Labels
enhancement
New feature or request
Comments
8 tasks
Agreed to go with the semver proposal in the define kick-off. |
nikku
pushed a commit
that referenced
this issue
Dec 6, 2024
`engines` is a new property that allows templates to declare compatibility with other run-time provided engines. Closes #146
nikku
pushed a commit
that referenced
this issue
Dec 6, 2024
`engines` is a new property that allows templates to declare compatibility with other run-time provided engines. Closes #146
nikku
added a commit
to bpmn-io/element-templates-validator
that referenced
this issue
Dec 6, 2024
feat: support `engines` meta data Related to camunda/camunda-modeler#4530 Related to camunda/element-templates-json-schema#146
12 tasks
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Related to camunda/camunda-modeler#4530
What should we do?
Add a property that indicates which Camunda Platform runtime versions are supported by the template.
Proposal based on the documentation is to use semver.
Note:
Why should we do it?
Allow detection of incompatibilities between Camunda runtime version and runtime version supported by element template as described in Element Template Runtime versions epic.
The text was updated successfully, but these errors were encountered: