Four things reached their end this week: two .NET versions, a PostgreSQL major, five Claude models in some Bedrock regions, and a GitHub REST endpoint. None of them throws an error you would notice on day one, which is why they are worth a list.
Every date below was re-read from its source on Friday, November 13, 2026.
This week
Tue Nov 10: .NET 8 and .NET 9, end of support. No more patches, security ones included. .NET 10 is the LTS to move to, supported until November 14, 2028. (Microsoft .NET support policy)
Thu Nov 12: PostgreSQL 14, final release. The last one is 14.25. Servers keep running; fixes stop. PostgreSQL 18 is supported until November 14, 2030, and pg_upgrade goes from 14 to 18 in one step. (PostgreSQL versioning policy)
Fri Nov 13: five Claude models reach end of life on Amazon Bedrock, in some regions only. AWS says requests fail "on, or soon after the EOL date." (Bedrock model lifecycle)
| Model ID | Regions ending Nov 13 |
|---|---|
anthropic.claude-3-haiku-20240307-v1:0 | ap-northeast-2, ap-south-1, ap-southeast-1, eu-central-2, sa-east-1 |
anthropic.claude-3-sonnet-20240229-v1:0 | ap-south-1, ap-southeast-1, eu-west-2, sa-east-1 |
anthropic.claude-3-5-sonnet-20240620-v1:0 | ap-northeast-2, ap-south-1, ap-southeast-1 |
anthropic.claude-3-5-sonnet-20241022-v2:0 | ap-northeast-2, ap-south-1, ap-southeast-1 |
anthropic.claude-3-7-sonnet-20250219-v1:0 | ap-south-1, eu-west-2 |
Claude 3 Haiku and Claude 3 Sonnet keep running in ca-central-1 until November 27. If you call these from a region not in the table, check that region's own state: AWS says a model "can remain Active in other Regions."
Fri Nov 13: GitHub's synchronous SBOM endpoint, sunset. GET /repos/{owner}/{repo}/dependency-graph/sbom is replaced by generate-report plus fetch-report. It was still answering this morning, but its own sunset header says November 13. (GitHub changelog)
Next week
| Date | What | Source |
|---|---|---|
| Sun Nov 15 | claude-haiku-4-5 and codex-mini (2025-05-16) retire on Microsoft Foundry | Foundry schedule |
| Tue Nov 17 | Earliest shutdown for five Gemini API previews: gemini-2.5-flash-preview-tts, gemini-2.5-pro-preview-tts, gemini-3.1-flash-tts-preview, gemini-3.1-flash-live-preview, gemini-2.5-flash-native-audio-preview-12-2025 | Gemini deprecations |
| Tue Nov 17 | gpt-chat-latest versions 2026-05-05 and 2026-06-24 retire on Foundry | Foundry schedule |
| Thu Nov 19 | o1, o1-pro, o3, o3-pro, o3-mini, o3-deep-research, o4-mini and Llama-4-Maverick-17B-128E-Instruct-FP8 retire on Foundry | Foundry schedule |
Two notes on next week. Google's dates are floors: its page says they are "the earliest possible dates on which a model might be retired." And the Foundry o-series dates are Azure's only; on the OpenAI API, o3 runs until December 11.
Microsoft's lifecycle page says a retired Foundry model returns 410 Gone for every request.
The quickest check for all of it is a grep for the IDs above in your repo, your .env files and your deploy config. I keep all of these dates in one public calendar at since.dev/calendar.
Which of these did you have to deal with this week, and which one did you only find out about here?
I'm Nabil. I build Since, which tracks what your code depends on and tells you before it breaks.
