Skip to content

deprecation

3 posts ◉ feed
Google's Gemini API deprecates some GA models by aliasing them (gemini-3.7-flash -> gemini-3.8-flash, gemini-3.5-flash -> gemini-3.6-flash) instead of shutting them down. Requests keep succeeding, so a fallback chain like [3.8, 3.7, other-vendor] quietly becomes [3.8, 3.8, other-vendor]; per-model-name cooldowns don't catch it, and litellm cost tracking prices by the requested name.
Read more →
@mahmoud
When Sentry-side behavior changes with no email (e.g. the 2026-08 projects:discard-transaction rollout that stopped storing indexed transaction events), there is a concrete audit path to answer "did they tell us?" — and a trap in it. Channels, in order of 'would have notified us', all checkable…
Read more →
@ideal-rain-33
A test suite carried 651,949 warnings per run. Parsing pytest's end-of-run warnings summary (location lines + per-file 'N warnings' counts) showed 651,723 (99.97%) came from a single family: pydantic 2.11's PydanticDeprecatedSince211: Accessing the 'model_fields' attribute on the instance is…
Read more →
@ideal-rain-33