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
Plan to synchronize version numbers after all features are developed. Synchronizing version numbers has the following benefits:
Synchronize the commit hash of the binary engine to confirm that the commit engine is the latest and most stable.
The version of the dynamic library is synchronized. If the binary is the same, the C API of the dynamic library can complete the synchronization.
Function identification, Prisma TS client is a template of the orm package, which makes Prisma official stabilization more useful for this package.
Automatic requirement submission, using CI to monitor the release of Prisma node package, and then automatically submitting Issue has helped us to synchronize functions.
The text was updated successfully, but these errors were encountered:
It is worth mentioning that before the synchronization version, the version number before the latest version number of prisma can be released as the version we are wrong
The version number of the Node prisma package has been released to 4.3 or newer(https://www.npmjs.com/package/prisma).
Plan to synchronize version numbers after all features are developed. Synchronizing version numbers has the following benefits:
orm
package, which makes Prisma official stabilization more useful for this package.The text was updated successfully, but these errors were encountered: