Skip to content

New v0.1.1 tag doesn't match v0.1.0 in version.go #183

@wking

Description

@wking

We just tagged v0.1.1 yesterday, but I think the plan had been to make the opening tag v0.1.0 (which matches SemVer's first FAQ entry). In any event, #173 went with v0.1.0. It would be nice if the tag and the version.go constant matched each other ;), so I'd suggest bumping both to v0.1.2 to avoid any ambiguity.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions