Repository navigation
fix(combo): keep declared priority order ahead of session stickiness - #15458
Merged
diegosouzapw merged 2 commits intoOct 6, 2026
Merged
diegosouzapw merged 2 commits into
diegosouzapw merged 2 commits into
Conversation
skygunner
force-pushed
the
fix/15241-priority-order-vs-stickiness
branch
from
October 6, 2026 16:35
53200e7 to
ff7f70c
Compare
diegosouzapw
merged commit Oct 6, 2026
3cd2d6f
into
diegosouzapw:release/v3.8.52
44 of 51 checks passed
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
2 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 #15241
A successful mid-list target can currently be promoted to runtime try-slot #1 for the session-stickiness TTL even when a
prioritycombo still declares another model first. That makes the saved failover order and the effective order diverge.Add an opt-in
respectDeclaredOrdermode to session stickiness and use it only forprioritytarget resolution. The existing stickiness health, saturation, quota, and binding-hygiene checks still run; only mid-list promotion is suppressed for priority. Other strategies keep their existing behavior.The scope intentionally follows the maintainer's issue triage comment and does not change
fill-firstor other strategies.Validation:
npm run typecheck:corenpm run lint