Empacotamento e publicação

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
Pacote	uip function pack	uipath pack
Publicar	uip function publish	uipath publish
Version comes from	package.json	pyproject.toml

Pacote

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.

Publicar

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.

Implantar

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:

• Uma tarefa de serviço do Maestro
• The Orchestrator API and job triggers (scheduled, event-based)
• Its HTTP trigger, for a JavaScript function that declares a method and path

Controle de versão

• The package version comes from the project file — package.json for JavaScript, pyproject.toml for Python.
• A publicação de uma nova versão a adiciona ao feed; atualize o processo ou a associação da Tarefa de Serviço do Maestro para selecioná-lo.
• O .nupkg é o mesmo formato de pacote usado pela RPA — o mesmo feed, upload e mecanismo de gerenciamento de versão se aplicam.

Próximas Etapas

• Invocar funções — conecte a função publicada a um processo.