Skip to content

Bump org.clojure:clojure from 1.10.3 to 1.11.2 in the maven group across 1 directory #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dependabot wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Bump org.clojure:clojure from 1.10.3 to 1.11.2 in the maven group across 1 directory #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@
<dependency>
<groupId>org.clojure</groupId>
<artifactId>clojure</artifactId>
<version>1.10.3</version>
<version>1.11.2</version>
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot Apr 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Upgrade Clojure consistently across dependency manifests

Changing only pom.xml to 1.11.2 leaves the actively used Clojure coordinates in deps.edn (deps.edn:2) and the generated template (resources/clj/new/clj_lambda/deps.edn:2) pinned to 1.10.3, so local clojure -X/-T workflows and generated projects continue running the old runtime. This makes the security/version bump incomplete and can produce inconsistent behavior depending on whether tooling reads Maven POM vs deps.edn.

Useful? React with 👍 / 👎.

</dependency>
</dependencies>
<build>
Expand Down
Loading