Skip to content

chore: require uipath-runtime>=0.13.1 for the output-arguments split - #1858

Open
eduard-dumitru wants to merge 1 commit into
mainfrom
feat/output-args-memory-optimization
Open

chore: require uipath-runtime>=0.13.1 for the output-arguments split#1858
eduard-dumitru wants to merge 1 commit into
mainfrom
feat/output-args-memory-optimization

Conversation

@eduard-dumitru

Copy link
Copy Markdown
Contributor

Why

uipath-runtime 0.13.1 added runtime.splitOutputArguments (uipath-runtime-python#159): when set, a job's output arguments are written to their own file and the result envelope carries an outputArgumentsFilePath pointer instead of the inline output value, so a consumer can stream the payload instead of materializing it. In Serverless that is the difference between an ~80 MB job completing and OOMing the handler.

An older runtime does not recognise the key and silently ignores it — the payload stays inline and the consumer gets exactly the blowup the split exists to avoid, with no error to explain it. Raising the floor turns that silent no-op into a resolution failure.

What

  • uipath-runtime>=0.13.0>=0.13.1
  • uipath 2.14.2 → 2.14.3
  • uv.lock regenerated (resolves uipath-runtime 0.13.1)

No source changes.

Testing

2375 passed, 1 skipped; uv lock --check, ruff and full mypy (324 files, src + tests) all clean.

Chain

This is 2 of 4. Each link can only open once the previous one publishes.

  1. uipath-runtime-python — the split itself (published as 0.13.1)
  2. this PR — raise the floor so the key is guaranteed present
  3. uipath-agents-python — three ceilings currently exclude both new versions
  4. hdens — consume the pointer and stream the file into the blob upload

0.13.1 adds runtime.splitOutputArguments, which writes a job's output arguments
to their own file and leaves an outputArgumentsFilePath pointer in the result
envelope. Raising the floor guarantees the key is understood rather than silently
ignored by an older runtime, which would leave the payload inline and hand the
consumer the memory blowup the split exists to avoid.

Version-only change on top; no source touched.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Copilot AI lite review requested due to automatic review settings August 12, 2026 14:39

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

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 the uipath package’s dependency floor to require uipath-runtime>=0.13.1 (ensuring runtime.splitOutputArguments is available and not silently ignored), and bumps the uipath package patch version accordingly. It fits into the monorepo by adjusting the main SDK/CLI package’s published metadata and lockfile to align with the newer runtime behavior.

Changes:

  • Bump uipath version 2.14.22.14.3.
  • Raise uipath-runtime requirement >=0.13.0,<0.14.0>=0.13.1,<0.14.0.
  • Regenerate uv.lock to resolve uipath-runtime 0.13.1.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.

File Description
packages/uipath/pyproject.toml Bumps uipath version and raises the minimum uipath-runtime version to 0.13.1.
packages/uipath/uv.lock Updates the lockfile to reflect uipath 2.14.3 and resolve uipath-runtime 0.13.1.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants