打包和发布

Functions are packaged as standard UiPath .nupkg packages and published to an Orchestrator feed. From there, a package is deployed as a process in an Orchestrator folder before it can be invoked. The flow is the same in both languages; only the command prefix and the version source differ.

	JavaScript / TypeScript	Python
包	uip function pack	uipath pack
发布	uip function publish	uipath publish
Version comes from	package.json	pyproject.toml

包

uip function pack

This produces a versioned .nupkg (for example, my-function.1.0.0.nupkg). Bump the version in your project file before packing a new release.

发布

uip function publish

You are prompted to select a package feed (for example, the Orchestrator Tenant Processes Feed); pass --feed-id to select one non-interactively in CI. Publishing uploads the .nupkg to that feed — at this point it is a package on the feed, not yet a runnable process.

部署

Before a function can be invoked, the published package must be deployed as a process in an Orchestrator folder — either manually in Orchestrator or through solution deployment. A function joins a solution the same way an RPA or API project does:

uip solution project import "./my-functions"
uip solution resources refresh

Once the process exists, the function becomes available to:

• Maestro 服务任务
• The Orchestrator API and job triggers (scheduled, event-based)
• Its HTTP trigger, for a JavaScript function that declares a method and path

版本控制

• The package version comes from the project file — package.json for JavaScript, pyproject.toml for Python.
• 发布新版本会将其添加到订阅源中；更新流程或 Maestro 服务任务绑定以选取该流程。
• .nupkg 与 RPA 使用的包格式相同 — 适用相同的订阅源、上传和版本管理机制。

后续步骤

• 调用函数— 将已发布的函数连接到流程中。