Closed Yohe-Am closed 2 months ago
Oh I may have messed up by using the SHA somewhere instead of the tag. But I think this should be 20240415
. I'm not sure why there isn't an entry in the history for 20240224
. \cc @indygreg
I'm worried that the SHA will break consumers so going to merge even though this points to the "last" release.
Hey, looks like something went awry and the
latest-release.json
file now sports a sha instead of the tag. This PR fixes it.