File tree Expand file tree Collapse file tree 3 files changed +6
-2
lines changed Expand file tree Collapse file tree 3 files changed +6
-2
lines changed Original file line number Diff line number Diff line change @@ -13,6 +13,8 @@ A release with known breaking changes is marked with:
13
13
// (adjust these in publish.clj as you see fit)
14
14
== Unreleased
15
15
16
+ == v1.2.23 - 2023-02-13 [[v1.2.23]]
17
+
16
18
* Bump stale deps, some of which had vulnerabilities
17
19
(https://github.com/clj-commons/pomegranate/issues/134[#134])
18
20
(https://github.com/lread[@lread])
@@ -46,6 +48,8 @@ A release with known breaking changes is marked with:
46
48
(https://github.com/clj-commons/pomegranate/pull/154[#154])
47
49
(https://github.com/lread[@lread])
48
50
51
+ https://github.com/clj-commons/pomegranate/compare/Release-1.2.1\...v1.2.23[commit log]
52
+
49
53
== v1.2.1 - 2021-04-12
50
54
51
55
* Upgrade wagon libs from 3.2.2 \-> 3.3.4
Original file line number Diff line number Diff line change 20
20
21
21
:aliases {; ; we use babashka/neil for project attributes
22
22
; ; publish workflow references these values (and automatically bumps patch component of version)
23
- :neil {:project {:version " 1.2.22 "
23
+ :neil {:project {:version " 1.2.23 "
24
24
; ; artifact deploy name (and also, by chance, GitHub coordinates)
25
25
:name clj-commons/pomegranate}}
26
26
Original file line number Diff line number Diff line change 2
2
:toclevels: 5
3
3
:toc:
4
4
// DO NOT EDIT: the lib-version parameter is automatically updated by bb publish
5
- :lib-version: 1.2.1
5
+ :lib-version: 1.2.23
6
6
7
7
== Audience
8
8
You want to learn more about how to use the Pomegranate library from your app or library.
You can’t perform that action at this time.
0 commit comments