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.

Sign up for GitHub

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

Jump to bottom

Run go mod tidy after go mod edit -replace #39

Merged
merged 4 commits into from
Feb 17, 2022
Merged

Run go mod tidy after go mod edit -replace #39

merged 4 commits into from
Feb 17, 2022

Commits on Feb 16, 2022

  1. Run go mod tidy after go mod edit -replace 

    This lets you *not* specify a correctly formatted version for a replace
but let you use branch names or `latest` or nothing (which is `latest`)
    @mstoykov
    mstoykov committed Feb 16, 2022
    Configuration menu
    Copy the full SHA
    70961eb View commit details
    Browse the repository at this point in the history

Commits on Feb 17, 2022

  1. Refactor go mod tidy to one place

    @mstoykov
    mstoykov committed Feb 17, 2022
    Configuration menu
    Copy the full SHA
    6f07696 View commit details
    Browse the repository at this point in the history

  2. add -compat=1.17 to tidy so it doesn't blow up with most extensions

    @mstoykov
    mstoykov committed Feb 17, 2022
    Configuration menu
    Copy the full SHA
    ee53c00 View commit details
    Browse the repository at this point in the history

  3. Add README notice that at least go 1.17 is needed

    @mstoykov
    mstoykov committed Feb 17, 2022
    Configuration menu
    Copy the full SHA
    65357af View commit details
    Browse the repository at this point in the history