This is an automated email from the ASF dual-hosted git repository. hboutemy pushed a commit to branch hboutemy-patch-1 in repository https://gitbox.apache.org/repos/asf/maven-site.git
commit ab5fc97433d41b1b556f91e7f7fadea6f01a0bae Author: Hervé Boutemy <[email protected]> AuthorDate: Fri Mar 13 08:01:52 2026 +0100 use section, not title --- content/markdown/guides/development/guide-testing-releases.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/markdown/guides/development/guide-testing-releases.md b/content/markdown/guides/development/guide-testing-releases.md index d86725c2..02893745 100644 --- a/content/markdown/guides/development/guide-testing-releases.md +++ b/content/markdown/guides/development/guide-testing-releases.md @@ -47,7 +47,7 @@ The important thing is that the staged release does not pollute your eventual en This is why clearing the local repository is necessary, but if you are using a repository manager this is also important to clear. The following provides instructions for setting Archiva up in such a way that the artifacts are isolated already. -# Checking Reproducible Builds +## Checking Reproducible Builds Checking binary output, ideally to control that the build is reproducible, can be done by running `verify` (NOT `install`) followed by `artifact:compare` against the staged content:
