Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

In version 1.0.0, Mergo moves to a vanity URL: dario.cat/mergo. Can update to the latest version? #3149

Closed
yeqiaojun opened this issue Jan 6, 2024 · 6 comments · Fixed by #3297
Labels
question Further information is requested

Comments

@yeqiaojun
Copy link

No description provided.

@yeqiaojun yeqiaojun added the question Further information is requested label Jan 6, 2024
Copy link

dosubot bot commented Jan 6, 2024

🤖

Hello @yeqiaojun!

I'm Dosu, a friendly bot here to assist you with bugs, answer your queries, and help you become a contributor to Kratos. I'm here to help while we wait for a human maintainer. If you have any questions or need any assistance, feel free to ask. Let's make Kratos even better together!

Yes, you can update Mergo to the latest version. However, since Mergo has moved to a vanity URL in version 1.0.0, you need to update the import path in your code and the module path in your go.mod file.

Here's how you can do it:

  1. Update the import paths in your code from github.com/imdario/mergo to dario.cat/mergo.

  2. Update the module path in your go.mod file from github.com/imdario/mergo v0.3.16 to dario.cat/mergo v1.0.0 or the latest version.

Your updated go.mod file should look like this:

module github.com/go-kratos/kratos/v2

go 1.19

require (
	// other dependencies...
	dario.cat/mergo v1.0.0
	// other dependencies...
)

Please note that you should replace v1.0.0 with the latest version of Mergo if it's not the latest one. The current version of Mergo used in the Kratos repository is v0.3.16, as indicated in the go.mod file. The latest version of Mergo available at the vanity URL dario.cat/mergo is not mentioned in the provided context. However, you can check the latest version on the Mergo's new URL.

If you have any other questions or need further clarification, feel free to ask.

Sources


This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

@amao12580
Copy link

same issuse

@kratos-ci-bot
Copy link
Collaborator

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


same issue

@amao12580
Copy link

please quick fix the require version

@Windfarer
Copy link
Member

According to mergo README https://github.com/darccio/mergo?tab=readme-ov-file#100

If the vanity URL is causing issues in your project due to a dependency pulling Mergo - it isn't a direct dependency in your project - it is recommended to use replace to pin the version to the last one with the old import URL:

replace github.com/imdario/mergo => github.com/imdario/mergo v0.3.16

@yangyile1990
Copy link

same issue.

when I want to update all my dependency packages to lastest version by this command:

admin@lele-de-MacBook-Pro uvxlan % go get -u ./...

go: github.com/imdario/mergo@v1.0.0: parsing go.mod:
        module declares its path as: dario.cat/mergo
                but was required as: github.com/imdario/mergo
        restoring github.com/imdario/mergo@v0.3.16

I got an error message.

So I check the reason:

admin@lele-de-MacBook-Pro uvxlan % go mod why github.com/imdario/mergo

# github.com/imdario/mergo
gitlab.yyle.com/golang/uvdemo.git/main_kratos/main_kratos_config
github.com/go-kratos/kratos/v2/config
github.com/imdario/mergo

So please fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants