Update from v1.23 to v1.33.1

[ayewo]

Switch to a different branch vercel instead of master so I could apply the manual DB migration step mentioned here in the hope that it will fix the error I am seeming after today's deployment:

[GET] /api/website/1/metrics?type=event&start_at=1662206400000&end_at=1662292799999
12:38:35:35
Function Status:None
Edge Status:500
Duration:468.96 ms
Init Duration: N/A
Memory Used:186 MB
ID:lhr1:lhr1::gcnvq-1662291515141-ebe8b465d73b
User Agent:${user-agent-string}

2022-09-04T11:38:35.895Z	aac46f22-bf7c-4813-9eff-c62ecc2e825c	ERROR	PrismaClientKnownRequestError: Raw query failed. Code: `1054`. Message: `Unknown column 'event_name' in 'field list'`    at RequestHandler.handleRequestError (/var/task/node_modules/@prisma/client/runtime/index.js:28658:13)    at RequestHandler.request (/var/task/node_modules/@prisma/client/runtime/index.js:28640:12)    at async consumer (/var/task/node_modules/@prisma/client/runtime/index.js:29618:18)    at async Proxy._request (/var/task/node_modules/@prisma/client/runtime/index.js:29639:16)    at async __WEBPACK_DEFAULT_EXPORT__ (/var/task/.next/server/pages/api/website/[id]/metrics.js:223:27)    at async Object.apiResolver (/var/task/node_modules/next/dist/server/api-utils/node.js:184:9)    at async NextNodeServer.runApi (/var/task/node_modules/next/dist/server/next-server.js:381:9)    at async Object.fn (/var/task/node_modules/next/dist/server/base-server.js:491:37)    at async Router.execute (/var/task/node_modules/next/dist/server/router.js:213:36)    at async NextNodeServer.run (/var/task/node_modules/next/dist/server/base-server.js:610:29) {  code: 'P2010',  clientVersion: '4.1.1',  

meta: {    code: '1054',    message: "Unknown column 'event_name' in 'field list'"  }}

This branch is based on v1.23 which the last error-free deployment on Nov 2, 2021.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
umami	✅ Ready (Inspect)	Visit Preview	Sep 4, 2022 at 8:38PM (UTC)