Bump dorny/paths-filter from 3.0.2 to 4.0.1#2
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Bumps [dorny/paths-filter](https://github.com/dorny/paths-filter) from 3.0.2 to 4.0.1. - [Release notes](https://github.com/dorny/paths-filter/releases) - [Changelog](https://github.com/dorny/paths-filter/blob/master/CHANGELOG.md) - [Commits](dorny/paths-filter@v3.0.2...v4.0.1) --- updated-dependencies: - dependency-name: dorny/paths-filter dependency-version: 4.0.1 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Author
|
Looks like dorny/paths-filter is up-to-date now, so this is no longer needed. |
dependabot
Bot
deleted the
dependabot/github_actions/dorny/paths-filter-4.0.1
branch
tony
added a commit
that referenced
this pull request
May 10, 2026
…s only why: External CSS expert recommendation #2. The previous prefix wrapper rule re-fonted the entire `name (type)` portion to monospace — including parens, brackets, commas, and ellipsis. The expert noted: only the parameter name and type cross-references are truly "code"; structural punctuation around them should stay sans so the syntax-vs-text boundary is clearer. Reduces the optical mass of each row without changing what's actually monospace. what: - .gp-sphinx-field-prefix: change `font-family: var(--font-stack --monospace)` to `font-family: inherit`. The wrapper becomes a presentational container for the prefix text run; its children pick their own font-family. - Add `.gp-sphinx-field-prefix > strong` rule pinning the bold parameter name to monospace — it's the row's primary identifier and reads as code alongside the type. - Inline `<code>` xref children continue to pick up monospace from Furo's `code.literal` rule in gp-furo-theme/.../code.css — unchanged, no new rule needed here. - Trim the docstring on the wrapper rule to reflect the new intent. verification: at 1280 px on the typehints-gp examples page, getComputedStyle('.gp-sphinx-field-prefix').fontFamily returns "IBM Plex Sans" (was "IBM Plex Mono"); strong child returns "IBM Plex Mono"; code.literal child returns "IBM Plex Mono"; the inline span.p (bracket/comma punctuation) returns "IBM Plex Sans".
tony
added a commit
that referenced
this pull request
May 10, 2026
…m name why: External expert refinement #2. Pre-FE5 the row carried two mono treatments: <strong> (param name) in mono bold black, and <code class="xref"> (type chip) in mono regular blue with chip background. Two distinct mono runs in the same row read busier than necessary. Sans-bold for the param name lets it read as a definition term; mono is then cleanly scoped to "code identifier inside chip" — semantic match, single mono treatment per row. what: - Delete `.gp-sphinx-field-prefix > strong { font-family: var( --font-stack--monospace) }`. <strong> now inherits font-family from its .gp-sphinx-field-prefix parent (which is `inherit`, resolves to body sans). The browser's default `<strong> { font-weight: 700 }` keeps the bold weight. - Trim the surrounding comment to reflect the new policy: the prefix wrapper now leaves all family resolution to inheritance; only the inline <code> children pick up monospace (via Furo's code.literal rule, no extra rule on our side). verification: at 1280 px, getComputedStyle('.gp-sphinx-field-prefix > strong').fontFamily returns "IBM Plex Sans" (was "IBM Plex Mono"); fontWeight stays 700. Type chips still render in IBM Plex Mono with chip background (Furo's rule unaffected). If the live preview reads as off (e.g. param names lose their "identifier" feel without mono), revert this single commit; FE4's chip-padding fix and the rest of the round-2 work stand on their own.
tony
added a commit
that referenced
this pull request
May 10, 2026
…s only why: External CSS expert recommendation #2. The previous prefix wrapper rule re-fonted the entire `name (type)` portion to monospace — including parens, brackets, commas, and ellipsis. The expert noted: only the parameter name and type cross-references are truly "code"; structural punctuation around them should stay sans so the syntax-vs-text boundary is clearer. Reduces the optical mass of each row without changing what's actually monospace. what: - .gp-sphinx-field-prefix: change `font-family: var(--font-stack --monospace)` to `font-family: inherit`. The wrapper becomes a presentational container for the prefix text run; its children pick their own font-family. - Add `.gp-sphinx-field-prefix > strong` rule pinning the bold parameter name to monospace — it's the row's primary identifier and reads as code alongside the type. - Inline `<code>` xref children continue to pick up monospace from Furo's `code.literal` rule in gp-furo-theme/.../code.css — unchanged, no new rule needed here. - Trim the docstring on the wrapper rule to reflect the new intent. verification: at 1280 px on the typehints-gp examples page, getComputedStyle('.gp-sphinx-field-prefix').fontFamily returns "IBM Plex Sans" (was "IBM Plex Mono"); strong child returns "IBM Plex Mono"; code.literal child returns "IBM Plex Mono"; the inline span.p (bracket/comma punctuation) returns "IBM Plex Sans".
tony
added a commit
that referenced
this pull request
May 10, 2026
…m name why: External expert refinement #2. Pre-FE5 the row carried two mono treatments: <strong> (param name) in mono bold black, and <code class="xref"> (type chip) in mono regular blue with chip background. Two distinct mono runs in the same row read busier than necessary. Sans-bold for the param name lets it read as a definition term; mono is then cleanly scoped to "code identifier inside chip" — semantic match, single mono treatment per row. what: - Delete `.gp-sphinx-field-prefix > strong { font-family: var( --font-stack--monospace) }`. <strong> now inherits font-family from its .gp-sphinx-field-prefix parent (which is `inherit`, resolves to body sans). The browser's default `<strong> { font-weight: 700 }` keeps the bold weight. - Trim the surrounding comment to reflect the new policy: the prefix wrapper now leaves all family resolution to inheritance; only the inline <code> children pick up monospace (via Furo's code.literal rule, no extra rule on our side). verification: at 1280 px, getComputedStyle('.gp-sphinx-field-prefix > strong').fontFamily returns "IBM Plex Sans" (was "IBM Plex Mono"); fontWeight stays 700. Type chips still render in IBM Plex Mono with chip background (Furo's rule unaffected). If the live preview reads as off (e.g. param names lose their "identifier" feel without mono), revert this single commit; FE4's chip-padding fix and the rest of the round-2 work stand on their own.
tony
added a commit
that referenced
this pull request
May 10, 2026
…s only why: External CSS expert recommendation #2. The previous prefix wrapper rule re-fonted the entire `name (type)` portion to monospace — including parens, brackets, commas, and ellipsis. The expert noted: only the parameter name and type cross-references are truly "code"; structural punctuation around them should stay sans so the syntax-vs-text boundary is clearer. Reduces the optical mass of each row without changing what's actually monospace. what: - .gp-sphinx-field-prefix: change `font-family: var(--font-stack --monospace)` to `font-family: inherit`. The wrapper becomes a presentational container for the prefix text run; its children pick their own font-family. - Add `.gp-sphinx-field-prefix > strong` rule pinning the bold parameter name to monospace — it's the row's primary identifier and reads as code alongside the type. - Inline `<code>` xref children continue to pick up monospace from Furo's `code.literal` rule in gp-furo-theme/.../code.css — unchanged, no new rule needed here. - Trim the docstring on the wrapper rule to reflect the new intent. verification: at 1280 px on the typehints-gp examples page, getComputedStyle('.gp-sphinx-field-prefix').fontFamily returns "IBM Plex Sans" (was "IBM Plex Mono"); strong child returns "IBM Plex Mono"; code.literal child returns "IBM Plex Mono"; the inline span.p (bracket/comma punctuation) returns "IBM Plex Sans".
tony
added a commit
that referenced
this pull request
May 10, 2026
…m name why: External expert refinement #2. Pre-FE5 the row carried two mono treatments: <strong> (param name) in mono bold black, and <code class="xref"> (type chip) in mono regular blue with chip background. Two distinct mono runs in the same row read busier than necessary. Sans-bold for the param name lets it read as a definition term; mono is then cleanly scoped to "code identifier inside chip" — semantic match, single mono treatment per row. what: - Delete `.gp-sphinx-field-prefix > strong { font-family: var( --font-stack--monospace) }`. <strong> now inherits font-family from its .gp-sphinx-field-prefix parent (which is `inherit`, resolves to body sans). The browser's default `<strong> { font-weight: 700 }` keeps the bold weight. - Trim the surrounding comment to reflect the new policy: the prefix wrapper now leaves all family resolution to inheritance; only the inline <code> children pick up monospace (via Furo's code.literal rule, no extra rule on our side). verification: at 1280 px, getComputedStyle('.gp-sphinx-field-prefix > strong').fontFamily returns "IBM Plex Sans" (was "IBM Plex Mono"); fontWeight stays 700. Type chips still render in IBM Plex Mono with chip background (Furo's rule unaffected). If the live preview reads as off (e.g. param names lose their "identifier" feel without mono), revert this single commit; FE4's chip-padding fix and the rest of the round-2 work stand on their own.
tony
added a commit
that referenced
this pull request
May 10, 2026
…s only why: External CSS expert recommendation #2. The previous prefix wrapper rule re-fonted the entire `name (type)` portion to monospace — including parens, brackets, commas, and ellipsis. The expert noted: only the parameter name and type cross-references are truly "code"; structural punctuation around them should stay sans so the syntax-vs-text boundary is clearer. Reduces the optical mass of each row without changing what's actually monospace. what: - .gp-sphinx-field-prefix: change `font-family: var(--font-stack --monospace)` to `font-family: inherit`. The wrapper becomes a presentational container for the prefix text run; its children pick their own font-family. - Add `.gp-sphinx-field-prefix > strong` rule pinning the bold parameter name to monospace — it's the row's primary identifier and reads as code alongside the type. - Inline `<code>` xref children continue to pick up monospace from Furo's `code.literal` rule in gp-furo-theme/.../code.css — unchanged, no new rule needed here. - Trim the docstring on the wrapper rule to reflect the new intent. verification: at 1280 px on the typehints-gp examples page, getComputedStyle('.gp-sphinx-field-prefix').fontFamily returns "IBM Plex Sans" (was "IBM Plex Mono"); strong child returns "IBM Plex Mono"; code.literal child returns "IBM Plex Mono"; the inline span.p (bracket/comma punctuation) returns "IBM Plex Sans".
tony
added a commit
that referenced
this pull request
May 10, 2026
…m name why: External expert refinement #2. Pre-FE5 the row carried two mono treatments: <strong> (param name) in mono bold black, and <code class="xref"> (type chip) in mono regular blue with chip background. Two distinct mono runs in the same row read busier than necessary. Sans-bold for the param name lets it read as a definition term; mono is then cleanly scoped to "code identifier inside chip" — semantic match, single mono treatment per row. what: - Delete `.gp-sphinx-field-prefix > strong { font-family: var( --font-stack--monospace) }`. <strong> now inherits font-family from its .gp-sphinx-field-prefix parent (which is `inherit`, resolves to body sans). The browser's default `<strong> { font-weight: 700 }` keeps the bold weight. - Trim the surrounding comment to reflect the new policy: the prefix wrapper now leaves all family resolution to inheritance; only the inline <code> children pick up monospace (via Furo's code.literal rule, no extra rule on our side). verification: at 1280 px, getComputedStyle('.gp-sphinx-field-prefix > strong').fontFamily returns "IBM Plex Sans" (was "IBM Plex Mono"); fontWeight stays 700. Type chips still render in IBM Plex Mono with chip background (Furo's rule unaffected). If the live preview reads as off (e.g. param names lose their "identifier" feel without mono), revert this single commit; FE4's chip-padding fix and the rest of the round-2 work stand on their own.
tony
added a commit
that referenced
this pull request
May 11, 2026
…s only why: External CSS expert recommendation #2. The previous prefix wrapper rule re-fonted the entire `name (type)` portion to monospace — including parens, brackets, commas, and ellipsis. The expert noted: only the parameter name and type cross-references are truly "code"; structural punctuation around them should stay sans so the syntax-vs-text boundary is clearer. Reduces the optical mass of each row without changing what's actually monospace. what: - .gp-sphinx-field-prefix: change `font-family: var(--font-stack --monospace)` to `font-family: inherit`. The wrapper becomes a presentational container for the prefix text run; its children pick their own font-family. - Add `.gp-sphinx-field-prefix > strong` rule pinning the bold parameter name to monospace — it's the row's primary identifier and reads as code alongside the type. - Inline `<code>` xref children continue to pick up monospace from Furo's `code.literal` rule in gp-furo-theme/.../code.css — unchanged, no new rule needed here. - Trim the docstring on the wrapper rule to reflect the new intent. verification: at 1280 px on the typehints-gp examples page, getComputedStyle('.gp-sphinx-field-prefix').fontFamily returns "IBM Plex Sans" (was "IBM Plex Mono"); strong child returns "IBM Plex Mono"; code.literal child returns "IBM Plex Mono"; the inline span.p (bracket/comma punctuation) returns "IBM Plex Sans".
tony
added a commit
that referenced
this pull request
May 11, 2026
…m name why: External expert refinement #2. Pre-FE5 the row carried two mono treatments: <strong> (param name) in mono bold black, and <code class="xref"> (type chip) in mono regular blue with chip background. Two distinct mono runs in the same row read busier than necessary. Sans-bold for the param name lets it read as a definition term; mono is then cleanly scoped to "code identifier inside chip" — semantic match, single mono treatment per row. what: - Delete `.gp-sphinx-field-prefix > strong { font-family: var( --font-stack--monospace) }`. <strong> now inherits font-family from its .gp-sphinx-field-prefix parent (which is `inherit`, resolves to body sans). The browser's default `<strong> { font-weight: 700 }` keeps the bold weight. - Trim the surrounding comment to reflect the new policy: the prefix wrapper now leaves all family resolution to inheritance; only the inline <code> children pick up monospace (via Furo's code.literal rule, no extra rule on our side). verification: at 1280 px, getComputedStyle('.gp-sphinx-field-prefix > strong').fontFamily returns "IBM Plex Sans" (was "IBM Plex Mono"); fontWeight stays 700. Type chips still render in IBM Plex Mono with chip background (Furo's rule unaffected). If the live preview reads as off (e.g. param names lose their "identifier" feel without mono), revert this single commit; FE4's chip-padding fix and the rest of the round-2 work stand on their own.
tony
added a commit
that referenced
this pull request
May 11, 2026
…s only why: External CSS expert recommendation #2. The previous prefix wrapper rule re-fonted the entire `name (type)` portion to monospace — including parens, brackets, commas, and ellipsis. The expert noted: only the parameter name and type cross-references are truly "code"; structural punctuation around them should stay sans so the syntax-vs-text boundary is clearer. Reduces the optical mass of each row without changing what's actually monospace. what: - .gp-sphinx-field-prefix: change `font-family: var(--font-stack --monospace)` to `font-family: inherit`. The wrapper becomes a presentational container for the prefix text run; its children pick their own font-family. - Add `.gp-sphinx-field-prefix > strong` rule pinning the bold parameter name to monospace — it's the row's primary identifier and reads as code alongside the type. - Inline `<code>` xref children continue to pick up monospace from Furo's `code.literal` rule in gp-furo-theme/.../code.css — unchanged, no new rule needed here. - Trim the docstring on the wrapper rule to reflect the new intent. verification: at 1280 px on the typehints-gp examples page, getComputedStyle('.gp-sphinx-field-prefix').fontFamily returns "IBM Plex Sans" (was "IBM Plex Mono"); strong child returns "IBM Plex Mono"; code.literal child returns "IBM Plex Mono"; the inline span.p (bracket/comma punctuation) returns "IBM Plex Sans".
tony
added a commit
that referenced
this pull request
May 11, 2026
…m name why: External expert refinement #2. Pre-FE5 the row carried two mono treatments: <strong> (param name) in mono bold black, and <code class="xref"> (type chip) in mono regular blue with chip background. Two distinct mono runs in the same row read busier than necessary. Sans-bold for the param name lets it read as a definition term; mono is then cleanly scoped to "code identifier inside chip" — semantic match, single mono treatment per row. what: - Delete `.gp-sphinx-field-prefix > strong { font-family: var( --font-stack--monospace) }`. <strong> now inherits font-family from its .gp-sphinx-field-prefix parent (which is `inherit`, resolves to body sans). The browser's default `<strong> { font-weight: 700 }` keeps the bold weight. - Trim the surrounding comment to reflect the new policy: the prefix wrapper now leaves all family resolution to inheritance; only the inline <code> children pick up monospace (via Furo's code.literal rule, no extra rule on our side). verification: at 1280 px, getComputedStyle('.gp-sphinx-field-prefix > strong').fontFamily returns "IBM Plex Sans" (was "IBM Plex Mono"); fontWeight stays 700. Type chips still render in IBM Plex Mono with chip background (Furo's rule unaffected). If the live preview reads as off (e.g. param names lose their "identifier" feel without mono), revert this single commit; FE4's chip-padding fix and the rest of the round-2 work stand on their own.
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 dorny/paths-filter from 3.0.2 to 4.0.1.
Release notes
Sourced from dorny/paths-filter's releases.
Changelog
Sourced from dorny/paths-filter's changelog.
Commits
fbd0ab8feat: add merge_group event supportefb1da7feat: add dist/ freshness check to PR workflowd8f7b06Merge pull request #302 from dorny/issue-299addbc14Update README for v49d7afb8Update CHANGELOG for v4.0.0782470cMerge branch 'releases/v3'd1c1ffeUpdate CHANGELOG for v3.0.3ce10459Merge pull request #294 from saschabratton/master5f40380feat: update action runtime to node24668c092Merge pull request #279 from wardpeet/patch-1Dependabot 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 show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@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)