[dependabot]

Bumps the maven-minor-updates group with 22 updates in the / directory:

Package	From	To
org.bouncycastle:bc-jdk18on-bom	1.85.2	1.86.2
org.apache.commons:commons-lang3	3.20.0	3.21.0
com.google.guava:guava	33.7.1-jre	33.7.2-jre
org.slf4j:slf4j-bom	2.0.19	2.0.20
com.google.protobuf:protobuf-java	4.36.1	4.36.2
com.google.errorprone:error_prone_annotations	2.50.0	2.51.0
org.eclipse.jetty.ee11:jetty-ee11-servlet	12.1.13	12.1.14
org.eclipse.jetty:jetty-security	12.1.13	12.1.14
org.eclipse.jetty:jetty-util	12.1.13	12.1.14
org.eclipse.jetty:jetty-server	12.1.13	12.1.14
org.eclipse.jetty:jetty-jmx	12.1.13	12.1.14
org.eclipse.jetty:jetty-security	12.1.13	12.1.14
org.eclipse.jetty:jetty-util	12.1.13	12.1.14
org.eclipse.jetty:jetty-server	12.1.13	12.1.14
org.eclipse.jetty:jetty-jmx	12.1.13	12.1.14
com.google.code.gson:gson	2.14.0	2.15.0
commons-codec:commons-codec	1.22.1	1.23.0
com.fasterxml.jackson.core:jackson-core	2.22.2	2.22.4
com.fasterxml.jackson.core:jackson-databind	2.22.2	2.22.4
org.apache.mina:mina-core	2.2.9	2.2.10
io.netty:netty-all	4.2.18.Final	4.2.19.Final
io.prometheus:prometheus-metrics-core	1.8.0	1.10.0
io.prometheus:prometheus-metrics-exporter-servlet-jakarta	1.8.0	1.10.0
io.prometheus:prometheus-metrics-exporter-servlet-jakarta	1.8.0	1.10.0
org.apache.zookeeper:zookeeper	3.9.6	3.9.7
org.mockito:mockito-core	5.23.0	5.24.0
org.apache.maven:apache-maven	3.9.16	3.10.0

Updates org.bouncycastle:bc-jdk18on-bom from 1.85.2 to 1.86.2

Changelog

Sourced from org.bouncycastle:bc-jdk18on-bom's changelog.

Bouncy Castle Crypto Package - Release Notes

1.0 Introduction

The Bouncy Castle Crypto package is a Java implementation of cryptographic algorithms. The package is organised so that it contains a light-weight API suitable for use in any environment (including the J2ME) with the additional infrastructure to conform the algorithms to the JCE framework.

2.0 Release History

2.1.1 Version

Release: 1.87
Date: 2026, TBD

2.1.2 Defects Fixed

• PrivateKeyFactory, and so the ML-DSA and ML-KEM KeyFactory services, did not use the tag of the RFC 9881 / RFC 9935 private key CHOICE to decide which arm it had been given and applied no length checks of its own: a [0]-tagged value was treated as a seed whatever its length, so an expanded key under the seed tag was accepted, and the SEQUENCE of the both form accepted an expanded key in its seed position and compared the expandedKey position against it, so a both value carrying the expanded key twice, or a seed twice, was accepted or failed with an unhelpful message. The seed arm must now be exactly 32 (ML-DSA) or 64 (ML-KEM) bytes, the expandedKey arm the parameter set's expanded key length, and the both form exactly two elements with a seed of the seed length and an expandedKey of the expanded length that it expands to, with a tag other than [0] rejected. The three forms of the pre-RFC drafts - the raw seed or raw expanded key as the privateKey OCTET STRING's content, and the seed in an untagged OCTET STRING - are still read, as before.
• X500Name.equals compared two names that are equal but not byte-identical - the same RDNs in another order, or in another string type - by searching the second name for each RDN of the first and canonicalising both values on every candidate comparison, so the comparison was quadratic in the number of RDNs, and CMSSignedData.getSignerInfos(), the CMSEnvelopedData, CMSAuthEnvelopedData and CMSEnvelopedDataParser constructors, TimeStampToken, the S/MIME classes built on them and X509CertificateHolderSelector.match() all compare names taken from the message before anything in it is verified: a 1.1 MB signed or enveloped message carrying two 40,000 RDN issuer names took about 90 seconds of CPU to parse. The signer and recipient stores also indexed their entries in a HashMap keyed on the signer or recipient id, whose hash code is easy to make collide, so a message with 16,000 signers or recipients chosen to collide took several seconds to index. AbstractX500NameStyle.areEqual now compares the RDNs positionally and otherwise sorts the canonical form of each RDN once and compares the two multisets, so a comparison is n log n in the number of RDNs, the two stores now scan their entries on lookup instead of indexing them, and the selector checks the serial number before the issuer name.
• The hash code of an ASN.1 object is a short fold over its content octets that a sender can make collide at will, and several tables built while a message is parsed were keyed on one: the extension table behind Extensions, so every certificate, CRL, OCSP and timestamp request parse, the deprecated X509Extensions, ExtendedKeyUsage, the CMS AttributeTable built from a SignerInfo's signed and unsigned attributes (the unsigned ones lying outside the signature), the EST CSRAttributesResponse index, and the Set of digest AlgorithmIdentifiers that the CMSSignedDataParser constructor and CMSSignedData.getDigestAlgorithmIDs() build from the SignedData digestAlgorithms field. With every key sharing one hash code each insert scanned all those before it, so a 6 MB certificate or message holding 65,000 such entries took about 35 seconds of CPU to parse and the parser's digest algorithm set about 140 seconds. Those tables are now ordered maps keyed on the OID's string form and the digest algorithm sets are ordered on the identifier's DER encoding, so each is n log n in the number of entries whatever their hash codes. AttributeTable.add() and remove() also no longer share a multi-valued entry's Vector with the table they were derived from.
• CMSSignedData digested the encapsulated or detached content once for every signer it verified, so a message carrying many SignerInfos over a large content cost their product in digesting before any signature was checked, where CMSSignedDataParser digests once per algorithm named in the digestAlgorithms field. The signers of a CMSSignedData now share the content digests computed under each digest algorithm identifier, so signers using the same algorithm digest the content once. The new org.bouncycastle.cms.max_digest_algorithms property bounds the number of distinct digest algorithms either class will compute over one message's content, each algorithm past the limit raising a CMSException; it is unlimited unless set.
• The verify side of the ML-DSA-CALCULATE-MU signature service, and MLDSASigner.verifyMu beneath it, compared the supplied mu with a value derived from the key's tr and the context alone, never absorbing the message passed to update(), so a correct mu was accepted only for an empty message and rejected for every other, while the sign side of the same service computed mu correctly. The comparison also finalised the engine's shared digest, so an ordinary verifySignature on the same MLDSASigner afterwards failed for a valid signature, and a mu of the wrong length escaped Signature.verify() as an unchecked DataLengthException. verifyMu now derives the expected mu from the message digest exactly as generateMu does and compares in constant time, the signer stays usable afterwards, the service answers a wrong-length mu with a SignatureException, and the contract - the verify side accepts exactly the mu the sign side returns for the same key, context and data - is now in the javadoc of both.
• The SM2 key pair generator of the BC provider, KeyPairGenerator.getInstance("SM2", "BC"), was built on the generic EC key pair generator rather than the lightweight SM2KeyPairGenerator the 1.73 release notes described, so it could draw a private key of n - 1, which Section 6.1 of GB/T 32918.1 excludes and which the SM2 signer rejects. It now uses SM2KeyPairGenerator and draws from [1, n - 2].
• ESTResponse added each header line of an EST server's response to its header table by copying that header's value array, so a response repeating one header many times was quadratic to parse - about 7 seconds of CPU per megabyte of header lines - and a read limit set through JsseESTServiceBuilder.withReadLimit() only applied once the header block had been read. The values of each header are now collected once, and the header block counts against the read limit of the source.
• The C509 encoding of an RFC 6955 proof-of-possession value (the sa-ecdhPop signature algorithms, values 14 to 16 of the C509 Signature Algorithms Registry) copied the DER DhSigStatic into the signature value byte string, where Section 4.2 of draft-ietf-cose-cbor-encoded-cert-21 defines the value as the bare hashValue when the DhSigStatic names no issuer and serial number and as the [issuer, certificateSerialNumber, hashValue] array when it does. The converter now produces both forms from the DER and reconstructs the DER from either; previously the array form was rejected outright and the byte-string form reconstructed a signature value four bytes short of the DER it came from, so a type 3 request carrying one could not verify. The privateKeyPossessionStatement certification request attribute (RFC 9883, Section 4.3.3 of the draft) was carried in the generic ~oid form on conversion and refused on reconstruction; it is now converted to and from its int-coded [issuer, certificateSerialNumber, cert] form, with an embedded signature certificate re-encoded as a type 3 C509 certificate. The certificate, certification request and template vectors of draft-ietf-cose-c509-test-vectors-02 now drive the util and pkix test suites.
• The DANE SMIMEA support in org.bouncycastle.cert.dane had three defects. JndiDANEFetcherFactory, when asked for every entry under a bare domain name, removed the first and last characters of the owner name the JNDI DNS provider reports for each listed record, assuming a quoted name; the provider returns the name unquoted with a trailing root dot, so the first hex digit of the hash label was lost and the lookup that followed could never find the record. It now removes only the root dot. DANEEntryStore kept one entry per owner name, so an address with more than one SMIMEA record (a signing and an encryption certificate, say) only ever showed its last; every entry is now kept. DANEEntrySelectorFactory split an address at its first '@', mis-handling a quoted local-part containing one, and threw StringIndexOutOfBoundsException rather than DANEException for an address with none; it now splits at the last '@', removes enclosing quotes and backslash quoting from the local-part before hashing as RFC 8162 sec. 3 describes, and rejects an address with no '@'. The DANEEntry(String, byte[]) constructor also now rejects, with an IOException, a record whose flags do not describe a full certificate entry rather than parsing whatever follows the flags as a certificate.
• TimeStampToken accepted a token whose signing-time signed attribute disagreed with the genTime in its TSTInfo. Both are the TSA's statement of when the token was produced, and the disagreement is what distinguishes an RFC 3161 token from a signature a TSA has put over a supplied TSTInfo through another service using the same key, such as a legacy countersignature endpoint, which some TSAs still offer. The constructor now rejects a token whose signing-time, when present, is further from genTime than the token's accuracy plus one minute; the check can be switched off with the org.bouncycastle.tsp.allow_inconsistent_signing_time property. TimeStampTokenGenerator now sets a signing-time attribute from the genTime it is given rather than the clock, so its tokens are consistent whatever genTime is passed.
• TimeStampToken.validate() accepted a token whose message imprint was calculated with MD5, for which collisions can be computed, and TSPAlgorithms.ALLOWED, the set the request side is typically checked against, included MD5. MD5 has been removed from TSPAlgorithms.ALLOWED, and validate() now rejects a token whose imprint algorithm is not in it (failure code badAlg). The new TSPAlgorithms.LEGACY is ALLOWED plus MD5; validate(SignerInformationVerifier, Set) takes the set of acceptable imprint algorithms, and the org.bouncycastle.tsp.allowed_imprint_algorithms property, a comma separated list of digest names or OIDs, replaces ALLOWED as the default for validate(SignerInformationVerifier). TSPAlgorithms.ALLOWED and LEGACY are now unmodifiable.
• CRL-based revocation checking (the PKIX CertPathValidator and the pkix X509RevocationChecker) tracked a CRL entry's reasonCode in the same field as its own status markers and did not range-check it, so a CRL entry whose reasonCode was outside the RFC 5280 sec. 5.3.1 set was mishandled: 11 left the certificate unrevoked, other out-of-range values threw an unchecked exception out of validation. The revocation date and the reason code are now kept separately; an undefined reasonCode is processed as unspecified and reported as "(unknown code: N)".
• OERDefinition.enumItem(label, value) discarded the explicit enumerand value: Builder.enumValue() set it on the builder it had just copied and returned the copy without it, so every item was numbered by its position in the definition instead. The value is now kept, and the items without one are numbered as X.680 sec. 20.3 and 20.6 specify: a root item takes the successive integers from 0, skipping any explicit root number, and an extension item takes the smallest value not defined in the root and greater than every preceding extension item (the old loop restarted its count after an explicit number, so an explicit 0 followed by an unnumbered item was a duplicate). The three ETSI TS 102 941 response-code definitions that use explicit values give "ok" the value 0 at position 0, so their encodings are unchanged.
• OERInputStream read the two length-prefixed INTEGER forms and BIT STRING with Streams.readFully and did not check its best-effort return, so a stream that ended inside the value decoded the zero-padded buffer as a value rather than failing. Every length-driven read in the decoder now goes through Streams.readLenBytesFully, which fails with EOFException at the real end of input and, for a long length, does not allocate the full array until the stream has delivered a fair part of it - so a hostile length that is within the decoder's allocation cap, or a cap a caller has raised, cannot drive a large allocation from a short input.
• The OER codec gave a signed INTEGER whose upper bound is exactly the maximum of a fixed-size word the next word up: X.696 sec. 10.4 a)-d) make both bounds inclusive, but the upper-bound comparison was strict, so INTEGER (-128..127) was a two-octet word rather than one, and likewise at the 16-, 32- and 64-bit boundaries. The two signed ranges shipped with the library, NinetyDegreeInt and OneEightyDegreeInt, lie inside the four-octet word and are unaffected.
• The ETSI TS 102 941 response code wrappers AuthorizationResponseCode, AuthorizationValidationResponseCode and EnrolmentResponseCode checked their range on BigInteger.intValue(), which truncates, so a value past the int range whose low 32 bits were in range was accepted - 2^32 as "ok". The check now rejects a negative value or one over 31 bits before consulting intValue().
• OERInputStream accepted an empty group of octets as the value zero in four places where X.696 requires at least one: a variable-size INTEGER with a length determinant of 0 (sec. 3.7.11 and 3.7.12 define the number forms as one or more octets), an ENUMERATED long form with 0 subsequent octets (sec. 11.4 says 1 to 127), a length determinant long form with 0 subsequent octets (sec. 8.6.5, likewise) and a sequence-of quantity of 0 octets (sec. 17.2). Each now fails with an IOException; the one-octet encodings of zero decode as before.
• OEROutputStream could not encode a CHOICE whose chosen alternative has a tag number of 63 or more. X.696 sec. 8.7.2.2 keeps a tag number below 63 in the first octet and sec. 8.7.2.3 continues one of 63 or more in 7-bit groups, most significant first, with bit 8 as the continuation flag; the encoder used the single octet up to and including 63, so 63 went out as the continuation escape with nothing after it, and BitBuilder.write7BitBytes took its groups from bit 31 downward rather than from the low end, so 63 encoded as 83 78, which decodes as 504. Both forms of write7BitBytes now write the fewest 7-bit groups of the value, and the boundary is at 63. No CHOICE in the shipped ITS definitions has that many alternatives.
• OEROutputStream rejected a required SEQUENCE component as absent whenever it arrived wrapped in an OEROptional, the form the ITS classes' toASN1Primitive methods produce for present values, rather than only when the wrapper is the undefined ABSENT. A defined wrapper at a required position is now unwrapped and written like the bare value.
• OERInputStream, for an absent optional SEQUENCE component selected through a switch, tested the selected alternative for a default value but then took the default from the switch itself, which has none, so the alternative's default was added as null and the decode failed with NullPointerException. The default now comes from the selected alternative. No definition shipped with the library has a switched component with a default.
• OERInputStream read a SEQUENCE OF count through BigInteger.intValue(), which keeps only the low 32 bits, so a count of 2^32 + 3 decoded as 3 elements and the rest of the input was left in place for the next field. A count that does not fit in 31 bits is now rejected as out of range, and the fixed sizes taken from a definition go through BigIntegers.intValueExact() rather than silently truncating.
• OERInputStream rejected a valid SEQUENCE OF as "out of range" on any stream whose available() reported fewer bytes than the element count: available() is an estimate of what can be read without blocking, 0 from the base InputStream and from wrappers such as CipherInputStream, and the decoder had been using it as a bound on the count. The count is now bounded by the decoder's allocation ceiling (maxByteAllocation, 1 MiB by default) instead, and a count within it over a short input fails at the first element that is not there.
• OERInputStream could not decode a variable-size BIT STRING. X.696 sec. 13.3 encodes one as a length determinant covering an initial octet, which gives the number of unused bits in the final octet, and the octets of the value, which is what OEROutputStream writes; the decoder read the determinant as a bit count, divided it by 8 and never read the initial octet, so it took no data at all for a two-octet value, and a stray third branch keyed on a negative size bound threw NullPointerException for an unbounded schema. The decoder now has the two forms of clause 13: a fixed size reads the whole octets the size occupies and derives the unused bits from it (a 12-bit string is two octets with four unused bits, where it was one octet), and any other size reads the determinant, the initial octet (rejected over 7, or non-zero for an empty value, 13.3.4) and the data, carrying the unused-bit count into the DERBitString. OERDefinition gains bitString() and bitString(lower, upper) alongside bitString(size). The single BIT STRING in the shipped ITS definitions is a fixed 8 bits and decodes as before.
• OEROutputStream wrote a negative INTEGER value under a type whose lower bound is zero or more through the unsigned encodings, so it went out as a different, positive value: -1 under INTEGER (0..255) as FF, the encoding of 255, and under INTEGER (0..MAX) as 01 FF. A negative value is now rejected with IllegalArgumentException on both unsigned paths.
• OERInputStream.uint64() read its eight octets as a signed number, so a value with the top bit set came back negative; the other uintN readers were unsigned. It now reads unsigned.
• The OER codec treated an INTEGER with a positive lower bound as signed. X.696 sec. 10.2 a) gives the unsigned encodings to an integer whose lower bound is zero or positive; OERInputStream and OEROutputStream tested for a lower bound of exactly zero, so INTEGER (1..255) went out as a two-octet signed word rather than one unsigned octet and INTEGER (1..MAX) as a variable-size signed number, where 128 is 00 80 rather than 80. No OER definition shipped with the library puts a positive lower bound on an INTEGER.
• The OER codec encoded and decoded a negative ENUMERATED value wrongly. X.696 sec. 11.4 reserves the one-octet short form for the values 0 to 127 and puts every other value, negative ones included, in the long form as a two's-complement signed integer; OEROutputStream chose the long form only for values above 127, so a negative value went out in the short form masked to seven bits (-1 as 7F, the encoding of 127), and OERInputStream read a long-form value as unsigned (81 FF, the encoding of -1, as 255). Both now follow sec. 11.4. No OER definition shipped with the library declares a negative enumerand.
• ASN1Enumerated rejected negative values, although an ENUMERATED is an integer (X.680 sec. 20) and may be negative: the int and BigInteger constructors threw "enumerated must be non-negative", the byte array constructor rejected a leading sign bit, and a parsed ENUMERATED with a negative value failed to decode. The checks are removed, ASN1Enumerated gains isNegative() and longValueExact() alongside the existing intValueExact(), and a zero-length ENUMERATED is now reported as "malformed enumerated", as a zero-length INTEGER is reported as "malformed integer", rather than "ENUMERATED has zero length". ASN1Enumerated.valueOf(int) and valueOf(long) return shared instances for the values 0 to 15, as ASN1Integer.valueOf() does, and a parsed single-byte ENUMERATED in that range is returned as the shared instance.
• A PBEKey stored in a BCFKS KeyStore was not reported as a key entry: isKeyEntry() returned false for it, so KeyStore.getEntry() returned null rather than a SecretKeyEntry, although getKey() recovered it. The PBE key entry type added for github #2164 was missing from engineIsKeyEntry, and is now included.
• The CMS content-type decoders SignedData, EnvelopedData, AuthenticatedData, AuthEnvelopedData and EncryptedData read their mandatory fields by index or enumeration with no lower-bound size check, so a ContentInfo whose inner content was an empty or too-short SEQUENCE - malformed but DER-parseable - left the decode as an unchecked NoSuchElementException or ArrayIndexOutOfBoundsException rather than the CMSException the CMSSignedData, CMSEnvelopedData, CMSAuthenticatedData and CMSAuthEnvelopedData constructors declare (the IllegalArgumentException CMSEncryptedData documents). Each now rejects a short sequence with IllegalArgumentException before reading, as the sibling content types CompressedData and DigestedData already did, so the wrappers surface it as their declared exception; the case that claims an OPTIONAL field and then truncates the mandatory ones after it is covered too. The streaming parsers CMSSignedDataParser, CMSEnvelopedDataParser, CMSAuthenticatedDataParser, CMSAuthEnvelopedDataParser and CMSCompressedDataParser had the same gap and more: an absent or truncated inner SEQUENCE, a mandatory field of the wrong type, or absent encapsulated or encrypted content escaped as NullPointerException, ClassCastException, IllegalArgumentException or IllegalStateException. The asn1.cms stream parsers now report a missing mandatory field as an IOException, and the CMS parsers report malformed content as CMSException ("Malformed content." / "Missing content.") or the IOException they declare.
• A KeyAgreement asked for its shared secret before doPhase returned data rather than refusing. javax.crypto.KeyAgreement specifies IllegalStateException for that state, but nothing in the provider tracked it, so each SPI handed back whatever its result field held: for Diffie-Hellman that was the private value itself - engineInit seeded result with x, so generateSecret() returned the private exponent padded to the prime's length and generateSecret("AES") an all-zero key taken from that padding - while ECDH returned null and its named-algorithm overload raised NullPointerException. BaseAgreementSpi now records whether a doPhase has completed the agreement since the last init and refuses the request with an IllegalStateException naming the algorithm, so every family in the provider - DH, ECDH and ECMQV, the SM2 exchange, both ECGOST families, XDH, SM9 and NewHope - answers the same way, and the DH SPI no longer holds the private value in that field at all.
• Mac.getInstance and KeyGenerator.getInstance by the HMAC SHA-512/224 and SHA-512/256 object identifiers (1.2.840.113549.2.12 and .13) failed, although the same algorithms resolved by name and the matching SecretKeyFactory aliases were registered: the SHA512 mappings called addHMACAlgorithm for the two truncated variants without the addHMACAlias that registers their OIDs against Mac and KeyGenerator. Both are now aliased, as every other HMAC in that class already was.
• A KTSParameterSpec naming an HKDF key-derivation function with a parameters field - a form the provider does not service - was accepted at Cipher init and then failed out of wrap or unwrap with an unchecked IllegalStateException neither method declares. The KTS key-wrapping Ciphers (ML-KEM, Classic McEliece, FrodoKEM, the composite KEM and RSA-KEM) now validate the spec's KDF when they take it, reporting an unserviceable one as the InvalidAlgorithmParameterException engineInit declares, which is what the javax.crypto.KEM services already did through KdfUtil.resolveKemSpec.

... (truncated)

Commits

• See full diff in compare view

Updates org.apache.commons:commons-lang3 from 3.20.0 to 3.21.0

Updates com.google.guava:guava from 33.7.1-jre to 33.7.2-jre

Release notes

Sourced from com.google.guava:guava's releases.

33.7.2

Maven

<dependency>
  <groupId>com.google.guava</groupId>
  <artifactId>guava</artifactId>
  <version>33.7.2-jre</version>
  <!-- or, for Android: -->
  <version>33.7.2-android</version>
</dependency>

Jar files

• 33.7.2-jre.jar
• 33.7.2-android.jar

Guava requires one runtime dependency, which you can download here:

• failureaccess-1.0.3.jar

Javadoc

• 33.7.2-jre
• 33.7.2-android

JDiff

• 33.7.2-jre vs. 33.7.1-jre
• 33.7.2-android vs. 33.7.1-android
• 33.7.2-android vs. 33.7.2-jre

Changelog

• collect: Changed MapMaker, CompactHashMap, and CompactHashSet deserialization to avoid eagerly allocating as much memory as a serialization payload requests (CVE-2026-102554). (a0d0c36432)

Commits

• See full diff in compare view

Updates org.slf4j:slf4j-bom from 2.0.19 to 2.0.20

Release notes

Sourced from org.slf4j:slf4j-bom's releases.

SLF4J 2.0.20

2026-09-22 - Release of SLF4J 2.0.20

• Marker instances are slated to become immutable in future releases. As such, methods in the Marker interface adding/removing children are now marked as deprecated.

• A bit-wise identical binary of this version can be reproduced by building from source code at commit 58d80a4fe8f2e811707fcfba4d292b5d62fc2fe9 associated with the tag v_2.0.20. Release built using Java "21" 2023-10-17 LTS build 21.0.1.+12-LTS-29 under Linux Debian 11.6.

Full Changelog: qos-ch/slf4j@v_2.0.19...v_2.0.20

Commits

• 58d80a4 prepare release 2.0.20
• ef47ab9 deprecate methods for adding/remocing children to markers
• 6b6c63e fix failing test on Windows
• 233d4d1 renamed LoggerTestSuite.java as SimpleLoggerAcceptanceTest
• bf3a7b9 start work on 2.0.20-SNAPSHOT
• See full diff in compare view

Updates com.google.protobuf:protobuf-java from 4.36.1 to 4.36.2

Commits

• See full diff in compare view

Updates com.google.errorprone:error_prone_annotations from 2.50.0 to 2.51.0

Release notes

Sourced from com.google.errorprone:error_prone_annotations's releases.

Error Prone 2.51.0

New checks:

• HashCodeInObjectsHash: Detect redundant hashCode() or Objects.hash() calls inside Objects.hash(...), and simplify single-argument Objects.hash(x) calls to Objects.hashCode(x).
• LoopToTestParameter: Suggest migrating loops in unit tests to TestParameterInjector.
• MissingJavadoc: Flag public types that are missing Javadoc comments (disabled by default).
• PreferCharsetOverload: Prefer calling method and constructor overloads that accept a Charset over those that accept a String encoding name.
• PreferPreconditions: Suggest using Guava's Preconditions instead of explicit if-throw statements for parameter validation (disabled by default).
• RequireNonNullRefactoring: Refactor explicit if (x == null) { throw new NullPointerException(...); } checks to Objects.requireNonNull (disabled by default).
• SimplifyTestParameter: Remove redundant explicit value lists on @TestParameter annotations for boolean and Enum types when all values are specified (disabled by default).
• TraditionalJavadocToMarkdown: Convert traditional /** ... */ Javadoc comments into /// Markdown Javadoc comments (disabled by default).
• ValueClassIdentity: Flag reliance on identity semantics (such as synchronization, WeakReference, IdentityHashMap, or System.identityHashCode) of value-based classes (disabled by default).

Other changes:

• CompareToZero: Upgraded from warning to error, and expanded to flag non-relational operations, unary negation, and switch statements/expressions on compareTo and compare results without Integer.signum.
• IfChainToSwitch: Enabled by default as a warning.
• UndefinedEquals: Merged ArrayAsKeyOfSetOrMap and CollectionUndefinedEquality into UndefinedEquals (retaining their names as altNames), and generalized detection of types without well-defined equals or hashCode across direct equality, collection containment, and hash-based containers.
• EqualsIncompatibleType / TruthIncompatibleType: Flag equality comparisons between distinct record types (#6107).
• ReferenceEquality: Allow == comparisons on private classes whose type hierarchy does not override Object.equals (#5865), private static final sentinel fields, Thread (#5900), and com.sun.source.tree.Tree.
• PatternMatchingInstanceof: Support while and for loops, parenthesized expressions (#5843), and replacing additional redundant casts when the instanceof already introduces a pattern variable.
• DistinctVarargsChecker: Expanded to check Objects.hash, CompletableFuture.allOf/anyOf, EnumSet.of, Sets.union/intersection/difference, Stream.concat, Math.min/max, and additional JDK, Guava, Protobuf, Truth, and Mockito methods.
• MustBeClosedChecker: Require java.lang.foreign.Arena.ofConfined and Arena.ofShared to be closed.
• ImpossibleNullComparison: Flag null checks on the return value of Class.forName.
• RestrictedApi / RestrictedInheritance: Added an allowedPaths attribute to allow calls or inheritance from matching file paths without a regular expression.
• InlineMeInliner: Support substituting type arguments at call sites when inlining generic @InlineMe methods.
• WellKnownKeep: Recognize Apache Beam DoFn annotations and retain open-source library annotations (Gson, Mockito, Guice, Objectify, TestParameterInjector, AutoFactory).
• Per-check timing collection is now disabled by default, reducing Error Prone compile-time overhead by ~3–5%; pass -XepPrintTimings to print a timing report after compilation or -XepRecordTimings to record timings programmatically (#6079).
• CompilationTestHelper now reports all lines with mismatched diagnostic expectations in a single test run rather than failing on the first mismatch (#6116).
• Replaced the RE2/J dependency with SafeRE.

Closed issues: #4914, #5182, #5843, #5857, #5865, #5878, #5900, #6029, #6079, #6107, #6116, #6133

Commits

• 3e9c316 Release Error Prone 2.51.0
• 4f83ec3 Add Maven 3.9.16 setup to release workflow
• 47eb5be Exempt Apache Beam DoFn method annotations in WellKnownKeep
• 7e2efea [IfChainToSwitch] Lower the minimum if-chain length from 5 to 4
• 0a97086 [IfChainToSwitch] address issue where deleting trailing code can cause compil...
• f61d405 [Reachability] drop skipLabel from visitContinue
• 854665b Collapse duplicated package prefixes in _javac source jar paths.
• 3588433 Introduce -XepOpt:Nullness:LikelyPublicApiOnly=true for annotating only API...
• b8a8390 Merge CollectionUndefinedEquality and ArrayAsKeyOfSetOrMap into UndefinedEquals.
• 59f98c3 Allow == comparisons on Tree instances.
• Additional commits viewable in compare view

Updates org.eclipse.jetty.ee11:jetty-ee11-servlet from 12.1.13 to 12.1.14

Updates org.eclipse.jetty:jetty-security from 12.1.13 to 12.1.14

Updates org.eclipse.jetty:jetty-util from 12.1.13 to 12.1.14

Updates org.eclipse.jetty:jetty-server from 12.1.13 to 12.1.14

Updates org.eclipse.jetty:jetty-jmx from 12.1.13 to 12.1.14

Updates org.eclipse.jetty:jetty-security from 12.1.13 to 12.1.14

Updates org.eclipse.jetty:jetty-util from 12.1.13 to 12.1.14

Updates org.eclipse.jetty:jetty-server from 12.1.13 to 12.1.14

Updates org.eclipse.jetty:jetty-jmx from 12.1.13 to 12.1.14

Updates com.google.code.gson:gson from 2.14.0 to 2.15.0

Release notes

Sourced from com.google.code.gson:gson's releases.

Gson 2.15.0

What's Changed

These are some of the more important changes

API addition:

• Add JsonReader.getCharacterOffset to track stream position by @​barakhub in google/gson#3102

Behaviour changes and bugfixes:

• Use LinkedHashMap as the default Map. by @​eamonnmcmanus in google/gson#3057
• Make LazilyParsedNumber implement Comparable. by @​eamonnmcmanus in google/gson#3076
• Only deserialize InetAddress from numeric IP addresses. by @​eamonnmcmanus in google/gson#3075
• Correct logic for BOM detection. by @​eamonnmcmanus in google/gson#3137
• fix: Include location info in NumberFormatException from JsonReader by @​daguimu in google/gson#3000
• Fix: peekNumber rejects some numerals like 2^64 + "0" by @​ogolberg in google/gson#3034
• Fix URI type adapter to preserve identity for non-ASCII URIs by @​anishesg in google/gson#3067
• Fix JsonPrimitive.hashCode to honor the equals/hashCode contract (#992) by @​earfman in google/gson#3059
• Reject non-ASCII digits in JsonTreeReader.nextInt/nextLong by @​dong0713 in google/gson#3063
• Include location in NumberFormatException thrown by JsonTreeReader by @​dong0713 in google/gson#3062
• Update JSON path after promoteNameToValue by @​tanvir-ux in google/gson#3098
• fix: reject unpaired surrogates in strict JSON by @​rksharma-owg in google/gson#3116
• Skip accessibility check in BoundField once it is known to have passed by @​nileshpatil6 in google/gson#3086
• Avoid quadratic removeIf in JsonArray list views by @​ishu7w in google/gson#3115
• Use the runtime type for a wildcard element type by @​HuzaifaChaudary in google/gson#3112

New Contributors

• @​daguimu made their first contribution in google/gson#3000
• @​anish-anantharaman made their first contribution in google/gson#3025
• @​adilburaksen made their first contribution in google/gson#3027
• @​ogolberg made their first contribution in google/gson#3034
• @​vasiliy-mikhailov made their first contribution in google/gson#3038
• @​mayokunyusuf made their first contribution in google/gson#3061
• @​arpitagarwal1301 made their first contribution in google/gson#3065
• @​anishesg made their first contribution in google/gson#3067
• @​earfman made their first contribution in google/gson#3059
• @​dong0713 made their first contribution in google/gson#3063
• @​nafisa1602 made their first contribution in google/gson#3049
• @​barakhub made their first contribution in google/gson#3102
• @​tanvir-ux made their first contribution in google/gson#3098
• @​rksharma-owg made their first contribution in google/gson#3116
• @​nileshpatil6 made their first contribution in google/gson#3086
• @​lllincoln made their first contribution in google/gson#3046
• @​Phhofm made their first contribution in google/gson#1532
• @​ishu7w made their first contribution in google/gson#3115
• @​HuzaifaChaudary made their first contribution in google/gson#3112

Full Changelog: google/gson@gson-parent-2.14.0...gson-parent-2.15.0

Commits

• fcd4169 [maven-release-plugin] prepare release gson-parent-2.15.0
• 828cbe0 Update protobuf-maven-plugin dependency. (#3153)
• 66dd98a Disable Spotless plugin before Java 21. (#3152)
• 094f500 Fix typo in comment (#3148)
• 881d2b5 Consistently use "Gson" instead of "GSON" as project name (#3150)
• e2292f9 Address a few static analysis findings. (#3141)
• 67427c4 Bump the github-actions group across 1 directory with 5 updates (#3133)
• 845664b Correct logic for BOM detection. (#3137)
• 216c41b Bump com.fasterxml.jackson.core:jackson-databind (#3136)
• 854c825 Simplify key removal in LegacyProtoTypeAdapterFactoryTest (#3124)
• Additional commits viewable in compare view

Updates commons-codec:commons-codec from 1.22.1 to 1.23.0

Changelog

Sourced from commons-codec:commons-codec's changelog.

Apache Commons Codec 1.23.0 Release Notes

The Apache Commons Codec team is pleased to announce the release of Apache Commons Codec 1.23.0.

The Apache Commons Codec component contains encoders and decoders for formats such as Base16, Base32, Base64, digest, and Hexadecimal. In addition to these widely used encoders and decoders, the codec package also maintains a collection of phonetic encoding utilities.

This is a feature and maintenance release. Java 8 or later is required.

New features

•         Add and use PhoneticEngine.Builder and deprecate old constructors. Thanks to Gary Gregory.
  

•         Add BeiderMorseEncoder.Builder and deprecate old constructor. Thanks to Gary Gregory.
  

•         Add PhoneticEngine.Builder.setMaxInputLength(int). Thanks to Yu Bao, Gary Gregory.
  

•         Add Base45 support. Thanks to Gary Gregory.
  

•         Add URLCodec.decodeUrl(BitSet, byte[]) to decode with a custom safe set. Thanks to Gary Gregory.
  

Fixed Bugs

•         GitIdentifiers orders tree entries by unsigned UTF-8 bytes, as Git does, instead of UTF-16 code units. Thanks to Jeff Lenamon.
  

•         Optimize PhoneticEngine.encode(String, LanguageSet) for speed. Thanks to Yu Bao, Gary Gregory.
  

•         RFC1522Codec.decodeText(String) now throws a DecoderException instead of a StringIndexOutOfBoundsException when a separator is missing. Thanks to Yu Bao, Gary Gregory.
  

•         Optimize Base58.convertFromBase58(byte[], Context) for speed and temporary object allocation. Thanks to Yu Bao, Gary Gregory.
  

•         Allocate a single MessageDigest and use it in Sha2Crypt.sha2Crypt(byte[], String, String, int, String). Thanks to Yu Bao, Gary Gregory.
  

•         Javadoc improvements. Thanks to Gary Gregory.
  

•         Throw IOException instead of IllegalArgumentException in BaseNCodecOutputStream and BaseNCodecOutputStream IO methods. Thanks to Gary Gregory.
  

•         Throw DecoderException instead of IllegalArgumentException in RFC1522Codec.decodeText(String). Thanks to Gary Gregory.
  

•         Fix Blake3 KDF example and clarify finalization semantics. Thanks to Gary Gregory.
  

•         Base32 and Base64 STRICT decoding now require the encoder's canonical alphabet, padding, and line separators, and validate streams through EOF. Use LENIENT to retain permissive decoding. Thanks to Gary Gregory.
  

•         Limit Base58 decoding to 8192 encoded bytes by default, checking cumulative stream input before buffering. Use Base58.Builder.setMaxDecodeLength(int) for larger trusted input. Encoding defaults to a configurable 8192-byte binary input limit through Base58.Builder.setMaxEncodeLength(int). Thanks to Gary Gregory.
  

•         Grow Base58 accumulation buffers geometrically within the configured input limits and validate actual accumulated length. Thanks to Gary Gregory.
  

•         Implement Base58 encoded-length calculation and explicitly reject unsupported line chunking. Thanks to Gary Gregory.
  

•         Close the underlying BaseNCodecOutputStream output even when final conversion or flushing fails, preserving suppressed close exceptions. Thanks to Gary Gregory.
  

•         Reject invalid GitIdentifiers tree entry names and file/directory name conflicts to prevent ambiguous tree serialization and colliding identifiers. Thanks to Gary Gregory.
  

•         Hex decoding now accepts only ASCII hexadecimal characters (0-9, A-F, a-f). Previously accepted non-ASCII Unicode digits and fullwidth letters now cause DecoderException, including when supplied as UTF-8 bytes or ByteBuffers. Thanks to Gary Gregory.
  

•         Restrict Hex decoding to ASCII hexadecimal characters. Thanks to Gary Gregory.
  

•         Validate BinaryCodec input while preserving leading-bit truncation. Thanks to Gary Gregory.
  

•         Reject oversized Beider-Morse input before language guessing. Thanks to Gary Gregory.
  

•         QuotedPrintableCodec decoding now preserves hard CRLF line breaks and, leniently, unpaired CR and LF bytes instead of discarding them. Soft line breaks require the full =CRLF sequence; previously accepted =CR without LF now throws DecoderException. This affects both constructor modes and QCodec, which shares the decoder. Thanks to Gary Gregory.
  

•         Bound Sha2Crypt rounds from caller-supplied salts. Thanks to Gary Gregory.
  

•         Bound Sha2Crypt password length to prevent quadratic CPU DoS. Thanks to Gary Gregory.
  

•         Make the @param names in BaseNCodec match the parameters they document ([#444](https://github.com/apache/commons-codec/issues/444)). Thanks to geonseok, Gary Gregory.
  

• CODEC-345: Restore URLCodec.encodeUrl(BitSet, byte[]) support for custom safe sets containing percent and plus, and document the decoding limitations. Thanks to Ganesh Gautam, Gary Gregory.
• CODEC-245: Reject malformed Sha2Crypt salt syntax (#445). Thanks to Efe, Gary Gregory.

... (truncated)

Commits

• 1147e78 Add github.autolink_jira
• 129a289 Prepare for the release candidate 1.23.0 RC1
• d7bff67 Prepare for the release candidate
• 89d6498 Update GH CI from Java 26 to 27
• 5444a15 [test] Bump org.apache.commons:commons-lang3 from 3.20.0 to 3.21.0
• 6685826 Bump org.apache.commons:commons-lang3 from 3.20.0 to 3.21.0 (#446)
• 7221073 Parameterize some unit tests
• cb9c04d Parameterize some unit tests
• 6837802 [CODEC-245] Reject malformed Sha2Crypt salt syntax
• 3e05f66 [CODEC-245] Reject malformed Sha2Crypt salt syntax (#445)
• Additional commits viewable in compare view

Updates com.fasterxml.jackson.core:jackson-core from 2.22.2 to 2.22.4

Commits

• 822b0a0 [maven-release-plugin] prepare release jackson-core-2.22.4
• 8d6ea81 Prep for 2.22.4 release
• b809db3 Merge branch '2.21' into 2.22
• 498587a Post-release dep version bump
• ad24c5b [maven-release-plugin] prepare for next development iteration
• 8bd7d2f [maven-release-plugin] prepare release jackson-core-2.21.8
• bffd3aa Prep for 2.21.8 release
• 6ac4640 Merge branch '2.21' into 2.22
• 3a5647b Merge branch '2.20' into 2.21
• a18f841 Merge branch '2.19' into 2.20
• Additional commits viewable in compare view

Updates com.fasterxml.jackson.core:jackson-databind from 2.22.2 to 2.22.4

Commits

• a56a810 [maven-release-plugin] prepare release jackson-databind-2.22.4
• c172c5d Prep for 2.22.4 release
• 1e761c0 Merge branch '2.21' into 2.22
• fe3780f Post-release dep version bump
• a0e1fad [maven-release-plugin] prepare for next development iteration
• c92512e [maven-release-plugin] prepare release jackson-databind-2.21.8