Skip to content

fix: clarify AI provider collision warnings (#28549) - #28627

Merged
mtojek merged 1 commit into
release/2.37from
backport/28549-to-2.37
Aug 27, 2026
Merged

fix: clarify AI provider collision warnings (#28549)#28627
mtojek merged 1 commit into
release/2.37from
backport/28549-to-2.37

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Cherry-pick of #28549

Original PR: #28549 — fix: clarify AI provider collision warnings
Merge commit: 56c6144
Requested by: @ssncferreira

AI provider collision warnings were only partially asserted, and the
update coverage did not exercise a provider changing from a distinct
hostname to a colliding hostname.

Assert the complete warning consistently across create, get, list, and
update responses, cover collisions introduced by base URL and
enabled-state updates, and only return the proxy-specific warning when
AI Gateway Proxy is enabled. Clarify that lifecycle status values are
reported by the provider metrics.

Follow-up to #28208.

> [!NOTE]
> Generated by Coder Agents for @ssncferreira.

(cherry picked from commit 56c6144)
@github-actions github-actions Bot added the cherry-pick/v2.37 Cherry-pick PR targeting release/2.37 label Aug 26, 2026
@github-actions
github-actions Bot requested a review from ssncferreira August 26, 2026 10:46
@ssncferreira
ssncferreira requested a review from mtojek August 26, 2026 10:47
@mtojek
mtojek merged commit ccaeafd into release/2.37 Aug 27, 2026
@mtojek
mtojek deleted the backport/28549-to-2.37 branch August 27, 2026 08:30
@github-actions github-actions Bot locked and limited conversation to collaborators Aug 27, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

cherry-pick/v2.37 Cherry-pick PR targeting release/2.37

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants