docs(blog): recount July stability update provider fixes to 41 and group them by failure class#548
Open
mateo-berri wants to merge 1 commit into
Open
docs(blog): recount July stability update provider fixes to 41 and group them by failure class#548mateo-berri wants to merge 1 commit into
mateo-berri wants to merge 1 commit into
Conversation
…oup them by failure class
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The July stability update counted 27 LLM provider fixes, but counting every merged provider-area fix PR in the window gives 41. This PR updates the post to use 41 and restructures the provider section so it reads as a stability story: how many bugs were quashed and where, what classes of bugs they were, and the structural fix behind them (capabilities and prices as declared data instead of per-surface guesses). The appendix is regrouped by those failure classes and expanded to list every counted fix, and the title, description, and intro now name provider translation as the third major issue alongside MCP auth and pass-through memory
Two things to verify before merge: the bug-class recount (15 capabilities dropped, 12 broken output, 8 billing, 6 request auth/URL building) replaces the old routing class because the routing work in the window was features and refactors rather than fixes, now listed in the appendix as hardening; and By the numbers assumes the 14 fixes reclassified into LLM Providers previously sat under Proxy Core / Reliability (23 -> 9), which should be checked against the triage sheet so the areas still sum to 134