Skip to content

The outdated mod dependency would cause the version mismatch error. #14

@Calvin-Huang

Description

@Calvin-Huang

Here is the error message when the project's go.mod mismatch to gorm-cli's gorm version.

> gorm-cli db:create_migration change_partner_store_id_typepanic: Open plugin filed. (plugin.Open("./migration/.plugins/connection"): plugin was built with a different version of package gorm.io/gorm/clause)
goroutine 1 [running]:
github.com/iKala/gorm-cli/migrate.NewDB()
        /Users/..../go/pkg/mod/github.com/i!kala/gorm-cli@v0.0.0-20230308011807-f9e560bab2f6/migrate/init_db.go:11 +0x9c
main.main()
        /Users/..../go/pkg/mod/github.com/i!kala/gorm-cli@v0.0.0-20230308011807-f9e560bab2f6/main.go:153 +0xb68

You have no choice but refer to this repo and verify the GORM version in the go.mod. I believe the project shouldn't stick to the CLI-tool's dependency version. It would be more efficient for me if there were auto-update feature or other method to disregard the underlying effort needed to keep up with the version.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions