Skip to content

Tag release according to golang standards #56

@mooreds

Description

@mooreds

Using the savant release plugin, I see that this client library has releases (1.29.0, 1.28.0) and tags with the same format.

However, the golang way is to preface the version with a v: v1.29.0. This is documented here: https://blog.golang.org/publishing-go-modules and here: https://golang.org/doc/modules/version-numbers

I reviewed the release git plugin ( http://savantbuild.org/docs/plugins/release-git/ ) but was unable to determine how to modify the build.savant file to prepend that v.

This matters because when you pull in the lib as a go module, you are not able to pull in a specific version by tag. Instead, your go.mod file looks like:

% cat go.mod 
module example.com/test/fusionauth

go 1.16

require github.com/FusionAuth/go-client v0.0.0-20210806213402-4c80b3657d94

Discovered in the course of this: FusionAuth/fusionauth-site#867

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