Skip to content

Go semantic versioning is broken #16

@9er

Description

@9er

The go docs state that

If the module is version v2 or higher, the major version of the module must be included as a /vN at the end of the module paths

When I'm using this package, go always "updates" to v2.0.4+incompatible. When I'm trying to pin it to the v2.2.1 (because I'm running into the time window bug), go gives me:

go: github.com/asecurityteam/rolling@v2.2.1: invalid version: module contains a go.mod file, so module path must match major version ("github.com/asecurityteam/rolling/v2") 

So the v2 part should probably be added to the module path.

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