You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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?
Hi! 👋
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.
The text was updated successfully, but these errors were encountered: