feat(loadtesting): advertise tag filter on run-list endpoints - #403
Merged
sourabhd-cbu merged 1 commit intoSep 8, 2026
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Central YAML (base), Organization UI (inherited), Workspace UI (inherited) Review profile: ASSERTIVE Plan: Enterprise Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
sourabhd-cbu
merged commit Sep 8, 2026
7a072c5
into
browserstack:feat/capability-registry
1 check 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
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.
Adds a
tagquery param (and a one-line guidance note) to the three run-list capabilities so the registry advertises run-tag filtering:Without this, bind rejects
?tag=as an unknown query even though the backend supports it — so the filter is unreachable through the MCP. Response-sidetagson run objects needs no declaration (fields pass through); only the query param must be declared.Pairs with the load-testing-backend read-path change that implements the filter (getRunDisplayTags surfacing + findJobIdsByLabels push-down). Follows the merged run-tag write path (#402, runId on updateLoadTest).