First, I thought: Simply downgrade leiningen to the previous version (2.9.8).
However, this turned out to be a bit more complicated than I hoped.
Leiningen is automatically installed (and updated) on all GitHub Actions nodes.
That is convenient and useful.
Thus I leaned toward the workaround suggested on Slack: make sure to turn off the dev profile
or specify the
production profile explicitly, when installing the dependencies:
lein with-profile production install
And to be safe, do the same thing when building the uberjar:
lein with-profile production uberjar
I updated our build script and verified that everything worked as before.