[dependabot]

Bumps fgrosse/go-coverage-report from 1.3.1 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

v1.4.0

• Also report packages whose coverage changed without any of their files being changed, e.g. when running integration tests with go test -coverpkgfgrosse/go-coverage-report#102
• fgrosse/go-coverage-report#103
• Fix the excludefgrosse/go-coverage-report#104

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

[v1.4.0] - 2026-09-20

• Also report packages whose coverage changed without any of their files being changed, e.g. when running integration tests with go test -coverpkgfgrosse/go-coverage-report#102
• fgrosse/go-coverage-report#103
• Fix the excludefgrosse/go-coverage-report#104

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)
• 2eb52af Release v1.4.0
• bdc98a2 go-coverage-report: apply -exclude to changed files (#104)
• 5ddcd46 report: hide packages without statements (#103)
• 037572f report: include packages whose coverage changed (#102)
• 7977258 Bump github/codeql-action from 4.37.9 to 4.38.0 (#106)
• Additional commits viewable 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)

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-01T14:07:55.040552Z	ba07a6e	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.