fix: error when saving global with versioning enabled #12778
Merged
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
paulpopus
previously approved these changes
Jun 12, 2025
paulpopus
approved these changes
Jun 12, 2025
|
🚀 This is included in version v3.43.0 |
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.
When saving a global with versioning enabled as draft, and then publishing it, the following error may appear:
[16:50:35] ERROR: Could not find createdAt or updatedAt in latestVersion.versionThis is due to an incorrect check to appease typescript strict mode. We shouldn't throw if
version.updatedAtdoesn't exist - the purpose of this logic is to add that property if it doesn't exist