Hi there! You are recieving this because I believe you are packaging Rust or are otherwise sensitive to changes in Rust deployment.
We just released 1.15.1, and it was a difficult release where we made
a mistake that impacts you. The TL;DR is that we force-pushed the
1.15.1 tag and if you rely on Rust's git tags for your processes, you
should take steps to ensure you have the right value for it. git fetch origin --tags should be sufficient.
Details: for the 1.15.0 and 1.15.1 releases our process involved tagging the release a day before the release, then making the release, then signing the tag. This ended up being a mistake because just signing a tag requires a force push to rewrite it. But furthermore, when we did the 1.15.1 release we ended up halting the initial attempt at the release at the last moment and appending another patch. Even though we knew this was problematic for the tag we decided to continue with our process as designed rather than take the risk of making last-minute changes. Pracitaclly, if you or your infrastructure has fetched tags in the last few days, you may have the wrong tag for 1.15.1.
This also impacted the 1.15.0 tag, but only in that it went from unsigned to signed. The commit remained the same.
We will change the process to not involve retagging before doing another release.
I apologize for the incovenience. I'm happy to take suggestions.