Noteworthy changes, edited into a practical daily brief.
Issue checked:
This issue includes verified public sources only; event dates and issue date are shown separately.
01 / OpenAI APIOfficial documentation
Event date ·
Selected GPT-4 API snapshots receive retirement dates
Announced October14: listed API snapshots are scheduled to shut down January14,2027. Exact IDs and scope appear below.
API model lifecycle
Scope: listed API snapshots only. This does not establish retirement of ChatGPT products or local weights.
Announcement date
Scheduled shutdown date
Explicitly listed API snapshots
gpt-4o-2024-08-06
gpt-4o-2024-11-20
gpt-4o-mini-2024-07-18
gpt-4.1-2025-04-14
gpt-4.1-mini-2025-04-14
Fine-tuned versions follow their base model’s shutdown schedule.
Officially suggested replacement: gpt-6-luna
Dates are recorded as published; no timezone or exact instant is given. Check interface,pricing and output before migration; no migration test was run here.
Who should care · How to start
Who should care
Developers still selecting these API snapshots or their fine-tuned versions.
How to start
Match full configured IDs first; evaluate the suggested replacement’s interface,cost and outputs. This site needs no key.
Boundaries
A retirement schedule,not a successful migration or ChatGPT-wide shutdown notice.
Cline extension fixes long local-model request timeouts
v4.1.25 fixes BodyTimeoutError after five silent minutes during large LM Studio/Ollama requests. Newly entered OpenAI Compatible base URLs are used verbatim.
Who should care · How to start
Who should care
Cline VS Code users with local models or custom compatible endpoints.
How to start
Record extension version and settings before a small check. Old saved host-only URLs receive /v1 once; do not remove /v1 indiscriminately. Pin model IDs to avoid default changes.
Boundaries
Extension release, not CLI/SDK. Cloud sessions roll out gradually and require opt-in; eligibility/cost unverified. No Cline upgrade or execution here.
October14 change: authorization redirects include iss=https://discord.com under RFC9207.
Who should care · How to start
Who should care
Developers implementing Discord OAuth2 callbacks, especially with multiple authorization providers.
How to start
Review callback parsing and expected issuer against official docs. Retain state validation; receiving iss is not a successful login. Test separately; never paste authorization codes here.
Boundaries
OAuth2 response change, not a new bot API version or a universal login rewrite. No Discord connection or live login test here.