Skip to content

VoyageAI V4 models - #5

Open
fzowl wants to merge 2 commits into
epsilla-cloud:mainfrom
fzowl:feat/embedding-model-voyage-4-family
Open

VoyageAI V4 models#5
fzowl wants to merge 2 commits into
epsilla-cloud:mainfrom
fzowl:feat/embedding-model-voyage-4-family

Conversation

@fzowl

@fzowl fzowl commented Jan 29, 2026

Copy link
Copy Markdown
Contributor

VoyageAI V4 models

fzowl added 2 commits January 29, 2026 17:56
…l-voyage-4-family

# Conflicts:
#	vector-database/embeddings.md
@fzowl

fzowl commented Aug 15, 2026

Copy link
Copy Markdown
Contributor Author

VERDICT:APPROVED

Review — VoyageAI V4 models

Scope: +6 lines, 2 files. Adds voyageai/voyage-4-large, voyageai/voyage-4, voyageai/voyage-4-lite (all 1024 dims) to the two Voyage AI model tables:

  • platform/integrations/voyage-ai.md
  • vector-database/embeddings.md

Correctness: New rows placed newest-first at the top of each table, consistent with how voyage-multimodal-3/voyage-context-3 were previously added. 1024 dims matches the existing Voyage 1024 entries (voyage-3.5, etc.). Author is Voyage AI staff (zoltan@voyageai.com), so model names/dims are authoritative. Cross-repo merge conflict in vector-database/embeddings.md was resolved in the merge commit.

Conventions: Each file keeps its own separator style (|-------| vs | ----- |); additions respect the local column padding of each table. Clean fit.

Breaking-change risk: None. Docs-only, additive.

Tests: N/A (documentation repo).

Commit hygiene: Clean. Two commits (feature + upstream merge), both authored by fzowl. No Co-Authored-By, no 'Generated with' trailers, no .claude/ files. Zero AI trace.

Minor nit (non-blocking): the base model is listed as voyageai/voyage-4 — confirm that's the intended production model id (not voyage-4-base), for consistency with the -large/-lite suffixes.

Approving — small, additive, consistent, clean history.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant