25.10.20

Release date: June 4, 2026

错误修复

Deploying to an existing process no longer fails with "the name is already used"

Fixed an issue where deploying a package to update an existing process could fail with the error "the name is already used", even though the process already existed and should simply have been updated to the new package version.

If you ran uipcli package deploy against a process that already existed in Orchestrator, the deployment could be rejected instead of updating the process. With 25.10.20, the CLI reliably finds the existing process and updates it in place — the deployment succeeds and no duplicate process is created — whether you are updating or renaming it.

If you have hit "the name is already used" when redeploying an existing process, upgrade to 25.10.20.

Entry points are chosen by Orchestrator when you don't specify one

When you deploy without --entryPointsPath, the CLI no longer picks an entry point on its own:

• For a new process, Orchestrator selects the entry point.
• For an existing process, your current entry point is kept if it still exists in the new package version; otherwise Orchestrator selects one.

If you pass --entryPointsPath (or --processName) explicitly, nothing changes — the entry point you specify is used exactly as before.