Giters

ross-spencer / spargo

SPARQL helper library for Golang

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Fixup tags

ross-spencer opened this issue · comments

commented

For all the work tagging, it turns out Go mod and docs are looking for the format v.x.x.x specifically with the v: https://dave.cheney.net/2016/06/24/gophers-please-tag-your-releases

commented

Recipe for renaming annotated tags:

git tag -a new old^{}
git tag -d old
git push origin new :old

The {} syntax is especially important for annotated tags and making sure we point at the original commit from that tag.

Reference: https://stackoverflow.com/a/5719854

commented

Alright, 4 tags available here now: https://github.com/ross-spencer/spargo/releases

Will measure the success of this endeavor shortly when we see the pkg.go pages update: here.

commented

v1.0.0 and v2.0.0 have been rolled back to v0.1.0 and v0.2.0 respectively. If this package ever gets out of v0.x.x aka "experimental" we'll need to be more sure about what an interface change looks like. Not my proudest day.

Info about the releases:

I am expecting the golang servers to update at some point. Closing until they prove otherwise.

For reference, information about creating a v2 module: https://blog.golang.org/v2-go-modules NB. this package isn't even close to being setup to be able to do that afaict.

commented

Similar issue for this person here: golang/go#44521

commented

Potential CI addition to have tags updated sooner by pkg.go.dev: https://stackoverflow.com/a/61974058

commented

Retract directive:

TODO:

  • v0.2.0 needs to become 1.0.1. It needs its agent/version string updating. It will become the new stable. Ideally there will be no more "breaking" changes.
  • v0.1.0 needs to become 0.3.0. It needs its agent/version string updating.
  • v1.0.0 is retracted.
  • v0.2.0 becomes v1.0.1.
commented

You can stay on pre-v1 if that's preferable by creating a new 1.0.1 release that is itself retracted, and retracts v1. This would make 0.2.0 the latest version

`As an example, consider a case where the author of module example.com/m publishes version v1.0.0 accidentally. To prevent users from upgrading to v1.0.0, the author can add two retract directives to go.mod, then tag v1.0.1 with the retractions.

retract (
v1.0.0 // Published accidentally.
v1.0.1 // Contains retractions only.
)
When a user runs go get example.com/m@latest, the go command reads retractions from v1.0.1, which is now the highest version. Both v1.0.0 and v1.0.1 are retracted, so the go command will upgrade (or downgrade!) to the next highest version, perhaps v0.9.5.`

commented

Resolved via 03b783b.

$ go list -m -versions
github.com/ross-spencer/spargo v0.0.2 v0.0.3 v0.3.0 v0.4.0

Thanks @richardlehane for the help!