Skip to content

docs(custom-harness): add note about semantic versioning - #33

Merged
fargito merged 3 commits into
mainfrom
docs/custom-harness-semantic-versioning
Oct 7, 2026
Merged

fargito merged 3 commits into
mainfrom
docs/custom-harness-semantic-versioning

Conversation

@fargito

@fargito fargito commented Oct 7, 2026

Copy link
Copy Markdown
Member

No description provided.

@fargito fargito self-assigned this Oct 7, 2026
@fargito
fargito requested a review from not-matthias October 7, 2026 07:42
@greptile-apps

greptile-apps Bot commented Oct 7, 2026 •

Copy link
Copy Markdown

RetriggerConfidence Score: 5/5

[Low risk] Documentation updates to the custom harness guide.

This documentation-only change appears safe to merge.

Summary

CUSTOM_HARNESS.md now tells custom harness authors to use semantic versioning for their integration version.

  • Fixes the cleanup step number.
  • Adds blank lines before lists and code blocks.
  • No actionable issues found.

Reviews (1) · Last reviewed commit: "docs(custom-harness): add note about sem..." · Reviewed by Greptile

cpp-linter-hooks v0.6.1 downloads clang-format from static binary
releases that no longer resolve, so the lint job fails before checking
any file. v1.x installs clang-format from PyPI wheels instead.

Pin --version=13 to keep the formatting previously enforced; newer
majors reflow existing sources.
Upstream added the VG_USERREQ__ADD_DESC client request and the
CALLGRIND_ADD_DESC macro. The header-sync check fails until the vendored
copy matches.
@fargito
fargito merged commit 248f071 into main Oct 7, 2026
52 checks passed
@fargito
fargito deleted the docs/custom-harness-semantic-versioning branch October 7, 2026 08:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants