.Net: gpt-image-1 is the default image model in the .NET OpenAI connector, and OpenAI shuts it down on October 23
Maintainers usually reply within 4 days
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 73/100
Research direction
Read the two reported fallbacks in Services/OpenAITextToImageService.cs:39 and Core/ClientCore.TextToImage.cs:44, then verify the provider's deprecation notice. Check how the .NET connector selects default image models and run the relevant tests. Done when its defaults no longer name the model scheduled for shutdown and the tests pass.
Written by the indexing model from the issue text.
Description
Hi, quick heads-up in case this isn't already on your radar.
OpenAI shuts down gpt-image-1 on October 23, 2026, three weeks from now. After that, requests that name it fail. OpenAI's replacement is gpt-image-2.
The .NET OpenAI connector uses it as the default image model when the caller doesn't pass a model id, so anyone generating images with the defaults would start getting errors on that date:
Services/OpenAITextToImageService.cs:39, wheremodelId ?? "gpt-image-1"is used when the service is createdCore/ClientCore.TextToImage.cs:44, the same fallback right beforeGenerateImageAsync
It's still there on the default branch as of October 2. OpenAI's notice is on their deprecations page.
How I found it: I maintain DocsWatcher, an open source scanner that checks code against the deprecation notices providers publish, and I run it over popular open source repositories. Most of what it turns up is model names sitting in lists and price tables, which don't break anything, so I read every hit in real code myself before opening anything. This one looked like a real call to me, but you know your code and I don't, so if I've got it wrong just say so and I'll close this.
Nothing to adopt here. I just thought you'd want to know.
- Dominant language
- C#
- Stars
- 28.6k
- Forks
- 4.8k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 12
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a 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.
More from microsoft/semantic-kernel
-
Python: VolatileMemoryStore.get_batch and get_nearest_matches ignore with_embeddings=False (deepcopy result is discarded)Possibly taken @VANDRANKI claimed this 4 days ago. Openpython triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
microsoft/semantic-kernel#14522 ·
Maintainers usually reply within 4 days
-
Python: VolatileMemoryStore.get_nearest_match returns an un-awaited coroutine instead of a (MemoryRecord, score) tuplePossibly taken @VANDRANKI claimed this 4 days ago. Openpython triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
microsoft/semantic-kernel#14521 ·
Maintainers usually reply within 4 days
-
.Net: Bug: BinaryContent does not decode the %xx escapes of a non-base64 data URIPossibly taken @Laurianti claimed this 4 days ago. Open.NET triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
microsoft/semantic-kernel#14518 ·
Maintainers usually reply within 4 days
-
Python: FunctionCallContent.combine_arguments drops a streamed "{}" chunk, producing invalid JSON argumentsPossibly taken @VANDRANKI claimed this 5 days ago. Openpython triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
microsoft/semantic-kernel#14512 · 2 comments ·
Maintainers usually reply within 4 days
-
.Net: Python: KernelJsonSchemaBuilder emits {"type": "object"} with no enum for typing.Literal parameters and fieldsPossibly taken @VANDRANKI claimed this 5 days ago. Open.NET python triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
microsoft/semantic-kernel#14511 ·
Maintainers usually reply within 4 days
All issues in microsoft/semantic-kernel
Similar issues
-
subsystem: UI
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Open-Systems-Pharmacology/PK-Sim#3812 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
PCL-Community/PCL-CE#3652 ·
Maintainers usually reply within 1 day
-
bug effort:S P3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nightscout/nocturne#2012 ·
Maintainers usually reply within 1 day
-
area:frontend bug FE P3
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
klasolsson81/jobbliggaren#2010 ·
Maintainers usually reply within 1 day
-
agentic-workflows untriaged
Difficulty 1/5 Under an hour Newbie friendliness 65/100
Maintainers usually reply within 1 day