Determining what's running in a convex deployment
I'm seeing an unexpected difference between my dev and prod environments (purely due to my application code).
I've rolled dev back as far as I can before schema changes cause the app to break, so I can't manually determine which sha is actually running in production.
For my immediate problem: any chance Convex is stashing metadata for these deploys besides the timestamp?
Broader feedback: it'd be great to have ways to help tie a deployment to a commit.
2 Replies
so I can't manually determine which sha is actually running in productionTo attempt to unblock you, if your deploys to production are through vercel / netlify / github actions, perhaps you can match up the timing of the deploy with the commits there?
Broader feedback: it'd be great to have ways to help tie a deployment to a commit.Yeah definitely -- thanks for raising!
Current issue resolved - I forgot there was a change in my dev data, wasn't a code issue at all 🤦♂️
But yeah, deployment metadata would be awesome 👍