Conversation
Introduce comprehensive release notes for v3.3.0, including schema changes, filter updates, and alignment of cardinalities and descriptions across services. Replace placeholder "TBD" entries in v3.2.3 with uniform status message
content/releases/3-3-0.md
Outdated
Comment on lines
145
to
148
| Before upgrading, export existing relationships to ProcessSegmentSpecification as they'll be lost after migration. Then import to update. | ||
|
|
||
| ### OperationsDefinition self-relationship name change. | ||
| The relationship names for a OperationsDefinition to itself have changed from children, parent to defines, definedBy respectively. Check for usage and if used, query out all the relationships, store them, and then re-implement once your schema is updated. |
Collaborator
There was a problem hiding this comment.
Suggested change
| Before upgrading, export existing relationships to ProcessSegmentSpecification as they'll be lost after migration. Then import to update. | |
| ### OperationsDefinition self-relationship name change. | |
| The relationship names for a OperationsDefinition to itself have changed from children, parent to defines, definedBy respectively. Check for usage and if used, query out all the relationships, store them, and then re-implement once your schema is updated. | |
| Before upgrading, export existing relationships to `ProcessSegmentSpecification` to avoid loss after migration. Then import to update. | |
| ### OperationsDefinition self-relationship name change. | |
| The relationship names for an `OperationsDefinition` to itself have changed from `children` and `parent` to `defines` and `definedBy` respectively. Check for usage and if used, query out all the relationships, store them, and then re-implement once your schema is updated. |
Add SHA256 checksums for all v3.3.0 container images to static/checksums/v3.3.0-checksums.txt for verification and reproducibility. Note that the BPMN Engine checksum is pending and marked as `todo`.
…ze-docs into feat/v3.3.0-release
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
2 participants
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.
Introduce comprehensive release notes for v3.3.0, including schema changes, filter updates, and alignment of cardinalities and descriptions across services.
Replace placeholder "TBD" entries in v3.2.3 with uniform status message