chore: update Pangea User-Agent repo URL (#1595)

[ichbinlucaskim]

Update repository URL in Pangea integration User-Agent header.

Description

This PR updates the remaining reference to the old repository URL in the Pangea integration User-Agent header.
Only the User-Agent header string in nemoguardrails/library/pangea/actions.py is changed to point to https://github.com/NVIDIA-NeMo/Guardrails.

Related Issue(s)

Fixes #1595.

Checklist

• I've read the CONTRIBUTING guidelines.
• I've updated the documentation if applicable.
• I've added tests if applicable.
• @mentions of the person or team responsible for reviewing proposed changes.
  • @tgasser-nv @trebedea

[greptile-apps]

Greptile Overview

Greptile Summary

Updated the repository URL in the Pangea integration User-Agent header from https://github.com/NVIDIA/NeMo-Guardrails to https://github.com/NVIDIA-NeMo/Guardrails.

This change aligns with the repository migration (see commit 632678d) and ensures the HTTP headers sent to Pangea AI Guard API reflect the current repository location. The change is purely cosmetic and has no impact on functionality.

Note: One old URL reference remains in docs/_extensions/json_output/README.md:70 (in an example JSON structure), though this appears to be example/template content rather than production code.

Confidence Score: 5/5

• This PR is completely safe to merge with zero risk
• The change updates only a string literal in a User-Agent HTTP header with no impact on functionality, logic, or security. This is a trivial cosmetic update to reflect the repository's new URL
• No files require special attention

Important Files Changed

Filename	Overview
nemoguardrails/library/pangea/actions.py	Updated User-Agent header to use new repository URL

Sequence Diagram

sequenceDiagram
    participant Client as NeMo Guardrails
    participant HTTP as httpx.AsyncClient
    participant Pangea as Pangea AI Guard API
    
    Note over Client,Pangea: Updated User-Agent Header
    Client->>HTTP: Create request with headers
    Note right of HTTP: User-Agent: NeMo Guardrails<br/>(https://github.com/NVIDIA-NeMo/Guardrails)
    HTTP->>Pangea: POST /v1/text/guard
    Pangea-->>HTTP: Response
    HTTP-->>Client: Return result

Loading

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[ichbinlucaskim]

This PR only updates the Pangea integration User-Agent string to point to the new repository URL:
https://github.com/NVIDIA-NeMo/Guardrails

There are no code logic changes in this PR; only the User-Agent header string in
nemoguardrails/library/pangea/actions.py was updated.

All tests pass on newer Python versions:

• Lint
• Ubuntu / Python 3.11
• Ubuntu / Python 3.12
• Ubuntu / Python 3.13

The only failing job is:

• Ubuntu / Python 3.10

From the logs, the 3.10 job fails during poetry install with a Cannot install langchain-core
dependency resolution error, before any tests are executed. The tests themselves pass once the
environment is set up, so this appears unrelated to the changes in this PR.

I added a Signed-off-by line to comply with the contribution guidelines, but that only touched the
commit message and did not change any code. I don’t have permission to re-run the failed job myself,
so I’d appreciate it if a maintainer could either re-run the 3.10 job or advise on how to proceed.

[trebedea]

Are we sure Pangea / Crowdstrike does not do any validation on the User-Agent field?

Maybe @kenany who opened a MR for the new Crowdstrike AIDR can help us (Pangea was acquired by Crowstrike and this integration will be deprecated soon if I understand correctly)?

Need to make sure server-side updates are deployed before this change is made

[kenany]

Are we sure Pangea / Crowdstrike does not do any validation on the User-Agent field?

No such validation is done. This change is good to go from that angle.

[trebedea]

Looks good, as no validation is made by Pangea API on the user-agent.

Thanks @ichbinlucaskim and @kenany !