Repository navigation
feat(telemetry): report integration version on coded run events [PC-5233] - #1951
Merged
Merged
Conversation
github-actions
Bot
added
test:uipath-langchain
tudormatei1
marked this pull request as ready for review
October 20, 2026 09:17
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The focused changes cover both CLI paths and optional version reporting, with no unresolved blocking issues.
No open issues 🎉
What changed in this PR
Adds integration package versions to coded run telemetry, extending existing framework reporting.
Changes:
- Reports
IntegrationVersionfor run and debug lifecycle events when available. - Adds tests for installed packages and factories without package metadata.
- Bumps
uipathto version2.14.42.
| File | Description |
|---|---|
packages/uipath/uv.lock |
Updates the locked SDK version. |
packages/uipath/tests/cli/test_run_telemetry.py |
Tests version reporting and omission. |
packages/uipath/src/uipath/_cli/cli_run.py |
Passes the runtime factory to telemetry. |
packages/uipath/src/uipath/_cli/cli_debug.py |
Passes the debug factory to telemetry. |
packages/uipath/src/uipath/_cli/_run_telemetry.py |
Resolves and includes the integration version. |
packages/uipath/pyproject.toml |
Bumps the package version. |
Review effort: Balanced
radu-mocanu
approved these changes
Oct 21, 2026
tudormatei1
marked this pull request as draft
October 21, 2026 12:14
tudormatei1
marked this pull request as ready for review
October 21, 2026 12:14
Projects only report AgentFramework once they upgrade their integration package, and nothing showed which release a run was on. Coded run events now carry IntegrationVersion: the installed version of the package the runtime factory class ships in, read once per run. It is omitted when the factory lives outside an installed package.
tudormatei1
force-pushed
the
feat/coded-run-integration-version
branch
from
October 21, 2026 12:15
a36be48 to
1cf800b
Compare
tudormatei1
enabled auto-merge (squash)
October 21, 2026 12:15
tudormatei1
disabled auto-merge
October 21, 2026 12:16
tudormatei1
enabled auto-merge (squash)
October 21, 2026 12:41
|
🚨 Heads up:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #1947. Framework reporting depends on the customer's integration version, and until now nothing told us which release a run was on. Coded run events now carry
IntegrationVersion, the installed version of the package the runtime factory class comes from (uipath-llamaindex,uipath-langchain,uipathfor functions, and so on). The integrations don't need any change.It's one
importlib.metadata.version()call per run, made only when the run is reported. Benchmarked at 0.2 to 0.3 ms per run across the eight integration environments, and an A/B of 30 realuipath runcalls each showed no difference beyond run-to-run noise (median +5.8 ms, mean -8.3 ms, against a 50 to 70 ms spread).A factory defined outside an installed package, such as in user code, gets no property. This is the integration package's version, not the underlying framework library (
llama-index-core,langgraph). The new property probably needs adding to the BOI portal event spec too.