Bump codecov/codecov-action from 5 to 6#4
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Bumps [codecov/codecov-action](https://github.com/codecov/codecov-action) from 5 to 6. - [Release notes](https://github.com/codecov/codecov-action/releases) - [Changelog](https://github.com/codecov/codecov-action/blob/main/CHANGELOG.md) - [Commits](codecov/codecov-action@v5...v6) --- updated-dependencies: - dependency-name: codecov/codecov-action dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Member
|
Manually updated in 8991684. Closing Dependabot PR. |
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
Bot
deleted the
dependabot/github_actions/codecov/codecov-action-6
branch
tony
added a commit
that referenced
this pull request
May 10, 2026
…code; pin to 0.8125rem why: External CSS expert recommendation #4. The previous neutralisation rule (`.field-list code.literal { background: transparent; padding: 0; border: none; font-size: inherit }`) existed to stop Furo's percentage chip rule from compounding to ~10.5 px when the field body was pinned to 13 px. Now that field-body is back at metadata-size (14 px) — see commit FE1 — a 13 px chip with light-gray background and padding **is** the right size: it acts as a cognitive container around each type identifier without overwhelming the row. what: - Delete the chip-strip block (background/padding/border/font-size all reset to inherit). Furo's `code.literal { background: var(...); padding: 0.1em 0.2em; border-radius: 0.2em; font-size: 81.25% }` rule now fires unmodified for inline code in field-list rows. - Add a single-line size pin: `.field-list code.literal { font-size: 0.8125rem }`. This overrides Furo's percentage size with a root- relative rem so chips render at ≈13 px regardless of the row's metadata-size parent. Without the pin, 14 px parent × 81.25 % = ~11.4 px (too small). - Keep `.default_value code.literal { font-size: inherit; ...}` — signature default-value surface, different cascade, unaffected. verification: at 1280 px on the typehints-gp examples page, getComputedStyle('dl.field-list code.literal') returns fontSize 13 px, fontFamily "IBM Plex Mono", backgroundColor rgb(248, 249, 251) (Furo's --color-background-secondary), borderTopLeftRadius 2.6 px, paddingTop 1.3 px, paddingLeft 2.6 px (Furo's 0.1em 0.2em).
tony
added a commit
that referenced
this pull request
May 10, 2026
…code; pin to 0.8125rem why: External CSS expert recommendation #4. The previous neutralisation rule (`.field-list code.literal { background: transparent; padding: 0; border: none; font-size: inherit }`) existed to stop Furo's percentage chip rule from compounding to ~10.5 px when the field body was pinned to 13 px. Now that field-body is back at metadata-size (14 px) — see commit FE1 — a 13 px chip with light-gray background and padding **is** the right size: it acts as a cognitive container around each type identifier without overwhelming the row. what: - Delete the chip-strip block (background/padding/border/font-size all reset to inherit). Furo's `code.literal { background: var(...); padding: 0.1em 0.2em; border-radius: 0.2em; font-size: 81.25% }` rule now fires unmodified for inline code in field-list rows. - Add a single-line size pin: `.field-list code.literal { font-size: 0.8125rem }`. This overrides Furo's percentage size with a root- relative rem so chips render at ≈13 px regardless of the row's metadata-size parent. Without the pin, 14 px parent × 81.25 % = ~11.4 px (too small). - Keep `.default_value code.literal { font-size: inherit; ...}` — signature default-value surface, different cascade, unaffected. verification: at 1280 px on the typehints-gp examples page, getComputedStyle('dl.field-list code.literal') returns fontSize 13 px, fontFamily "IBM Plex Mono", backgroundColor rgb(248, 249, 251) (Furo's --color-background-secondary), borderTopLeftRadius 2.6 px, paddingTop 1.3 px, paddingLeft 2.6 px (Furo's 0.1em 0.2em).
tony
added a commit
that referenced
this pull request
May 10, 2026
…code; pin to 0.8125rem why: External CSS expert recommendation #4. The previous neutralisation rule (`.field-list code.literal { background: transparent; padding: 0; border: none; font-size: inherit }`) existed to stop Furo's percentage chip rule from compounding to ~10.5 px when the field body was pinned to 13 px. Now that field-body is back at metadata-size (14 px) — see commit FE1 — a 13 px chip with light-gray background and padding **is** the right size: it acts as a cognitive container around each type identifier without overwhelming the row. what: - Delete the chip-strip block (background/padding/border/font-size all reset to inherit). Furo's `code.literal { background: var(...); padding: 0.1em 0.2em; border-radius: 0.2em; font-size: 81.25% }` rule now fires unmodified for inline code in field-list rows. - Add a single-line size pin: `.field-list code.literal { font-size: 0.8125rem }`. This overrides Furo's percentage size with a root- relative rem so chips render at ≈13 px regardless of the row's metadata-size parent. Without the pin, 14 px parent × 81.25 % = ~11.4 px (too small). - Keep `.default_value code.literal { font-size: inherit; ...}` — signature default-value surface, different cascade, unaffected. verification: at 1280 px on the typehints-gp examples page, getComputedStyle('dl.field-list code.literal') returns fontSize 13 px, fontFamily "IBM Plex Mono", backgroundColor rgb(248, 249, 251) (Furo's --color-background-secondary), borderTopLeftRadius 2.6 px, paddingTop 1.3 px, paddingLeft 2.6 px (Furo's 0.1em 0.2em).
tony
added a commit
that referenced
this pull request
May 10, 2026
…code; pin to 0.8125rem why: External CSS expert recommendation #4. The previous neutralisation rule (`.field-list code.literal { background: transparent; padding: 0; border: none; font-size: inherit }`) existed to stop Furo's percentage chip rule from compounding to ~10.5 px when the field body was pinned to 13 px. Now that field-body is back at metadata-size (14 px) — see commit FE1 — a 13 px chip with light-gray background and padding **is** the right size: it acts as a cognitive container around each type identifier without overwhelming the row. what: - Delete the chip-strip block (background/padding/border/font-size all reset to inherit). Furo's `code.literal { background: var(...); padding: 0.1em 0.2em; border-radius: 0.2em; font-size: 81.25% }` rule now fires unmodified for inline code in field-list rows. - Add a single-line size pin: `.field-list code.literal { font-size: 0.8125rem }`. This overrides Furo's percentage size with a root- relative rem so chips render at ≈13 px regardless of the row's metadata-size parent. Without the pin, 14 px parent × 81.25 % = ~11.4 px (too small). - Keep `.default_value code.literal { font-size: inherit; ...}` — signature default-value surface, different cascade, unaffected. verification: at 1280 px on the typehints-gp examples page, getComputedStyle('dl.field-list code.literal') returns fontSize 13 px, fontFamily "IBM Plex Mono", backgroundColor rgb(248, 249, 251) (Furo's --color-background-secondary), borderTopLeftRadius 2.6 px, paddingTop 1.3 px, paddingLeft 2.6 px (Furo's 0.1em 0.2em).
tony
added a commit
that referenced
this pull request
May 11, 2026
…code; pin to 0.8125rem why: External CSS expert recommendation #4. The previous neutralisation rule (`.field-list code.literal { background: transparent; padding: 0; border: none; font-size: inherit }`) existed to stop Furo's percentage chip rule from compounding to ~10.5 px when the field body was pinned to 13 px. Now that field-body is back at metadata-size (14 px) — see commit FE1 — a 13 px chip with light-gray background and padding **is** the right size: it acts as a cognitive container around each type identifier without overwhelming the row. what: - Delete the chip-strip block (background/padding/border/font-size all reset to inherit). Furo's `code.literal { background: var(...); padding: 0.1em 0.2em; border-radius: 0.2em; font-size: 81.25% }` rule now fires unmodified for inline code in field-list rows. - Add a single-line size pin: `.field-list code.literal { font-size: 0.8125rem }`. This overrides Furo's percentage size with a root- relative rem so chips render at ≈13 px regardless of the row's metadata-size parent. Without the pin, 14 px parent × 81.25 % = ~11.4 px (too small). - Keep `.default_value code.literal { font-size: inherit; ...}` — signature default-value surface, different cascade, unaffected. verification: at 1280 px on the typehints-gp examples page, getComputedStyle('dl.field-list code.literal') returns fontSize 13 px, fontFamily "IBM Plex Mono", backgroundColor rgb(248, 249, 251) (Furo's --color-background-secondary), borderTopLeftRadius 2.6 px, paddingTop 1.3 px, paddingLeft 2.6 px (Furo's 0.1em 0.2em).
tony
added a commit
that referenced
this pull request
May 11, 2026
…code; pin to 0.8125rem why: External CSS expert recommendation #4. The previous neutralisation rule (`.field-list code.literal { background: transparent; padding: 0; border: none; font-size: inherit }`) existed to stop Furo's percentage chip rule from compounding to ~10.5 px when the field body was pinned to 13 px. Now that field-body is back at metadata-size (14 px) — see commit FE1 — a 13 px chip with light-gray background and padding **is** the right size: it acts as a cognitive container around each type identifier without overwhelming the row. what: - Delete the chip-strip block (background/padding/border/font-size all reset to inherit). Furo's `code.literal { background: var(...); padding: 0.1em 0.2em; border-radius: 0.2em; font-size: 81.25% }` rule now fires unmodified for inline code in field-list rows. - Add a single-line size pin: `.field-list code.literal { font-size: 0.8125rem }`. This overrides Furo's percentage size with a root- relative rem so chips render at ≈13 px regardless of the row's metadata-size parent. Without the pin, 14 px parent × 81.25 % = ~11.4 px (too small). - Keep `.default_value code.literal { font-size: inherit; ...}` — signature default-value surface, different cascade, unaffected. verification: at 1280 px on the typehints-gp examples page, getComputedStyle('dl.field-list code.literal') returns fontSize 13 px, fontFamily "IBM Plex Mono", backgroundColor rgb(248, 249, 251) (Furo's --color-background-secondary), borderTopLeftRadius 2.6 px, paddingTop 1.3 px, paddingLeft 2.6 px (Furo's 0.1em 0.2em).
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
1 participant
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 codecov/codecov-action from 5 to 6.
Release notes
Sourced from codecov/codecov-action's releases.
... (truncated)
Changelog
Sourced from codecov/codecov-action's changelog.
... (truncated)
Commits
57e3a13Th/6.0.0 (#1928)f67d33dRevert "Revert "build(deps): bump actions/github-script from 7.0.1 to 8.0.0""...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 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)