You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating new version of versioned model, the createdAt field is also the same as updatedAt date. I think that the createdAt field should also stay the same.
Steps to reproduce the behavior
Create versioned model
Create new entry for this model and save it
Check createdAt date
Update this entry
Check new createdAt date. It is updated, but it shouldn't
Expected behavior
createdAt date should stay the same for all of the versioned (timestamp, when the entry was first created).
System
Node.js version: v18
NPM version: 9.5
Strapi version: v4
Database: mysql
Operating system: macOS/Ubuntu
The text was updated successfully, but these errors were encountered:
Bug report
Describe the bug
When creating new version of versioned model, the
createdAt
field is also the same as updatedAt date. I think that thecreatedAt
field should also stay the same.Steps to reproduce the behavior
createdAt
dateExpected behavior
createdAt
date should stay the same for all of the versioned (timestamp, when the entry was first created).System
The text was updated successfully, but these errors were encountered: