Replace decommissioned Groq model, add CI - #3
Merged
Conversation
Groq retired llama-3.3-70b-versatile. The three routes using it (goal-plan, voice-pep, weekly-insight) returned 500 with "model does not exist or you do not have access to it". Switched them to openai/gpt-oss-20b, which coach, daily-plan and weekly-dungeon were already using successfully. All six routes verified live against production after this change. Also adds a CI workflow (npm ci, tsc --noEmit, lint, build) on push and PR to main. The production build was silently broken for ~32 days after the Snyk bump to next 16.2.9 left node_modules drifted from the lockfile; nothing surfaced it. npm ci in CI catches exactly that. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@ai-sdk/gateway, @ai-sdk/groq and @ai-sdk/provider all declare "node": ">=22". On Node 20 the install emitted EBADENGINE for each, and npm 10 (bundled with Node 20) installed @ai-sdk/*@4.0.0 — versions the committed lockfile does not contain — which broke the build with "The export serializeModelOptions was not found". A fresh clone of this branch on Node 22 with npm 11 installs exactly what the lockfile pins (@ai-sdk/groq@3.0.38) and builds clean. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Two Snyk changes on main contradict each other: - PR #2 bumped @ai-sdk/groq to ^4.0.0. groq@4.0.0 depends on @ai-sdk/provider-utils 5.0.0. - An earlier SSRF fix added overrides["@ai-sdk/provider-utils"]="^4.0.41". The override caps provider-utils below what groq@4 needs. 4.0.41 does not export serializeModelOptions, which groq@4.0.0 imports, so every build since a899a87 failed with: The export serializeModelOptions was not found in module @ai-sdk/provider-utils This is why the last successful Vercel deploy was 32 days ago. Lifting the override to ^5.0.0 resolves provider-utils@5.0.32, which groq@4 requires. npm audit confirms the ai-sdk and undici advisories the override was protecting against remain resolved — a newer version supersedes the pin, so no security regression. Verified: tsc --noEmit exit 0, next build compiles all six routes. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
anishkb-dev
force-pushed
the
fix/dead-groq-model-and-ci
branch
from
August 28, 2026 10:25
61ba7f2 to
389546c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Groq retired
llama-3.3-70b-versatile. The three routes using it —goal-plan,voice-pep,weekly-insight— returned 500 with "The modelllama-3.3-70b-versatiledoes not exist or you do not have access to it."Switched them to
openai/gpt-oss-20b, whichcoach,daily-planandweekly-dungeonwere already using successfully.Also adds a CI workflow:
npm ci→tsc --noEmit→lint→build, on push and PR tomain.Why the CI matters
Production was broken for ~32 days and nothing surfaced it. Three stacked causes, each hiding the next:
next→ 16.2.9 plus apostcssoverride) leftnode_modulesdrifted frompackage-lock.json, so every build failed. Vercel reported this as a "git provider server error", which sent the diagnosis the wrong way.npm cifixed it.CI uses
npm cispecifically because it installs strictly from the lockfile — exactly the drift that caused #2.Verification
All six routes probed against production after the model change:
Locally:
tsc --noEmitexit 0,lintexit 0,build✓ compiled, 10/10 static pages.Notes
voice-pepandweekly-insightwere written for a 70B model; their prompts ask for prose with specific texture. Output on a 20B model may read flatter and the prompts may need tightening.ELEVENLABS_API_KEYis not set in production, sovoice-pepreturnsaudioBase64: null. It degrades gracefully.🤖 Generated with Claude Code