LuciferYang opened a new pull request, #838:
URL: https://github.com/apache/iceberg-cpp/pull/838

   ## What
   
   `cpp-linter/cpp-linter-action` is frozen at v2.15.1. Its v2.16 release 
pulled in
   an untrusted dependency and was blocked by ASF Infra
   (apache/infrastructure-actions#325), and the ASF gateway ignores newer 
versions.
   The pinned action still runs, but it can no longer be updated.
   
   ## How
   
   The action is a thin wrapper around the `cpp-linter` PyPI package, and the 
block
   does not touch that package. This installs it plus matching clang tools with
   pip and calls the `cpp-linter` CLI with the same options the action used. The
   `checks-failed` output and the Fail fast step stay as they were. Because it 
is a
   `run:` step and not a `uses:` reference, it adds no new third-party action 
to the
   ASF allowlist.
   
   I also looked at emitting SARIF and uploading it with
   `github/codeql-action/upload-sarif`, which is allowed since it is a 
`github/*`
   action. That route loses the thread comment and needs an extra conversion 
step,
   so calling the CLI directly stays closer to what we have now.
   
   ## Verified
   
   I ran the CLI locally against this repo's `.clang-format` and `.clang-tidy` 
on a
   file containing a `NULL` and a mis-named member. Both clang-format and
   clang-tidy ran, emitted `::warning` annotations, and wrote `checks-failed` to
   `GITHUB_OUTPUT`. The PR also carries a temporary probe commit that trips the
   linter on purpose so CI exercises the new path; I will drop it before merge.
   
   ---
   This contribution was authored with assistance from Claude Opus 4.8, in line 
with
   the Iceberg guidelines for AI-assisted contributions
   
(https://iceberg.apache.org/contribute/#guidelines-for-ai-assisted-contributions).
   All changes were reviewed and tested by the author.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to