Skip to content

chore[notask]: revert Opus registry removal (premature — SDK still references them)#1627

Merged
Alok-Ranjan23 merged 1 commit into
mainfrom
revert/opus-registry-entries
Apr 16, 2026
Merged

chore[notask]: revert Opus registry removal (premature — SDK still references them)#1627
Alok-Ranjan23 merged 1 commit into
mainfrom
revert/opus-registry-entries

Conversation

@Alok-Ranjan23

Copy link
Copy Markdown
Contributor

Summary

Reverts commit 436e29c (PR #1602) which removed 32 Opus model entries from the registry server.

Why

The registry entries were removed before the SDK stopped referencing them. The published SDK (@qvac/sdk@0.8.3) still exports MARIAN_OPUS_* constants. Users on that version get broken model resolution because the registry no longer has the Opus entries.

Correct order:

  1. First: SDK removes Opus constants (PR QVAC-14576 chore[bc]: remove Opus NMT engine from SDK API surface #1622)
  2. Publish new SDK version
  3. Then: remove Opus from registry

What's restored

  • 32 Opus/Marian entries in data/models.prod.json (680 → 712)
  • Marian attribution in NOTICE (Apache-2.0 + CC-BY-4.0 sections)
  • 22 ggml-opus-* entries in client/NOTICE

@github-actions

github-actions Bot commented Apr 16, 2026

Copy link
Copy Markdown
Contributor

Tier-based Approval Status

**PR Tier:** TIER1

**Current Status:** ✅ APPROVED

**Requirements:**
- 1 Team Member approval ❌ (0/1)
- 1 Team Lead OR Management approval ✅ (2/1)

**Bypass rule:** Triggered (2+ Team Lead approvals (Tier 1 exception)). This PR is approved regardless of tier.

---
*This comment is automatically updated when reviews change.*

@Alok-Ranjan23 Alok-Ranjan23 merged commit 3ebee8c into main Apr 16, 2026
43 of 45 checks passed
@Alok-Ranjan23 Alok-Ranjan23 deleted the revert/opus-registry-entries branch April 16, 2026 12:35
Proletter pushed a commit that referenced this pull request May 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants