From 688058398619fa659eb990776570172870c08999 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Fri, 17 Jul 2026 13:53:33 +0000 Subject: [PATCH] Release new version --- .changeset/true-moose-pick.md | 25 ------------------------- CHANGELOG.md | 26 ++++++++++++++++++++++++++ lib/build.gradle | 2 +- package.json | 2 +- 4 files changed, 28 insertions(+), 27 deletions(-) delete mode 100644 .changeset/true-moose-pick.md diff --git a/.changeset/true-moose-pick.md b/.changeset/true-moose-pick.md deleted file mode 100644 index 526ee4f..0000000 --- a/.changeset/true-moose-pick.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -"evervault-java": minor ---- - -Upgrade BouncyCastle from `bcprov-jdk15on:1.70` to `bcprov-jdk18on:1.84` to -pick up outstanding security fixes and move off the unmaintained `jdk15on` -line. - -**Action required for some consumers.** The Maven coordinate changed -(`bcprov-jdk15on` → `bcprov-jdk18on`), but both jars ship classes under -identical `org.bouncycastle.*` packages. If your project also pulls in -`bcprov-jdk15on` directly or transitively via another dependency, you will -end up with both jars on the classpath — build tools don't dedupe across -different artifact ids. Classloader ordering then decides which BC "wins" -at runtime, which can cause subtle crypto failures. Evict any remaining -`bcprov-jdk15on` from your dependency tree (Gradle `exclude`, Maven -``), or add an explicit dependency on `bcprov-jdk18on` at the -version you want. - -`InvalidCipherException` gains a new public constructor -`InvalidCipherException(Throwable cause)` that preserves the underlying -cause. The existing `InvalidCipherException(InvalidCipherTextException)` -constructor is now `@Deprecated` because it leaks BouncyCastle types into -the SDK's public API; it will be removed in the next major release. Switch -any direct construction to the `Throwable` overload. diff --git a/CHANGELOG.md b/CHANGELOG.md index 1e22efb..b9b3896 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,31 @@ # evervault-java +## 4.3.0 + +### Minor Changes + +- ded16a9: Upgrade BouncyCastle from `bcprov-jdk15on:1.70` to `bcprov-jdk18on:1.84` to + pick up outstanding security fixes and move off the unmaintained `jdk15on` + line. + + **Action required for some consumers.** The Maven coordinate changed + (`bcprov-jdk15on` → `bcprov-jdk18on`), but both jars ship classes under + identical `org.bouncycastle.*` packages. If your project also pulls in + `bcprov-jdk15on` directly or transitively via another dependency, you will + end up with both jars on the classpath — build tools don't dedupe across + different artifact ids. Classloader ordering then decides which BC "wins" + at runtime, which can cause subtle crypto failures. Evict any remaining + `bcprov-jdk15on` from your dependency tree (Gradle `exclude`, Maven + ``), or add an explicit dependency on `bcprov-jdk18on` at the + version you want. + + `InvalidCipherException` gains a new public constructor + `InvalidCipherException(Throwable cause)` that preserves the underlying + cause. The existing `InvalidCipherException(InvalidCipherTextException)` + constructor is now `@Deprecated` because it leaks BouncyCastle types into + the SDK's public API; it will be removed in the next major release. Switch + any direct construction to the `Throwable` overload. + ## 4.2.0 ### Minor Changes diff --git a/lib/build.gradle b/lib/build.gradle index 1347b47..4b34960 100644 --- a/lib/build.gradle +++ b/lib/build.gradle @@ -6,7 +6,7 @@ plugins { } group 'com.evervault' -version '4.2.0' +version '4.3.0' repositories { mavenCentral() diff --git a/package.json b/package.json index 1e83bae..1efbc85 100644 --- a/package.json +++ b/package.json @@ -1,7 +1,7 @@ { "name": "evervault-java", "private": true, - "version": "4.2.0", + "version": "4.3.0", "scripts": { "version": "changeset version && PACKAGE_VERSION=$(node -p \"require('./package.json').version\") && sed -i \"s/version '.*'/version '$PACKAGE_VERSION'/g\" lib/build.gradle" },