Skip to content

Doc: Trusted Checksums Summary File Procedure#1886

Open
adambkaplan wants to merge 1 commit into
apache:masterfrom
adambkaplan:trusted-checksums-procedure
Open

Doc: Trusted Checksums Summary File Procedure#1886
adambkaplan wants to merge 1 commit into
apache:masterfrom
adambkaplan:trusted-checksums-procedure

Conversation

@adambkaplan
Copy link
Copy Markdown

@adambkaplan adambkaplan commented May 22, 2026

Document the procedure to save Trusted Checksum summary files to version control. This procedure utilizes the .mvn/config file for consistent invocation and the ${session.rootDirectory} variable, which is only available in Maven 3.9.x. The configuration was taken from an example "locked down" repository provided by @cstamas. [1]

Unfortunately, saving Trusted Checksum summary files to version control can cause dependency management tools like Renovate and GitHub Dependabot to break builds. It is my hope that with improved documentation, the dependency management tool ecosystem will be able to appropriately update these trusted checksum files if present.

[1] https://github.com/ipfs-shipyard/java-ipfs-http-client

Following this checklist to help us incorporate your
contribution quickly and easily:

  • Your pull request should address just one issue, without pulling in other changes.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Each commit in the pull request should have a meaningful subject line and body.
    Note that commits might be squashed by a maintainer on merge.
  • Write unit tests that match behavioral changes, where the tests fail if the changes to the runtime are not applied.
    This may not always be possible but is a best-practice.
  • Run mvn verify to make sure basic checks pass.
    A more thorough check will be performed on your pull request automatically.
  • You have run the integration tests successfully (mvn -Prun-its verify).

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

Document the procedure to save Trusted Checksum summary files to
version control. This procedure utilizes the `.mvn/config` file for
consistent invocation and the `${session.rootDirectory}` variable,
which is only available in Maven 3.9.x. The configuration was taken
from an example "locked down" repository provided by @cstamas. [1]

Unfortunately, saving Trusted Checksum summary files to version control
can cause dependency management tools like Renovate and GitHub
Dependabot to break builds. It is my hope that with improved
documentation, the dependency management tool ecosystem will be able to
appropriately update these trusted checksum files if present.

[1] https://github.com/ipfs-shipyard/java-ipfs-http-client

Signed-off-by: Adam Kaplan <adam@adambkaplan.com>
@adambkaplan adambkaplan force-pushed the trusted-checksums-procedure branch from b6043d3 to aadfd0c Compare May 22, 2026 03:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant