Publish a Studio project to Orchestrator

Package a Studio project and publish it to your Orchestrator tenant, a NuGet feed or a local folder, with versioning and optional signing.

Publishing turns a Studio project into a versioned automation package (.nupkg) and sends it to a destination: your Orchestrator tenant, any NuGet v3 feed, or a local folder. Once the package is on the Orchestrator, you create an automation from it and run it on Robots. What a package contains# The project content (project.json and the workflows) under content/. velophex/package-manifest.json: the runtime, the entry points with their input and output schemas, the dependencies, and the SHA-512 hash of every content file. velophex/signature.json, if you sign the package. The package ID is the project name and the version is the project version. A version can be published only once to a destination, so raise it for every change. Prerequisites# The project validates without errors. See Build workflows with activities. For the Orchestrator destination: Settings > Publishing > Orchestrator URL set, and Studio signed in to the tenant you publish to, with permission to create packages (the Automation Developer role has it). See Sign in to Orchestrator from Studio. For signing: a code-signing certificate with its private key in your personal certificate store, or a .pfx file. Publish a project# On the Design ribbon tab, select Publish. If you have unsaved changes, save them: the package is built from the files on disk. Package properties: check the Package ID and Version. Use Bump for the next Patch, Minor or Major version, and Prerelease for a label such as beta. Description and Authors are required. Optionally choose an Icon. Select Next. Runtime: check the runtime and the packages the project uses, and any warnings. Select Next. Publish options: choose the destination: Velophex Orchestrator: your tenant's package feed. The feed address is shown for reference. NuGet feed: enter the Feed URL. Studio asks for the feed's API key when you publish. Local folder: enter the Folder. It defaults to My packages, which Studio also uses as a package source. Validation: Studio checks the package properties, entry points, dependencies and every workflow. Fix any errors it lists; errors block publishing. Workflow Analyzer errors also block it when Check before publish is on in Project settings > Workflow Analyzer. Review and publish: check the summary and the signing line, then select Publish. The result shows Published, with the package, version, destination and SHA-256. Select Open destination to open the Orchestrator's Packages page, or the folder. After a successful publish, Studio writes the new ID and version to project.json. A local copy of the package is kept in the project's .velophex/publish/ folder. Versioning# Studio uses semantic versions such as 1.2.0 or 1.3.0-beta.1. Build metadata (+…) is not allowed. When you open Publish and the project version is the one you last published, Studio suggests the next patch or prerelease number. If the version already exists at the destination, Studio stops with a message such as already published. Raise the version and publish again. The Orchestrator also refuses a package whose content is identical to one already published under another version. Sign packages# Signing lets the Orchestrator and Robots prove who built a package and that nothing changed since. It is optional unless your organisation requires it. Open Settings > Publishing. In Signing certificate, pick your certificate. Or set Signing certificate file (.pfx); Studio asks for its password each time you publish and never saves it. Turn on Only publish signed packages if Publish should fail when it cannot sign. Publish as usual. The review step shows which certificate signs the package. Give your administrators the certificate's SHA-256 thumbprint so they can trust it on the Orchestrator and on Robots. See Package signing and supply chain. Package IDs that start with VeloPhex. or Velophex. are reserved for packages signed by VeloPhex. Set publish defaults for a project# Project settings > Publishing sets the default destination (Publish to), folder and feed address for the project, and shows when it was last published from this computer. Studio remembers your last destination in .velophex/user/publish.json, which is personal and not committed. Credentials are never stored there. What appears in the Orchestrator# The package appears in the tenant's Packages list with its version. Publishing does not create or start anything by itself: To run a new package, create an automation (process) from it in a workspace. See Packages and processes. Existing automations set to follow the latest version move to the new version. Then start a job. See Jobs. Publish from a pipeline# The tenant feed is a standard NuGet v3 feed, so a CI pipeline can push a package that Studio built (from .velophex/publish/) with a personal access token: Publish with dotnet nugetPowerShellCopydotnet nuget push .\Invoice.Processing.1.2.0.nupkg ` --source https://orchestrator.example.com/api/v1/tenants/<tenantId>/feed/v3/index.json ` --api-key vpx_pat_... Next steps# Packages and processes. Run the published automation on a Robot: Jobs.

What a package contains

Prerequisites

Publish a project

Versioning

Sign packages

Set publish defaults for a project

What appears in the Orchestrator

Publish from a pipeline

Next steps