Update Leiningen to 2.13.0, built from verified source#288
Merged
Conversation
Generated Dockerfile output is committed separately.
Quantisan
approved these changes
Jun 11, 2026
Quantisan
left a comment
Quantisan
left a comment
Owner
There was a problem hiding this comment.
If this is the recommended approach 🤷
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Leiningen 2.13.0 no longer publishes a standalone uberjar (Codeberg has no release asset; only a thin jar is on Clojars), and the only prebuilt one is on the deprecated GitHub mirror. Instead, build the uberjar from source in the image: clone the release tag, verify its GPG signature (Phil Hagelberg's key, the same trust anchor the old prebuilt-jar verification used), bootstrap leiningen-core's dependencies with Maven, run
lein uberjar, and install the result alongside the upstreambin/lein-pkg.This is Phil's recommended approach for packaging leiningen.
2.13.0 requires Java 11+ (its source uses
java.nio.file.Path/of), so lein is dropped for JDK 8 via an exclusion; tools-deps still covers JDK 8.Build deps switch from wget/gnupg to git/gnupg/maven. The old prebuilt-jar download path is gone, so the lein installer hashes are removed.
Verified by building the generated debian-slim (JDK 11) and alpine (JDK 21) images end to end: the signed tag verifies, and both report "Leiningen 2.13.0" and pre-cache Clojure.