v1 migration: mastra_scorers column not renamed
StorageEval
After upgrading to v1.0.0-beta.19, I'm getting this error :
The codemod updated my code but the DB still has
- Question:
Should this be automated?
init() adds new columns but doesn't rename existing ones.
Should the codemod handle DB migrations, or is manual migration the expected approach?
- Environment:
@mastra/core@1.0.0-beta.19,
@mastra/pg@1.0.0-beta.11
Thank you for your help
"column \"requestContext\" of relation \"mastra_scorers\" does not exist"The codemod updated my code but the DB still has
runtimeContext- Question:
Should this be automated?
init() adds new columns but doesn't rename existing ones.
Should the codemod handle DB migrations, or is manual migration the expected approach?
- Environment:
@mastra/core@1.0.0-beta.19,
@mastra/pg@1.0.0-beta.11
Thank you for your help
