Source transparency and upstream tracking for tidal-link

[dvzrv]

Hi! :wave:

I maintain the haskell-tidal package on Arch Linux. For upstream source tracking and especially transparency purposes, it would be great to have specific tags that reflect the releases on hackage for tidal-link, as it is developed in the tree of this repository and is a requirement for tidal.

[matthewkaney]

Sure—in this case, the new link release was created in tandem with the main v1.9.5 release. Just so I understand you, you'd like a second tag pointing to the same commit that explicitly identifies the link release as well?

Any preference for the naming convention? Something like link-v1.0.3?

[sss-create]

@dvzrv, is this still in your interest?

[yaxu]

Hi @dvzrv another ping on this as we'll release a new tidal-link version soon

[dvzrv]

Hey! Sorry for the delay, I forgot to answer...

Yes, a separate tag that identifies the link release as mentioned in https://github.com/tidalcycles/Tidal/issues/1075#issuecomment-2053674623 would be great!

[yaxu]

Ok I think @polymorphicengine will do a tidal-link release a bit before the tidal one this time. Please make a tag on this monorepo when you do that Martin thanks!

[polymorphicengine]

all done now, the new tag is here: https://github.com/tidalcycles/Tidal/releases/tag/link-v1.1.0 and on hackage: https://hackage.haskell.org/package/tidal-link-1.1.0