[renovate]

This PR contains the following updates:

Package	Type	Update	Change
reviewdog	uses-with	minor	v0.20.1 → v0.21.3

---

Release Notes

reviewdog/reviewdog (reviewdog)

v0.21.3

Compare Source

🚀 Enhancements

• #​2059 Add support for range suggestions to gitlab-mr-discussion reporter

🐛 Fixes

• #​2944 Make SARIF file:// paths with a Windows drive letter relative, instead of leaving a leading slash in front of C:.
• #​2931 Allow GitHub annotation reporters to run with -filter-mode=nofilter without a GitHub token or repository metadata.
• #​2917 Include git's stderr in the error when git merge-base or git diff fails for GitLab and Gerrit, instead of only reporting exit status 128.
• #​2910 Keep git diff warnings on stderr out of the diff when GitHub and Gitea fall back to the git command, so the diff still parses.
• #​2891 Skip SARIF results whose kind is pass or notApplicable instead of reporting them as diagnostics.
• #​2865 Retry a GitHub Checks update that gets 404 right after the check run is created, instead of leaving it in_progress.
• #​2857 Place -f=diff suggestions that insert lines at the top of a file on line 1, instead of shifting that hunk's suggestions one line down.
• #​2856 Normalize Windows diagnostic paths when the tool reports a different path casing.
• #​2849 Preserve informational diagnostic severity as note when emitting SARIF.
• #​2850 Send an encoded absolute OAuth redirect_uri targeting the registered Doghouse callback route.
• #​2851 Allow the installation-store transaction to insert an account's first installation record.
• #​2848 Preserve diagnostic annotations when GitHub review publication falls back to Actions logging after a permission error.
• #​2847 Reject null runner definitions with a configuration error and avoid a panic for a single-word git diff command.
• #​2823 Fall back to the paginated "list pull request files" API when GitHub's diff API rejects pull requests with more than 300 changed files (fixes #​2150).
• #​2826 Bitbucket: keep an annotation that another runner already reported for the same diagnostic, instead of leaving that runner's report without it.
• #​2833 Resolve SARIF artifact locations that refer to entries in run.artifacts by index.

v0.21.2

Compare Source

🚀 Enhancements

• #​2153 Log diagnostic filtering counts at debug level so fully filtered input is visible

🐛 Fixes

• #​2801 Report GitHub Checks even when there are no findings (regression since v0.21.1).
• #​2477 Prevent deadlock when a runner outputs large stderr.
• #​2809 Prevent crash when SARIF replacement inserted content is mil (fixes #​2808).
• #​950 Report diff parse errors instead of silently returning the file diffs parsed so far.
• #​951 Parse a diff that carries blank lines around it, and a context line that lost its leading space to trailing-whitespace stripping.

v0.21.1

Compare Source

✨ Release Note

The Homebrew package has migrated from a formula to a cask. Install it with brew install --cask reviewdog/tap/reviewdog.

🚀 Enhancements

• #​2257 Use -trimpath flag for reproducible build
• #​2513 Drop support of windows/arm
• #​2543 Update gitlab-mr-discussion reporter to embed a fingerprint meta-comment in each posted note and automatically resolve previously-posted discussions whose diagnostic is no longer reported (fixes #​1150).
• #​2747 Update gitea-pr-review reporter to be on par with github-pr-review: report results outside the diff context as pull request comments, fallback to Actions logging commands for results outside the diff file and honor the -level flag.

🐛 Fixes

• #​2586 Honor SARIF result.suppressions in SARIF parser — suppressed results (per SARIF 2.1.0 §3.27.23 / §3.35) no longer emit diagnostics
• #​2481 Use CWD instead of git root in SARIF parser to prevent path doubling
• #​2663 Fix deadlock when parsing too-long RDJSONL lines.

🚨 Breaking changes

• doghouse: the /check endpoint (used by -reporter=github-pr-check via reviewdog.app) now always requires REVIEWDOG_TOKEN. The previous shortcut that accepted requests from certain CI providers without a token has been removed. Users who relied on the token-less path (e.g. AppVeyor) must now set REVIEWDOG_TOKEN explicitly. Tokens can be obtained from https://reviewdog.app/gh/<owner>/<repo-name>.

v0.21.0

Compare Source

✨ Release Note

Starting from this release, reviewdog enables immutable releases to ensure the integrity of released assets. Released assets and the release itself are now immutable and can be verified using:

gh release verify <tag>
gh release verify-asset <tag> <asset>

🚀 Enhancements

• #​2026 Add reporter for GitHub annotations github-annotations. Same as github-pr-annotations but not restricted to pull requests.
• #​2131 Fetch GitHub git based diffs using the base pull request repo to allow fetching from private forks in GitHub Actions.
• #​2210 Update Gitea PR reporter to detect comments for already reported issues and report suggestions.
• #​1931 Refactor handling of Git relative path - Centralized path normalization logic and added automatic --relative flag to git diff commands for consistent relative path handling.

🐛 Fixes

• #​967 Fix parsing long lines in diffs #​967
• #​1344 Bitbucket Cloud Fixes
• #​1983 Improve error message for diff command failure by including stderr output
• #​1975 Fix for suggestions not including an inserted EOF newline
• #​2026 Never filter diffs when running github-[pr-][check|annotate] on non-PRs
• #​2214 #​2231 Migrate install.sh from godownloader to binstaller to prevent future failures when .sbom.json files are added to release artifacts. While reviewdog releases don't currently include SBOM files, this preemptively fixes the grep pattern bug that would cause installation failures when they are added in the near future.

v0.20.3

Compare Source

🐛 Fixes

• #​1977 Include stderr in the error message if we run git command

v0.20.2

Compare Source

🚀 Enhancements

• #​1845 Normalize file path in related_locations too.

🐛 Fixes

• #​1846 Unexpected error
  exit code when using -reporter=github-[pr-]check with
  -fail-on-error=true. See the below breaking changes section for more details.
• #​1867 Tool name was incorrect for github-[pr-]check reporters and check API does not work correctly for project config based run
• #​1867 Deletion of outdated comment didn't work properly with github-pr-review reporter since tool name isn't correctly configured for project config based run
• #​1894 fix error when repository uses multiselect custom-properties #​1881
• #​1903 Adjust result paths for github-[pr-]check and github-pr-annotaions reporters relative to the git directory

🚨 Breaking changes

• #​1858 Remove original_output from rdjson/rdjsonl reporters' output

🚨 Deprecation Warnings

• #​1854 (Actually No Breaking changes) -fail-on-error
  flag is deprecated. Use -fail-level=[none,any,error,warning,info] flag
  instead. You can reproduce the same behavior with -fail-level=any for most
  reporters (reviewdog will exit with 1 if it find any severity level).
  As for github-[pr-]check reporter you can reproduce the same behavior with
  -fail-level=error (#​1846).

  -fail-on-error is just deprecated and it's not removed yet. Please update
  the flag while it's working.

---

Configuration

📅 Schedule: (in timezone Etc/UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.