chore(deps): bump browserslist from 4.21.7 to 4.21.8#1382
Merged
Conversation
Bumps [browserslist](https://github.com/browserslist/browserslist) from 4.21.7 to 4.21.8. - [Changelog](https://github.com/browserslist/browserslist/blob/main/CHANGELOG.md) - [Commits](browserslist/browserslist@4.21.7...4.21.8) --- updated-dependencies: - dependency-name: browserslist dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
remyduthu
added a commit
that referenced
this pull request
May 22, 2026
Mergify CLI #1382 shipped `mergify tests show` so developers and AI coding agents (Claude Code, Cursor, …) can decide whether a failing test is a real regression or known flakiness without parsing dashboards. Until now the command was undiscoverable from the docs site — agents that ran it from a skill could not link users to a reference, and developers had no entry point besides `--help`. Adds a dedicated `/test-insights/cli` guide covering single- and multi- test lookups, glob patterns, pipeline/job filters, JSON output, and the 0/1/6 exit-code contract (clap reserves `2`). A second half walks through agent recipes for routing failures to retry vs. fix vs. ignore based on exit code alone, plus a Claude Code skill snippet and Cursor project rule. The two backing endpoints (`GET …/search/tests`, `GET …/tests/{test_id}`) are auto-generated into the API reference from the engine's OpenAPI schema, so the guide links to `/api/test-insights` rather than duplicating the schema. `/tests/{test_id}/stats/{stat}` stays out of scope: it is `include_in_schema=False` server-side and not used by the CLI. The guide intentionally documents the shipped surface, which diverged from the MRGFY-7167 spec during MRGFY-7166 implementation: the command is `mergify tests show` (not `mergify ci tests show`), there is no `--quiet` flag, exit codes are `0/1/6` (not `0/1/2`), and the search endpoint is `GET` with repeated query params (not `POST` with a JSON body). Documenting reality beats documenting the plan. Fixes: MRGFY-7167 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Change-Id: I54b1908accda0ad2d2bf538af10e5960d76ad9b2
remyduthu
added a commit
that referenced
this pull request
May 22, 2026
Mergify CLI #1382 shipped `mergify tests show` so developers and AI coding agents (Claude Code, Cursor, …) can decide whether a failing test is a real regression or known flakiness without parsing dashboards. Until now the command was undiscoverable from the docs site — agents that ran it from a skill could not link users to a reference, and developers had no entry point besides `--help`. Adds a dedicated `/test-insights/cli` guide covering single- and multi- test lookups, glob patterns, pipeline/job filters, JSON output, and the 0/1/6 exit-code contract (clap reserves `2`). A second half walks through agent recipes for routing failures to retry vs. fix vs. ignore based on exit code alone, plus a Claude Code skill snippet and Cursor project rule. The two backing endpoints (`GET …/search/tests`, `GET …/tests/{test_id}`) are auto-generated into the API reference from the engine's OpenAPI schema, so the guide links to `/api/test-insights` rather than duplicating the schema. `/tests/{test_id}/stats/{stat}` stays out of scope: it is `include_in_schema=False` server-side and not used by the CLI. The guide intentionally documents the shipped surface, which diverged from the MRGFY-7167 spec during MRGFY-7166 implementation: the command is `mergify tests show` (not `mergify ci tests show`), there is no `--quiet` flag, exit codes are `0/1/6` (not `0/1/2`), and the search endpoint is `GET` with repeated query params (not `POST` with a JSON body). Documenting reality beats documenting the plan. Fixes: MRGFY-7167 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Change-Id: I54b1908accda0ad2d2bf538af10e5960d76ad9b2
remyduthu
added a commit
that referenced
this pull request
May 22, 2026
Mergify CLI #1382 shipped `mergify tests show` so developers and AI coding agents (Claude Code, Cursor, …) can decide whether a failing test is a real regression or known flakiness without parsing dashboards. Until now the command was undiscoverable from the docs site — agents that ran it from a skill could not link users to a reference, and developers had no entry point besides `--help`. Adds a dedicated `/test-insights/cli` guide covering single- and multi- test lookups, glob patterns, pipeline/job filters, JSON output, and the 0/1/6 exit-code contract (clap reserves `2`). A second half walks through agent recipes for routing failures to retry vs. fix vs. ignore based on exit code alone, plus a Claude Code skill snippet and Cursor project rule. The two backing endpoints (`GET …/search/tests`, `GET …/tests/{test_id}`) are auto-generated into the API reference from the engine's OpenAPI schema, so the guide links to `/api/test-insights` rather than duplicating the schema. `/tests/{test_id}/stats/{stat}` stays out of scope: it is `include_in_schema=False` server-side and not used by the CLI. The guide intentionally documents the shipped surface, which diverged from the MRGFY-7167 spec during MRGFY-7166 implementation: the command is `mergify tests show` (not `mergify ci tests show`), there is no `--quiet` flag, exit codes are `0/1/6` (not `0/1/2`), and the search endpoint is `GET` with repeated query params (not `POST` with a JSON body). Documenting reality beats documenting the plan. Fixes: MRGFY-7167 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Change-Id: I54b1908accda0ad2d2bf538af10e5960d76ad9b2
remyduthu
added a commit
that referenced
this pull request
May 22, 2026
Mergify CLI #1382 shipped `mergify tests show` so developers and AI coding agents (Claude Code, Cursor, …) can decide whether a failing test is a real regression or known flakiness without parsing dashboards. Until now the command was undiscoverable from the docs site — agents that ran it from a skill could not link users to a reference, and developers had no entry point besides `--help`. Adds a dedicated `/test-insights/cli` guide covering single- and multi- test lookups, glob patterns, pipeline/job filters, JSON output, and the 0/1/6 exit-code contract (clap reserves `2`). A second half walks through agent recipes for routing failures to retry vs. fix vs. ignore based on exit code alone, plus a Claude Code skill snippet and Cursor project rule. The two backing endpoints (`GET …/search/tests`, `GET …/tests/{test_id}`) are auto-generated into the API reference from the engine's OpenAPI schema, so the guide links to `/api/test-insights` rather than duplicating the schema. `/tests/{test_id}/stats/{stat}` stays out of scope: it is `include_in_schema=False` server-side and not used by the CLI. The guide intentionally documents the shipped surface, which diverged from the MRGFY-7167 spec during MRGFY-7166 implementation: the command is `mergify tests show` (not `mergify ci tests show`), there is no `--quiet` flag, exit codes are `0/1/6` (not `0/1/2`), and the search endpoint is `GET` with repeated query params (not `POST` with a JSON body). Documenting reality beats documenting the plan. Fixes: MRGFY-7167 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Change-Id: I54b1908accda0ad2d2bf538af10e5960d76ad9b2
mergify Bot
pushed a commit
that referenced
this pull request
May 22, 2026
Mergify CLI #1382 shipped `mergify tests show` so developers and AI coding agents (Claude Code, Cursor, …) can decide whether a failing test is a real regression or known flakiness without parsing dashboards. Until now the command was undiscoverable from the docs site — agents that ran it from a skill could not link users to a reference, and developers had no entry point besides `--help`. Adds a dedicated `/test-insights/cli` guide covering single- and multi- test lookups, glob patterns, pipeline/job filters, JSON output, and the 0/1/6 exit-code contract (clap reserves `2`). A second half walks through agent recipes for routing failures to retry vs. fix vs. ignore based on exit code alone, plus a Claude Code skill snippet and Cursor project rule. The two backing endpoints (`GET …/search/tests`, `GET …/tests/{test_id}`) are auto-generated into the API reference from the engine's OpenAPI schema, so the guide links to `/api/test-insights` rather than duplicating the schema. `/tests/{test_id}/stats/{stat}` stays out of scope: it is `include_in_schema=False` server-side and not used by the CLI. The guide intentionally documents the shipped surface, which diverged from the MRGFY-7167 spec during MRGFY-7166 implementation: the command is `mergify tests show` (not `mergify ci tests show`), there is no `--quiet` flag, exit codes are `0/1/6` (not `0/1/2`), and the search endpoint is `GET` with repeated query params (not `POST` with a JSON body). Documenting reality beats documenting the plan. Fixes: MRGFY-7167 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Bumps browserslist from 4.21.7 to 4.21.8.
Changelog
Sourced from browserslist's changelog.
Commits
d05ffabRelease 4.21.8 version510ff6bUpdate dependencies640a7abFix feature support queries with mobileToDesktop (#767)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)