Deploy preview for PR 635

Author: mhauru

pr-previews/635/developers/contributing/index.html

@@ -796,6 +796,7 @@ <h4 class="anchored" data-anchor-id="for-turing.jl-core-developers">For Turing.j
 
 Release notes:
 [YOUR RELEASE NOTES HERE]</code></pre>
+<p>If you are making a breaking release, your release notes must also contain the string <code>Breaking changes</code> somewhere in them (this is mandated by the <code>@JuliaRegistrator</code> bot, described below).</p>
 <p>The <code>@JuliaRegistrator</code> bot will handle creating a pull request into the Julia central package repository and tagging a new release in the repository. The release notes should be a copy-paste of the notes written in <code>HISTORY.md</code> if such an entry exists, or otherwise (for a patch release) a short summary of changes.</p>
 <p>Even core devs should always merge all their code through pull requests into <code>main</code> or <code>breaking</code>. All code should generally be reviewed by another core developer and pass continuous integration (CI) checks. Exceptions can be made in some cases though, such as ignoring failing CI checks where the cause is known and not due to the current pull request, or skipping code review when the pull request author is an experienced developer of the package and the changes are trivial.</p>
 </section>