Open ripytide opened 5 months ago
I don’t have a good sense of how much value this would add. But it can’t hurt, so if you’re happy to collect the hashes I’m happy to create tags for them all.
v0.17.0
: 543ec60bec957b900e909cf7eb97b3fef4ab6359
v0.18.0
: ae1d097144951ea34246d23a63303e841b7a1a81
v0.19.0
: 9225ee200c635fe495c9e98c93ff43865385a980
v0.19.1
: a64f803b4c38f5435ca52000ac236ff2d2a990b9
v0.19.2
: 3612eb2eab89cbba370157a51e87f81cc6f541c3
v0.20.0
: 3490a2e5431b365706698eccf80245fa84c404e3
v0.21.0
: b25182960df78a439ce393b00d253fd8cd2c4fdf
v0.22.0
: 4e6694e05ba8df2dab9230aeb8f6178864589923
v0.23.0
: 6a7adf4bfc75e506452c43681ab9b9a90ecb4081
v0.24.0
: 1c756b3f8d1cd655f1d35f54d9f4bfbc00aa6452
v0.25.0
: 44bbf5e7efd8d9de41ffafc2be2a0696cfecfb4b
Following from #497 I know we've now started tagging future releases. I think cargo records the current commit SHA hash in a
.carge_vcs_info.json
file in the published compressed crate file so it might be possible to add tags for past releases also. I can go through each past release and collect the SHA hashes if we're interested in adding them as tags.