Skip to content

chore(deps): bump pento/lcov-coverage-check from 3.1.0 to 3.1.1#54

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/pento/lcov-coverage-check-3.1.1
Open

chore(deps): bump pento/lcov-coverage-check from 3.1.0 to 3.1.1#54
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/pento/lcov-coverage-check-3.1.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 22, 2026

Copy link
Copy Markdown

Bumps pento/lcov-coverage-check from 3.1.0 to 3.1.1.

Release notes

Sourced from pento/lcov-coverage-check's releases.

The One That Got Away

Fix: Baseline retrieval pages back through default-branch runs

The action found the baseline by inspecting only the single most recent successful default-branch run for the lcov-baseline artifact. But a successful run doesn't guarantee a baseline — the coverage job is often conditional (path filters, matrix skips, flaky reruns), so the latest run can complete without one while an older run still holds a perfectly valid baseline.

When that happened, the action silently fell back to summary-only mode: ratcheting wasn't enforced (passed=true hardcoded) and no PR comparison comment was posted. Coverage could regress behind a green check, intermittently, depending only on what the most recent default-branch commit happened to touch.

Retrieval now pages back through recent successful default-branch runs (newest first) and uses the first that still holds a non-expired lcov-baseline[-<label>] artifact, only falling back to summary-only mode when none of the inspected runs has one. Pagination follows the Link: rel="next" header (per_page=100, 50-page cap). (#15)

Also

  • Hardened the per-run artifact query so a transient failure (or malformed response) for one run skips that run and keeps paging, instead of aborting the whole search.
  • mktemp calls now use a ${TMPDIR:-/tmp}/… template, matching the rest of the codebase (portable; the previous bare mktemp -d ignored $TMPDIR on macOS).

No workflow changes needed. Existing setups pick up the fix automatically.

Commits

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [pento/lcov-coverage-check](https://github.com/pento/lcov-coverage-check) from 3.1.0 to 3.1.1.
- [Release notes](https://github.com/pento/lcov-coverage-check/releases)
- [Commits](pento/lcov-coverage-check@972428b...d462675)

---
updated-dependencies:
- dependency-name: pento/lcov-coverage-check
  dependency-version: 3.1.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added automerge dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Jun 22, 2026
@dependabot dependabot Bot requested a review from BigMichi1 as a code owner June 22, 2026 04:19
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code automerge labels Jun 22, 2026
@github-actions

Copy link
Copy Markdown

❌ Coverage Report

Metric Value
Current coverage 71.45% (1619/2266)
Baseline coverage 71.49% (1620/2266)
Result FAIL

Failures

  • Overall coverage decreased: 71.45% < 71.49%

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automerge dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants