Adding VoyageAI integration by fzowl · Pull Request #345 · microsoft/semantic-kernel-java

fzowl · 2025-11-17T09:57:21Z

Motivation and Context

VoyageAI provides state-of-the-art embeddings models

Description

Adding VoyageAI integration
MicrosoftDocs/semantic-kernel-docs#327

Contribution Checklist

The code builds clean without any errors or warnings
The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
All unit tests pass, and I have added new tests where possible
I didn't break anyone 😄

Martijn Verburg (karianna) · 2025-12-14T00:09:09Z

fzowl - test / build failures if you can PTAL?

Martijn Verburg (karianna) · 2025-12-24T05:05:31Z

fzowl - seeing errors such as:

Error: Medium: Exception thrown in class com.microsoft.semantickernel.services.reranking.RerankResult at new com.microsoft.semantickernel.services.reranking.RerankResult(int, String, double) will leave the constructor. The object under construction remains partially initialized and may be vulnerable to Finalizer attacks. [com.microsoft.semantickernel.services.reranking.RerankResult, com.microsoft.semantickernel.services.reranking.RerankResult] At RerankResult.java:[line 21]At RerankResult.java:[line 21] CT_CONSTRUCTOR_THROW

…CONSTRUCTOR_THROW SpotBugs (bug-check profile) flagged CT_CONSTRUCTOR_THROW on classes whose constructors throw validation exceptions while being non-final, which the Java CI build treats as an error and fails merge-gatekeeper. Marking these value/service classes final removes the finalizer-attack vector SpotBugs warns about while preserving the existing constructor validation.

After merging upstream/main, the repository version advanced to 1.5.1-SNAPSHOT while the VoyageAI module still pinned the old 1.4.4-RC3-SNAPSHOT parent, which made the semantickernel-bom import unresolvable and broke the reactor build.

The VoyageAIModels request/response DTOs expose their mutable list and array fields directly through getters, setters and one constructor, which SpotBugs (bug-check profile) flags as EI_EXPOSE_REP/EI_EXPOSE_REP2. These are plain Jackson-mapped data holders, so annotate the individual accessors with @SuppressFBWarnings, matching the pattern already used by the other aiservices DTOs (e.g. HuggingFace, OpenAI, Google).

fzowl · 2026-08-16T17:45:02Z

Thanks Martijn Verburg (@karianna) — pushed a fix. The bug-check profile was failing on SpotBugs in two stages:

CT_CONSTRUCTOR_THROW: RerankResult, the four VoyageAI service classes, and VoyageAIClient throw validation exceptions from their constructors. Marked those classes final so they can't be subclassed for a finalizer attack — the validation itself is unchanged. This was the failure that stopped the build at semantickernel-api.
EI_EXPOSE_REP / EI_EXPOSE_REP2: the VoyageAIModels Jackson DTO accessors expose mutable list/array fields, so I annotated the getters/setters/constructor with @SuppressFBWarnings, matching the existing HuggingFace/OpenAI DTOs. (This only surfaced once the first fix let the build reach the VoyageAI module.)

I also merged current main and bumped the module's parent from 1.4.4-RC3-SNAPSHOT to 1.5.1-SNAPSHOT — the old pin made the semantickernel-bom import unresolvable. A full ./mvnw -Pbug-check -Pcompile-jdk17 clean install reactor build is green locally now. PTAL.

fzowl · 2025-11-17T09:57:21Z

Motivation and Context

VoyageAI provides state-of-the-art embeddings models

Description

Adding VoyageAI integration
MicrosoftDocs/semantic-kernel-docs#327

Contribution Checklist

The code builds clean without any errors or warnings
The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
All unit tests pass, and I have added new tests where possible
I didn't break anyone 😄

Martijn Verburg (karianna) · 2025-12-14T00:09:09Z

fzowl - test / build failures if you can PTAL?

Martijn Verburg (karianna) · 2025-12-24T05:05:31Z

fzowl - seeing errors such as:

Error: Medium: Exception thrown in class com.microsoft.semantickernel.services.reranking.RerankResult at new com.microsoft.semantickernel.services.reranking.RerankResult(int, String, double) will leave the constructor. The object under construction remains partially initialized and may be vulnerable to Finalizer attacks. [com.microsoft.semantickernel.services.reranking.RerankResult, com.microsoft.semantickernel.services.reranking.RerankResult] At RerankResult.java:[line 21]At RerankResult.java:[line 21] CT_CONSTRUCTOR_THROW

…CONSTRUCTOR_THROW SpotBugs (bug-check profile) flagged CT_CONSTRUCTOR_THROW on classes whose constructors throw validation exceptions while being non-final, which the Java CI build treats as an error and fails merge-gatekeeper. Marking these value/service classes final removes the finalizer-attack vector SpotBugs warns about while preserving the existing constructor validation.

After merging upstream/main, the repository version advanced to 1.5.1-SNAPSHOT while the VoyageAI module still pinned the old 1.4.4-RC3-SNAPSHOT parent, which made the semantickernel-bom import unresolvable and broke the reactor build.

The VoyageAIModels request/response DTOs expose their mutable list and array fields directly through getters, setters and one constructor, which SpotBugs (bug-check profile) flags as EI_EXPOSE_REP/EI_EXPOSE_REP2. These are plain Jackson-mapped data holders, so annotate the individual accessors with @SuppressFBWarnings, matching the pattern already used by the other aiservices DTOs (e.g. HuggingFace, OpenAI, Google).

fzowl · 2026-08-16T17:45:02Z

Thanks Martijn Verburg (@karianna) — pushed a fix. The bug-check profile was failing on SpotBugs in two stages:

CT_CONSTRUCTOR_THROW: RerankResult, the four VoyageAI service classes, and VoyageAIClient throw validation exceptions from their constructors. Marked those classes final so they can't be subclassed for a finalizer attack — the validation itself is unchanged. This was the failure that stopped the build at semantickernel-api.
EI_EXPOSE_REP / EI_EXPOSE_REP2: the VoyageAIModels Jackson DTO accessors expose mutable list/array fields, so I annotated the getters/setters/constructor with @SuppressFBWarnings, matching the existing HuggingFace/OpenAI DTOs. (This only surfaced once the first fix let the build reach the VoyageAI module.)

I also merged current main and bumped the module's parent from 1.4.4-RC3-SNAPSHOT to 1.5.1-SNAPSHOT — the old pin made the semantickernel-bom import unresolvable. A full ./mvnw -Pbug-check -Pcompile-jdk17 clean install reactor build is green locally now. PTAL.

fzowl · 2025-11-17T09:57:21Z

Motivation and Context

VoyageAI provides state-of-the-art embeddings models

Description

Adding VoyageAI integration
MicrosoftDocs/semantic-kernel-docs#327

Contribution Checklist

The code builds clean without any errors or warnings
The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
All unit tests pass, and I have added new tests where possible
I didn't break anyone 😄

Martijn Verburg (karianna) · 2025-12-14T00:09:09Z

fzowl - test / build failures if you can PTAL?

Martijn Verburg (karianna) · 2025-12-24T05:05:31Z

fzowl - seeing errors such as:

Error: Medium: Exception thrown in class com.microsoft.semantickernel.services.reranking.RerankResult at new com.microsoft.semantickernel.services.reranking.RerankResult(int, String, double) will leave the constructor. The object under construction remains partially initialized and may be vulnerable to Finalizer attacks. [com.microsoft.semantickernel.services.reranking.RerankResult, com.microsoft.semantickernel.services.reranking.RerankResult] At RerankResult.java:[line 21]At RerankResult.java:[line 21] CT_CONSTRUCTOR_THROW

…CONSTRUCTOR_THROW SpotBugs (bug-check profile) flagged CT_CONSTRUCTOR_THROW on classes whose constructors throw validation exceptions while being non-final, which the Java CI build treats as an error and fails merge-gatekeeper. Marking these value/service classes final removes the finalizer-attack vector SpotBugs warns about while preserving the existing constructor validation.

After merging upstream/main, the repository version advanced to 1.5.1-SNAPSHOT while the VoyageAI module still pinned the old 1.4.4-RC3-SNAPSHOT parent, which made the semantickernel-bom import unresolvable and broke the reactor build.

The VoyageAIModels request/response DTOs expose their mutable list and array fields directly through getters, setters and one constructor, which SpotBugs (bug-check profile) flags as EI_EXPOSE_REP/EI_EXPOSE_REP2. These are plain Jackson-mapped data holders, so annotate the individual accessors with @SuppressFBWarnings, matching the pattern already used by the other aiservices DTOs (e.g. HuggingFace, OpenAI, Google).

fzowl · 2026-08-16T17:45:02Z

Thanks Martijn Verburg (@karianna) — pushed a fix. The bug-check profile was failing on SpotBugs in two stages:

CT_CONSTRUCTOR_THROW: RerankResult, the four VoyageAI service classes, and VoyageAIClient throw validation exceptions from their constructors. Marked those classes final so they can't be subclassed for a finalizer attack — the validation itself is unchanged. This was the failure that stopped the build at semantickernel-api.
EI_EXPOSE_REP / EI_EXPOSE_REP2: the VoyageAIModels Jackson DTO accessors expose mutable list/array fields, so I annotated the getters/setters/constructor with @SuppressFBWarnings, matching the existing HuggingFace/OpenAI DTOs. (This only surfaced once the first fix let the build reach the VoyageAI module.)

I also merged current main and bumped the module's parent from 1.4.4-RC3-SNAPSHOT to 1.5.1-SNAPSHOT — the old pin made the semantickernel-bom import unresolvable. A full ./mvnw -Pbug-check -Pcompile-jdk17 clean install reactor build is green locally now. PTAL.

fzowl · 2025-11-17T09:57:21Z

Motivation and Context

VoyageAI provides state-of-the-art embeddings models

Description

Adding VoyageAI integration
MicrosoftDocs/semantic-kernel-docs#327

Contribution Checklist

The code builds clean without any errors or warnings
The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
All unit tests pass, and I have added new tests where possible
I didn't break anyone 😄

Martijn Verburg (karianna) · 2025-12-14T00:09:09Z

fzowl - test / build failures if you can PTAL?

Martijn Verburg (karianna) · 2025-12-24T05:05:31Z

fzowl - seeing errors such as:

Error: Medium: Exception thrown in class com.microsoft.semantickernel.services.reranking.RerankResult at new com.microsoft.semantickernel.services.reranking.RerankResult(int, String, double) will leave the constructor. The object under construction remains partially initialized and may be vulnerable to Finalizer attacks. [com.microsoft.semantickernel.services.reranking.RerankResult, com.microsoft.semantickernel.services.reranking.RerankResult] At RerankResult.java:[line 21]At RerankResult.java:[line 21] CT_CONSTRUCTOR_THROW

…CONSTRUCTOR_THROW SpotBugs (bug-check profile) flagged CT_CONSTRUCTOR_THROW on classes whose constructors throw validation exceptions while being non-final, which the Java CI build treats as an error and fails merge-gatekeeper. Marking these value/service classes final removes the finalizer-attack vector SpotBugs warns about while preserving the existing constructor validation.

After merging upstream/main, the repository version advanced to 1.5.1-SNAPSHOT while the VoyageAI module still pinned the old 1.4.4-RC3-SNAPSHOT parent, which made the semantickernel-bom import unresolvable and broke the reactor build.

The VoyageAIModels request/response DTOs expose their mutable list and array fields directly through getters, setters and one constructor, which SpotBugs (bug-check profile) flags as EI_EXPOSE_REP/EI_EXPOSE_REP2. These are plain Jackson-mapped data holders, so annotate the individual accessors with @SuppressFBWarnings, matching the pattern already used by the other aiservices DTOs (e.g. HuggingFace, OpenAI, Google).

fzowl · 2026-08-16T17:45:02Z

Thanks Martijn Verburg (@karianna) — pushed a fix. The bug-check profile was failing on SpotBugs in two stages:

CT_CONSTRUCTOR_THROW: RerankResult, the four VoyageAI service classes, and VoyageAIClient throw validation exceptions from their constructors. Marked those classes final so they can't be subclassed for a finalizer attack — the validation itself is unchanged. This was the failure that stopped the build at semantickernel-api.
EI_EXPOSE_REP / EI_EXPOSE_REP2: the VoyageAIModels Jackson DTO accessors expose mutable list/array fields, so I annotated the getters/setters/constructor with @SuppressFBWarnings, matching the existing HuggingFace/OpenAI DTOs. (This only surfaced once the first fix let the build reach the VoyageAI module.)

I also merged current main and bumped the module's parent from 1.4.4-RC3-SNAPSHOT to 1.5.1-SNAPSHOT — the old pin made the semantickernel-bom import unresolvable. A full ./mvnw -Pbug-check -Pcompile-jdk17 clean install reactor build is green locally now. PTAL.

fzowl · 2025-11-17T09:57:21Z

Motivation and Context

VoyageAI provides state-of-the-art embeddings models

Description

Adding VoyageAI integration
MicrosoftDocs/semantic-kernel-docs#327

Contribution Checklist

The code builds clean without any errors or warnings
The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
All unit tests pass, and I have added new tests where possible
I didn't break anyone 😄

Martijn Verburg (karianna) · 2025-12-14T00:09:09Z

fzowl - test / build failures if you can PTAL?

Martijn Verburg (karianna) · 2025-12-24T05:05:31Z

fzowl - seeing errors such as:

Error: Medium: Exception thrown in class com.microsoft.semantickernel.services.reranking.RerankResult at new com.microsoft.semantickernel.services.reranking.RerankResult(int, String, double) will leave the constructor. The object under construction remains partially initialized and may be vulnerable to Finalizer attacks. [com.microsoft.semantickernel.services.reranking.RerankResult, com.microsoft.semantickernel.services.reranking.RerankResult] At RerankResult.java:[line 21]At RerankResult.java:[line 21] CT_CONSTRUCTOR_THROW

…CONSTRUCTOR_THROW SpotBugs (bug-check profile) flagged CT_CONSTRUCTOR_THROW on classes whose constructors throw validation exceptions while being non-final, which the Java CI build treats as an error and fails merge-gatekeeper. Marking these value/service classes final removes the finalizer-attack vector SpotBugs warns about while preserving the existing constructor validation.

After merging upstream/main, the repository version advanced to 1.5.1-SNAPSHOT while the VoyageAI module still pinned the old 1.4.4-RC3-SNAPSHOT parent, which made the semantickernel-bom import unresolvable and broke the reactor build.

The VoyageAIModels request/response DTOs expose their mutable list and array fields directly through getters, setters and one constructor, which SpotBugs (bug-check profile) flags as EI_EXPOSE_REP/EI_EXPOSE_REP2. These are plain Jackson-mapped data holders, so annotate the individual accessors with @SuppressFBWarnings, matching the pattern already used by the other aiservices DTOs (e.g. HuggingFace, OpenAI, Google).

fzowl · 2026-08-16T17:45:02Z

Thanks Martijn Verburg (@karianna) — pushed a fix. The bug-check profile was failing on SpotBugs in two stages:

CT_CONSTRUCTOR_THROW: RerankResult, the four VoyageAI service classes, and VoyageAIClient throw validation exceptions from their constructors. Marked those classes final so they can't be subclassed for a finalizer attack — the validation itself is unchanged. This was the failure that stopped the build at semantickernel-api.
EI_EXPOSE_REP / EI_EXPOSE_REP2: the VoyageAIModels Jackson DTO accessors expose mutable list/array fields, so I annotated the getters/setters/constructor with @SuppressFBWarnings, matching the existing HuggingFace/OpenAI DTOs. (This only surfaced once the first fix let the build reach the VoyageAI module.)

I also merged current main and bumped the module's parent from 1.4.4-RC3-SNAPSHOT to 1.5.1-SNAPSHOT — the old pin made the semantickernel-bom import unresolvable. A full ./mvnw -Pbug-check -Pcompile-jdk17 clean install reactor build is green locally now. PTAL.

fzowl · 2025-11-17T09:57:21Z

Motivation and Context

VoyageAI provides state-of-the-art embeddings models

Description

Adding VoyageAI integration
MicrosoftDocs/semantic-kernel-docs#327

Contribution Checklist

The code builds clean without any errors or warnings
The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
All unit tests pass, and I have added new tests where possible
I didn't break anyone 😄

Martijn Verburg (karianna) · 2025-12-14T00:09:09Z

fzowl - test / build failures if you can PTAL?

Martijn Verburg (karianna) · 2025-12-24T05:05:31Z

fzowl - seeing errors such as:

Error: Medium: Exception thrown in class com.microsoft.semantickernel.services.reranking.RerankResult at new com.microsoft.semantickernel.services.reranking.RerankResult(int, String, double) will leave the constructor. The object under construction remains partially initialized and may be vulnerable to Finalizer attacks. [com.microsoft.semantickernel.services.reranking.RerankResult, com.microsoft.semantickernel.services.reranking.RerankResult] At RerankResult.java:[line 21]At RerankResult.java:[line 21] CT_CONSTRUCTOR_THROW

…CONSTRUCTOR_THROW SpotBugs (bug-check profile) flagged CT_CONSTRUCTOR_THROW on classes whose constructors throw validation exceptions while being non-final, which the Java CI build treats as an error and fails merge-gatekeeper. Marking these value/service classes final removes the finalizer-attack vector SpotBugs warns about while preserving the existing constructor validation.

After merging upstream/main, the repository version advanced to 1.5.1-SNAPSHOT while the VoyageAI module still pinned the old 1.4.4-RC3-SNAPSHOT parent, which made the semantickernel-bom import unresolvable and broke the reactor build.

The VoyageAIModels request/response DTOs expose their mutable list and array fields directly through getters, setters and one constructor, which SpotBugs (bug-check profile) flags as EI_EXPOSE_REP/EI_EXPOSE_REP2. These are plain Jackson-mapped data holders, so annotate the individual accessors with @SuppressFBWarnings, matching the pattern already used by the other aiservices DTOs (e.g. HuggingFace, OpenAI, Google).

fzowl · 2026-08-16T17:45:02Z

Thanks Martijn Verburg (@karianna) — pushed a fix. The bug-check profile was failing on SpotBugs in two stages:

CT_CONSTRUCTOR_THROW: RerankResult, the four VoyageAI service classes, and VoyageAIClient throw validation exceptions from their constructors. Marked those classes final so they can't be subclassed for a finalizer attack — the validation itself is unchanged. This was the failure that stopped the build at semantickernel-api.
EI_EXPOSE_REP / EI_EXPOSE_REP2: the VoyageAIModels Jackson DTO accessors expose mutable list/array fields, so I annotated the getters/setters/constructor with @SuppressFBWarnings, matching the existing HuggingFace/OpenAI DTOs. (This only surfaced once the first fix let the build reach the VoyageAI module.)

I also merged current main and bumped the module's parent from 1.4.4-RC3-SNAPSHOT to 1.5.1-SNAPSHOT — the old pin made the semantickernel-bom import unresolvable. A full ./mvnw -Pbug-check -Pcompile-jdk17 clean install reactor build is green locally now. PTAL.

fzowl · 2025-11-17T09:57:21Z

Motivation and Context

VoyageAI provides state-of-the-art embeddings models

Description

Adding VoyageAI integration
MicrosoftDocs/semantic-kernel-docs#327

Contribution Checklist

The code builds clean without any errors or warnings
The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
All unit tests pass, and I have added new tests where possible
I didn't break anyone 😄

Martijn Verburg (karianna) · 2025-12-14T00:09:09Z

fzowl - test / build failures if you can PTAL?

Martijn Verburg (karianna) · 2025-12-24T05:05:31Z

fzowl - seeing errors such as:

Error: Medium: Exception thrown in class com.microsoft.semantickernel.services.reranking.RerankResult at new com.microsoft.semantickernel.services.reranking.RerankResult(int, String, double) will leave the constructor. The object under construction remains partially initialized and may be vulnerable to Finalizer attacks. [com.microsoft.semantickernel.services.reranking.RerankResult, com.microsoft.semantickernel.services.reranking.RerankResult] At RerankResult.java:[line 21]At RerankResult.java:[line 21] CT_CONSTRUCTOR_THROW

…CONSTRUCTOR_THROW SpotBugs (bug-check profile) flagged CT_CONSTRUCTOR_THROW on classes whose constructors throw validation exceptions while being non-final, which the Java CI build treats as an error and fails merge-gatekeeper. Marking these value/service classes final removes the finalizer-attack vector SpotBugs warns about while preserving the existing constructor validation.

After merging upstream/main, the repository version advanced to 1.5.1-SNAPSHOT while the VoyageAI module still pinned the old 1.4.4-RC3-SNAPSHOT parent, which made the semantickernel-bom import unresolvable and broke the reactor build.

The VoyageAIModels request/response DTOs expose their mutable list and array fields directly through getters, setters and one constructor, which SpotBugs (bug-check profile) flags as EI_EXPOSE_REP/EI_EXPOSE_REP2. These are plain Jackson-mapped data holders, so annotate the individual accessors with @SuppressFBWarnings, matching the pattern already used by the other aiservices DTOs (e.g. HuggingFace, OpenAI, Google).

fzowl · 2026-08-16T17:45:02Z

Thanks Martijn Verburg (@karianna) — pushed a fix. The bug-check profile was failing on SpotBugs in two stages:

CT_CONSTRUCTOR_THROW: RerankResult, the four VoyageAI service classes, and VoyageAIClient throw validation exceptions from their constructors. Marked those classes final so they can't be subclassed for a finalizer attack — the validation itself is unchanged. This was the failure that stopped the build at semantickernel-api.
EI_EXPOSE_REP / EI_EXPOSE_REP2: the VoyageAIModels Jackson DTO accessors expose mutable list/array fields, so I annotated the getters/setters/constructor with @SuppressFBWarnings, matching the existing HuggingFace/OpenAI DTOs. (This only surfaced once the first fix let the build reach the VoyageAI module.)

I also merged current main and bumped the module's parent from 1.4.4-RC3-SNAPSHOT to 1.5.1-SNAPSHOT — the old pin made the semantickernel-bom import unresolvable. A full ./mvnw -Pbug-check -Pcompile-jdk17 clean install reactor build is green locally now. PTAL.

fzowl · 2025-11-17T09:57:21Z

Motivation and Context

VoyageAI provides state-of-the-art embeddings models

Description

Adding VoyageAI integration
MicrosoftDocs/semantic-kernel-docs#327

Contribution Checklist

The code builds clean without any errors or warnings
The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
All unit tests pass, and I have added new tests where possible
I didn't break anyone 😄

Martijn Verburg (karianna) · 2025-12-14T00:09:09Z

fzowl - test / build failures if you can PTAL?

Martijn Verburg (karianna) · 2025-12-24T05:05:31Z

fzowl - seeing errors such as:

Error: Medium: Exception thrown in class com.microsoft.semantickernel.services.reranking.RerankResult at new com.microsoft.semantickernel.services.reranking.RerankResult(int, String, double) will leave the constructor. The object under construction remains partially initialized and may be vulnerable to Finalizer attacks. [com.microsoft.semantickernel.services.reranking.RerankResult, com.microsoft.semantickernel.services.reranking.RerankResult] At RerankResult.java:[line 21]At RerankResult.java:[line 21] CT_CONSTRUCTOR_THROW

…CONSTRUCTOR_THROW SpotBugs (bug-check profile) flagged CT_CONSTRUCTOR_THROW on classes whose constructors throw validation exceptions while being non-final, which the Java CI build treats as an error and fails merge-gatekeeper. Marking these value/service classes final removes the finalizer-attack vector SpotBugs warns about while preserving the existing constructor validation.

After merging upstream/main, the repository version advanced to 1.5.1-SNAPSHOT while the VoyageAI module still pinned the old 1.4.4-RC3-SNAPSHOT parent, which made the semantickernel-bom import unresolvable and broke the reactor build.

The VoyageAIModels request/response DTOs expose their mutable list and array fields directly through getters, setters and one constructor, which SpotBugs (bug-check profile) flags as EI_EXPOSE_REP/EI_EXPOSE_REP2. These are plain Jackson-mapped data holders, so annotate the individual accessors with @SuppressFBWarnings, matching the pattern already used by the other aiservices DTOs (e.g. HuggingFace, OpenAI, Google).

fzowl · 2026-08-16T17:45:02Z

Thanks Martijn Verburg (@karianna) — pushed a fix. The bug-check profile was failing on SpotBugs in two stages:

CT_CONSTRUCTOR_THROW: RerankResult, the four VoyageAI service classes, and VoyageAIClient throw validation exceptions from their constructors. Marked those classes final so they can't be subclassed for a finalizer attack — the validation itself is unchanged. This was the failure that stopped the build at semantickernel-api.
EI_EXPOSE_REP / EI_EXPOSE_REP2: the VoyageAIModels Jackson DTO accessors expose mutable list/array fields, so I annotated the getters/setters/constructor with @SuppressFBWarnings, matching the existing HuggingFace/OpenAI DTOs. (This only surfaced once the first fix let the build reach the VoyageAI module.)

I also merged current main and bumped the module's parent from 1.4.4-RC3-SNAPSHOT to 1.5.1-SNAPSHOT — the old pin made the semantickernel-bom import unresolvable. A full ./mvnw -Pbug-check -Pcompile-jdk17 clean install reactor build is green locally now. PTAL.

Adding VoyageAI integration
27647c2

Martijn Verburg (karianna) requested a review from John (johnoliver)November 23, 2025 23:25

Merge branch 'main' into voyageai_integration
a26b027

Adding voyage-multimodal-3.5 tests
eb9a8cc

fzowland others added 6 commits January 24, 2026 15:55

Merge branch 'main' into voyageai_integration
a21efc3

Merge branch 'main' into voyageai_integration
ab661a6

Merge remote-tracking branch 'upstream/main' into voyageai_integration
2ae4952

fzowl mentioned this pull request Aug 16, 2026
Adding VoyageAI integration fzowl/semantic-kernel-java#1
Open

Adding VoyageAI integration
27647c2

Martijn Verburg (karianna) requested a review from John (johnoliver)November 23, 2025 23:25

Merge branch 'main' into voyageai_integration
a26b027

Adding voyage-multimodal-3.5 tests
eb9a8cc

fzowland others added 6 commits January 24, 2026 15:55

Merge branch 'main' into voyageai_integration
a21efc3

Merge branch 'main' into voyageai_integration
ab661a6

Merge remote-tracking branch 'upstream/main' into voyageai_integration
2ae4952

fzowl mentioned this pull request Aug 16, 2026
Adding VoyageAI integration fzowl/semantic-kernel-java#1
Open

Adding VoyageAI integration
27647c2

Martijn Verburg (karianna) requested a review from John (johnoliver)November 23, 2025 23:25

Merge branch 'main' into voyageai_integration
a26b027

Adding voyage-multimodal-3.5 tests
eb9a8cc

fzowland others added 6 commits January 24, 2026 15:55

Merge branch 'main' into voyageai_integration
a21efc3

Merge branch 'main' into voyageai_integration
ab661a6

Merge remote-tracking branch 'upstream/main' into voyageai_integration
2ae4952

fzowl mentioned this pull request Aug 16, 2026
Adding VoyageAI integration fzowl/semantic-kernel-java#1
Open

Adding VoyageAI integration
27647c2

Martijn Verburg (karianna) requested a review from John (johnoliver)November 23, 2025 23:25

Merge branch 'main' into voyageai_integration
a26b027

Adding voyage-multimodal-3.5 tests
eb9a8cc

fzowland others added 6 commits January 24, 2026 15:55

Merge branch 'main' into voyageai_integration
a21efc3

Merge branch 'main' into voyageai_integration
ab661a6

Merge remote-tracking branch 'upstream/main' into voyageai_integration
2ae4952

fzowl mentioned this pull request Aug 16, 2026
Adding VoyageAI integration fzowl/semantic-kernel-java#1
Open

Adding VoyageAI integration
27647c2

Martijn Verburg (karianna) requested a review from John (johnoliver)November 23, 2025 23:25

Merge branch 'main' into voyageai_integration
a26b027

Adding voyage-multimodal-3.5 tests
eb9a8cc

fzowland others added 6 commits January 24, 2026 15:55

Merge branch 'main' into voyageai_integration
a21efc3

Merge branch 'main' into voyageai_integration
ab661a6

Merge remote-tracking branch 'upstream/main' into voyageai_integration
2ae4952

fzowl mentioned this pull request Aug 16, 2026
Adding VoyageAI integration fzowl/semantic-kernel-java#1
Open

Adding VoyageAI integration
27647c2

Martijn Verburg (karianna) requested a review from John (johnoliver)November 23, 2025 23:25

Merge branch 'main' into voyageai_integration
a26b027

Adding voyage-multimodal-3.5 tests
eb9a8cc

fzowland others added 6 commits January 24, 2026 15:55

Merge branch 'main' into voyageai_integration
a21efc3

Merge branch 'main' into voyageai_integration
ab661a6

Merge remote-tracking branch 'upstream/main' into voyageai_integration
2ae4952

fzowl mentioned this pull request Aug 16, 2026
Adding VoyageAI integration fzowl/semantic-kernel-java#1
Open

Adding VoyageAI integration
27647c2

Martijn Verburg (karianna) requested a review from John (johnoliver)November 23, 2025 23:25

Merge branch 'main' into voyageai_integration
a26b027

Adding voyage-multimodal-3.5 tests
eb9a8cc

fzowland others added 6 commits January 24, 2026 15:55

Merge branch 'main' into voyageai_integration
a21efc3

Merge branch 'main' into voyageai_integration
ab661a6

Merge remote-tracking branch 'upstream/main' into voyageai_integration
2ae4952

fzowl mentioned this pull request Aug 16, 2026
Adding VoyageAI integration fzowl/semantic-kernel-java#1
Open

Adding VoyageAI integration
27647c2

Martijn Verburg (karianna) requested a review from John (johnoliver)November 23, 2025 23:25

Merge branch 'main' into voyageai_integration
a26b027

Adding voyage-multimodal-3.5 tests
eb9a8cc

fzowland others added 6 commits January 24, 2026 15:55

Merge branch 'main' into voyageai_integration
a21efc3

Merge branch 'main' into voyageai_integration
ab661a6

Merge remote-tracking branch 'upstream/main' into voyageai_integration
2ae4952

fzowl mentioned this pull request Aug 16, 2026
Adding VoyageAI integration fzowl/semantic-kernel-java#1
Open

Uh oh!

Conversation

fzowl commented Nov 17, 2025• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Motivation and Context

Description

Contribution Checklist

Uh oh!

Martijn Verburg (karianna) commented Dec 14, 2025

Uh oh!

Martijn Verburg (karianna) commented Dec 24, 2025

Uh oh!

fzowl commented Aug 16, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

fzowl commented Nov 17, 2025• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Motivation and Context

Description

Contribution Checklist

Uh oh!

Martijn Verburg (karianna) commented Dec 14, 2025

Uh oh!

Martijn Verburg (karianna) commented Dec 24, 2025

Uh oh!

fzowl commented Aug 16, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

fzowl commented Nov 17, 2025• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Motivation and Context

Description

Contribution Checklist

Uh oh!

Martijn Verburg (karianna) commented Dec 14, 2025

Uh oh!

Martijn Verburg (karianna) commented Dec 24, 2025

Uh oh!

fzowl commented Aug 16, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

fzowl commented Nov 17, 2025• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Motivation and Context

Description

Contribution Checklist

Uh oh!

Martijn Verburg (karianna) commented Dec 14, 2025

Uh oh!

Martijn Verburg (karianna) commented Dec 24, 2025

Uh oh!

fzowl commented Aug 16, 2026

Uh oh!

fzowl commented Nov 17, 2025•
edited
Loading

fzowl commented Nov 17, 2025•
edited
Loading

fzowl commented Nov 17, 2025•
edited
Loading

fzowl commented Nov 17, 2025•
edited
Loading

fzowl commented Nov 17, 2025•
edited
Loading

fzowl commented Nov 17, 2025•
edited
Loading