Remove Nova Premier (us.amazon.nova-premier-v1:0) from Studio model picker before its Sept 14, 2026 EOL
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 72/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- aws, typescript
- Domain
- cloud, documentation, frontend
Research direction
Start with the model catalog entries in frontend/src/studio/lib/models.ts and apps/studio/src/components/property-panel.tsx, then inspect the Nova Premier branches in frontend/src/studio/PropertyPanel.tsx, the code generators, and docs/studio-integration.md. Remove the obsolete catalog and model-specific references as scoped, and verify Nova Premier is no longer selectable while unrelated model handling remains intact.
Written by the indexing model from the issue text.
Description
Summary
us.amazon.nova-premier-v1:0 (Amazon Nova Premier) is scheduled for end of life on Amazon Bedrock on September 14, 2026. It is still offered as a selectable model in the Studio model picker. After the EOL date any agent built with it will fail at first invoke with a model-not-available error, so the entry should be removed before then.
anthropic.claude-opus-4-1-20250805-v1:0 (Claude Opus 4.1) is also on the EOL list (January 8, 2027) but is not referenced anywhere in this repo, so no action is needed for it.
Where Nova Premier is referenced (main)
Model catalog entries (user-facing, should be removed):
frontend/src/studio/lib/models.ts:83—{ model_id: 'us.amazon.nova-premier-v1:0', model_name: 'Amazon Nova Premier v1' }apps/studio/src/components/property-panel.tsx:129— same entry in the legacy Studio app
Model-specific handling (can be removed once the catalog entry is gone, or left as harmless dead branches):
frontend/src/studio/PropertyPanel.tsx:609—if (modelId.includes('nova-premier'))frontend/src/studio/lib/code-generator.ts:1498and:1604—max_tokensclamp to 32000frontend/src/studio/lib/graph-code-generator.ts:94— same clampdocs/studio-integration.md:295— documents the clamp
DEFAULT_MODEL_ID is unaffected (it is Sonnet 5), and no backend, evaluation, A/B, or governance code path references Nova Premier. Impact is limited to users who manually pick it from the dropdown.
Suggested change
- Remove the two catalog entries so the model can no longer be selected.
- Drop the
nova-premierspecial-casing inPropertyPanel.tsx,code-generator.ts,graph-code-generator.ts, and the note indocs/studio-integration.md. - Optionally, show a warning in the property panel when loading a saved flow whose node still carries
us.amazon.nova-premier-v1:0, so existing flows are not silently broken.
Reference
Amazon Bedrock model lifecycle: https://docs.aws.amazon.com/bedrock/latest/userguide/model-lifecycle.html
- Dominant language
- Python
- Stars
- 14
- Forks
- 2
- Avg merge
- 2h 9m
- Merged PRs (30d)
- 124
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 87/100
adri0/scadustats#128 ·
Maintainers usually reply within 1 day
-
`TIMESTAMP`, `TIMESTAMP_NTZ`, `TINYINT` and the other `TypeDecorator`s don't declare `python_type`Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
RPBCOpenawaiting policy acceptance precheck-passed
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Bioconductor/BiocContributions#240 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
documentation good first issue launch
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
FlologixAI/etchwork#4 ·