Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[email protected] mod issues #561

@umputun

Description

@umputun

I have tried to switch to v1.5.0 from v4.1.2+incompatible but because the version number decreased it caused a downgrade of all other dependencies using chi. For example, I have started with this:

git.example.com/commons/pkg/rest v1.3.2
github.com/go-chi/chi v4.1.2+incompatible
github.com/go-chi/render v1.0.1

After running go get github.com/go-chi/[email protected] I got:

git.example.com/commons/pkg/rest v1.1.0
github.com/go-chi/chi v1.5.1
github.com/go-chi/render v1.0.1

As you can see my pkg/rest downgraded to some old version and such side effects can be very unexpected and unpleasant.

Is there a reason why you decided to go with v1.5.x and not with a more traditional (and less dangerous) approach with v5 (also changing the package name to "/v5")? I'm not sure how to deal with this. In order to avoid those unexpected downgrades I have to have all of my dependencies migrated to v1.5, but unfortunately some of them not under my control.

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