fix(providers): require API key for Pollinations and fix optional key i18n labels (#11096) - #11117
Merged
diegosouzapw merged 2 commits intoAug 22, 2026
Conversation
rqzbeh
force-pushed
the
fix/pollinations-api-key-required
branch
from
August 22, 2026 12:24
6a67807 to
eb0b24d
Compare
rqzbeh
force-pushed
the
fix/pollinations-api-key-required
branch
from
August 22, 2026 15:03
eb0b24d to
0e91881
Compare
diegosouzapw
force-pushed
the
fix/pollinations-api-key-required
branch
from
August 22, 2026 18:58
330a00f to
9ebe213
Compare
diegosouzapw
merged commit Aug 22, 2026
3157e8a
into
diegosouzapw:release/v3.8.50
5 of 7 checks passed
diegosouzapw
pushed a commit
that referenced
this pull request
Aug 23, 2026
…ol (#9827) (#11194) Validated on the combined batch board over tip 8a42aee: static gates clean (changelog, file-size 159 frozen, complexity 2621<=2774, cognitive 1181<=1223, dead-code 408<=416), typecheck:core clean, 107 focused tests green. Keyless pollinations 401s no longer poison the noauth pool — key health classification treats the now-required-key provider correctly after #11117. chatcore-key-health + executor-pollinations green. Fixes #9827. Thank you @jonlwheat2-gif!
muhamadgalihsaputra
pushed a commit
to niyatna/NiyatnaRoute
that referenced
this pull request
Sep 27, 2026
… i18n labels (diegosouzapw#11096) (diegosouzapw#11117) Cherry-picked the value commit (0e91881) onto the current tip, dropping the stale base-red sync commits. Focused tests: pollinations-api-key-required 1/1 plus the whole optional-key suite 142/142 (two legacy assertions in provider-route-schemas flipped to the new key-required contract, commented with the PR). Fixes diegosouzapw#11096 — Pollinations answers 401 anonymously now. Thank you @rqzbeh!
muhamadgalihsaputra
pushed a commit
to niyatna/NiyatnaRoute
that referenced
this pull request
Sep 27, 2026
…ol (diegosouzapw#9827) (diegosouzapw#11194) Validated on the combined batch board over tip 76f9b2f: static gates clean (changelog, file-size 159 frozen, complexity 2621<=2774, cognitive 1181<=1223, dead-code 408<=416), typecheck:core clean, 107 focused tests green. Keyless pollinations 401s no longer poison the noauth pool — key health classification treats the now-required-key provider correctly after diegosouzapw#11117. chatcore-key-health + executor-pollinations green. Fixes diegosouzapw#9827. Thank you @jonlwheat2-gif!
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
3 participants
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.
Fixes #11096.
Summary
pollinationsfromEXPLICIT_OPTIONAL_APIKEY_PROVIDER_IDSinsrc/shared/constants/providers.tsbecause Pollinations no longer supports anonymous API calls and returns 401 Unauthorized without an API key.src/i18n/messages/en.jsonforapiKeyOptionalHintandapiKeyOptionalLabel.tests/unit/pollinations-api-key-required-11096.test.tsverifyingproviderAllowsOptionalApiKey('pollinations')returnsfalse.