chore(deps): bump fgrosse/go-coverage-report from 1.4.0 to 1.5.0

[dependabot]

Bumps fgrosse/go-coverage-report from 1.4.0 to 1.5.0.

Release notes

Sourced from fgrosse/go-coverage-report's releases.

v1.5.0

• If the base commit of the pull request has no usable baseline run (e.g. because it failed, is still running or its artifact expired), the action now uses the nearest commit in the first-parent history of the base commit with a usable run instead of the latest run on the target branch. The runs of each commit are filtered client-side, since the filtered workflow runs API can return stale results, and further candidates are tried if a coverage artifact cannot be downloaded or does not fgrosse/go-coverage-report#113
• Add baseline-search-depth and baseline-max-downloads inputs to configure how far the action searches for a baseline fgrosse/go-coverage-report#113
• fgrosse/go-coverage-report#13
• Behavior change: By default, the baseline coverage is now taken from the latest successful run for the base commit of the pull request (new baseline-sha input, defaults to github.event.pull_request.base.sha) instead of the latest successful run on the target branch. If there is no such run, the action falls back to the latest successful run on the target branch and emits a warning. Set baseline-sha to ""fgrosse/go-coverage-report#110
• Add baseline-run-idfgrosse/go-coverage-report#110
• Improve diagnostics when no baseline coverage is available: warnings and the pull request comment now distinguish between no successful baseline run being found and the coverage artifact of the selected run not being downloadable, and the fgrosse/go-coverage-report#110
• Show a caution callout at the top of the pull request comment if the report does not compare against the base commit fgrosse/go-coverage-report#110
• Name the baseline commit and run in the details section of the report via the new -baseline-commit, -baseline-run-id and -baseline-run-urlfgrosse/go-coverage-report#110
• Simplify the details section of the report: rename it to "Coverage details" and drop its headings to avoid mixing many fgrosse/go-coverage-report#110

Changelog

Sourced from fgrosse/go-coverage-report's changelog.

[v1.5.0] - 2026-10-02

• If the base commit of the pull request has no usable baseline run (e.g. because it failed, is still running or its artifact expired), the action now uses the nearest commit in the first-parent history of the base commit with a usable run instead of the latest run on the target branch. The runs of each commit are filtered client-side, since the filtered workflow runs API can return stale results, and further candidates are tried if a coverage artifact cannot be downloaded or does not fgrosse/go-coverage-report#113
• Add baseline-search-depth and baseline-max-downloads inputs to configure how far the action searches for a baseline fgrosse/go-coverage-report#113
• fgrosse/go-coverage-report#13
• Behavior change: By default, the baseline coverage is now taken from the latest successful run for the base commit of the pull request (new baseline-sha input, defaults to github.event.pull_request.base.sha) instead of the latest successful run on the target branch. If there is no such run, the action falls back to the latest successful run on the target branch and emits a warning. Set baseline-sha to ""fgrosse/go-coverage-report#110
• Add baseline-run-idfgrosse/go-coverage-report#110
• Improve diagnostics when no baseline coverage is available: warnings and the pull request comment now distinguish between no successful baseline run being found and the coverage artifact of the selected run not being downloadable, and the fgrosse/go-coverage-report#110
• Show a caution callout at the top of the pull request comment if the report does not compare against the base commit fgrosse/go-coverage-report#110
• Name the baseline commit and run in the details section of the report via the new -baseline-commit, -baseline-run-id and -baseline-run-urlfgrosse/go-coverage-report#110
• Simplify the details section of the report: rename it to "Coverage details" and drop its headings to avoid mixing many fgrosse/go-coverage-report#110

Commits

• c4bf7e7 Release v1.5.0
• 2d3d0a9 action: fall back to the nearest ancestor of the base commit (#113)
• 7752bdc action: select the baseline by the PR base commit and explain it in the repor...
• 6093ed4 Bump github/codeql-action from 4.38.0 to 4.38.1 (#112)
• b1b031a go-coverage-report: drop package name limitation (#111)
• See full diff in compare view

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)