We recently had a silent failure where the docs weren't updated for 6+ weeks, including missing the 33.0.0 release (and consequentially not properly updating the "Breaking Changes" doc for that release). This went unnoticed until it was reported to us in #672.
This PR adds a scheduled audit which compares the SHA of the latest docs update from the website (added here as a <meta> tag) to the last SHA on the current release branch on e/e. Any failures of this audit workflow should get picked up and reported through our usual workflow failure reporting.
We recently had a silent failure where the docs weren't updated for 6+ weeks, including missing the 33.0.0 release (and consequentially not properly updating the "Breaking Changes" doc for that release). This went unnoticed until it was reported to us in #672.
This PR adds a scheduled audit which compares the SHA of the latest docs update from the website (added here as a
<meta>tag) to the last SHA on the current release branch one/e. Any failures of this audit workflow should get picked up and reported through our usual workflow failure reporting.