Repository navigation
docs(changelog): record keyless Bing search tail - #39
Merged
h3c-hexin merged 2 commits intoSep 10, 2026
Merged
Conversation
|
Thanks @asto18089 for taking the time to contribute. This repository is observing a maintainer-managed PR intake gate in dry-run mode, so this pull request is staying open. This note helps maintainers prepare the allowlist before any enforcement is considered. Please read |
This was referenced Sep 2, 2026
h3c-hexin
force-pushed
the
pinvou3-clean
branch
from
September 9, 2026 02:58
f853f8f to
ff299f9
Compare
The copy half of this PR - the web_search module doc, the tool description, and the all-backends-down provider list - was absorbed upstream in evolved, tested form by "fix(search): preserve reachable API fallback" and "fix(search): restore actionable backend guidance", which route API-backed providers directly to the keyless Bing tail and name the keyed providers plus keyless routes in the configuration hint. What stays missing on pinvou3-clean is the CHANGELOG record for that switch: [Unreleased] had no entry for it. Adapt the original entry to the current chain (keyless Firecrawl default, direct keyless Bing tail, keyed-provider configuration hint) and place it under [Unreleased]. Signed-off-by: asto18089 <asto18089@126.com>
asto18089
force-pushed
the
fix/web-search-chain-tail-docs
branch
from
September 9, 2026 10:58
05d7950 to
b1d4f20
Compare
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
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.
Context
No-Issue: the CodeWhale repo tracks no issues; this batch is tracked as Pinvou/pinvou-agent#377 (r12 review leftovers).
Rebased onto
pinvou3-clean@1fafee7e2(post-v0.9.12). During the rebase, the three copy/diagnostics fixes this PR originally carried turned out to be already absorbed upstream in evolved, tested form, so the branch now carries only the piece still missing there.Changes
[Unreleased] / Fixedentry for the keyless chain-tail switch, adapted to the current chain: API-backed[search]providers degrade directly to the keyless Bing tail without a DuckDuckGo hop, the all-backends-down guidance names every keyed provider (tavily, bocha, metaso, baidu, volcengine, sofya) plus the keyless routes (firecrawl, bing), and theweb_searchtool description no longer claims a DuckDuckGo hop.Where the original items went
crates/tui/src/tools/web_search.rs): upstream rewrote both inff299f94b("fix(search): preserve reachable API fallback") with the same meaning against the newer chain — "visibly degrade directly to keyless Bing", keyless Firecrawl default — pinned byforkguard_api_provider_chain_tail_is_bing.crates/tui/src/tools/web/backend.rs): superseded by1fafee7e2("fix(search): restore actionable backend guidance"), whoseSEARCH_BACKEND_CONFIGURATION_HINTadds sofya and splits keyed from keyless guidance. SearXNG intentionally sits on the keyless/base_url side there; if reviewers want it named explicitly, that is a one-line follow-up on top of1fafee7e2.Not included
The branch no longer carries the fork-lineage commits that rode along before; they stay queued via their own PRs (#31, #34, #37, #38, #41, #43, #47).
Verification
pinvou3-cleanis CHANGELOG.md only (+12 lines): no behavior or build-surface change; the upstream CI gates run on this PR.forkguard_api_provider_chain_tail_is_bingand the configuration-hint tests added in1fafee7e2.Signed-off-by: asto18089 asto18089@126.com