Skip to content

feat(guardrails): consume uipath-platform 0.2.9 for BYOG evaluation#986

Merged
valentinabojan merged 1 commit into
mainfrom
valentinabojan/byo-guardrail-runtime-support
Jul 13, 2026
Merged

feat(guardrails): consume uipath-platform 0.2.9 for BYOG evaluation#986
valentinabojan merged 1 commit into
mainfrom
valentinabojan/byo-guardrail-runtime-support

Conversation

@valentinabojan

Copy link
Copy Markdown
Contributor

What changed?

Bumps the uipath-platform floor to 0.2.9 so Bring-Your-Own-Guardrail (BYOG) guardrails are evaluated correctly at runtime.

A BYOG guardrail is persisted as a BuiltInValidatorGuardrail with the "byo" sentinel validatorType and a byoValidatorName referencing the connector-backed configuration. uipath-platform 0.2.9 exposes byo_validator_name as a typed field and forwards it in the guardrail validation request; earlier versions dropped it, so the service could not resolve the configuration.

  • pyproject.tomluipath-platform>=0.2.5>=0.2.9; version 0.14.60.14.7.
  • uv.lock — regenerated (uipath-platform 0.2.9).
  • Regression tests confirming a "byo" built-in validator guardrail:
    • maps through build_guardrails_with_actions unchanged, preserving byo_validator_name
    • is not dropped by the stage filter (runs in every stage its scope runs)

Why

The runtime already passes the guardrail object straight through to evaluate_guardrail, so no source change is needed here — only the dependency floor so the forwarding is guaranteed present. With this bump, BYOG guardrails execute end-to-end.

Notes

Requires the platform change in UiPath/uipath-python#1810 (merged, released as uipath-platform 0.2.9).

All guardrail tests pass (279); ruff clean.

🤖 Generated with Claude Code

Copilot AI review requested due to automatic review settings July 13, 2026 19:27
Bump the uipath-platform floor to 0.2.9 so BYOG guardrails forward their
byoValidatorName reference during evaluation. Adds regression tests
confirming a "byo" built-in validator guardrail maps through the factory
unchanged (preserving byo_validator_name) and runs in every stage its scope
runs. Bumps uipath-langchain to 0.14.7.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@valentinabojan valentinabojan force-pushed the valentinabojan/byo-guardrail-runtime-support branch from 99324b4 to d6f27e6 Compare July 13, 2026 19:29

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates uipath-langchain to require uipath-platform>=0.2.9 so Bring-Your-Own-Guardrail (BYOG) built-in validator guardrails retain and forward byo_validator_name during evaluation, and adds regression tests to ensure BYOG guardrails are not altered or stage-filtered incorrectly.

Changes:

  • Bumped dependency floor: uipath-platform>=0.2.5>=0.2.9 and package version 0.14.60.14.7.
  • Regenerated uv.lock to reflect uipath-platform==0.2.9.
  • Added tests validating BYOG guardrails preserve byo_validator_name, have actions mapped correctly, and are not dropped by stage filtering.

Reviewed changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated no comments.

File Description
pyproject.toml Raises uipath-platform minimum version to ensure BYOG forwarding support; bumps package version.
uv.lock Updates locked dependencies to include uipath-platform 0.2.9.
tests/agent/guardrails/test_guardrails_factory.py Adds regression tests ensuring BYOG built-in validator guardrails pass through the factory and preserve byo_validator_name.
tests/agent/guardrails/test_guardrail_stage_filtering.py Adds tests ensuring BYOG validators (sentinel validator_type="byo") are not filtered out in any execution stage.

@sonarqubecloud

Copy link
Copy Markdown

@valentinabojan valentinabojan merged commit 5a837af into main Jul 13, 2026
71 of 72 checks passed
@valentinabojan valentinabojan deleted the valentinabojan/byo-guardrail-runtime-support branch July 13, 2026 20:33
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.

3 participants