Skip to content

feat(uipath-activity-migrator): get the migrator through uip rpa project migrate, the archive as fallback - #4749

Open
leonard-apostoaie wants to merge 2 commits into
mainfrom
feat/STUD-82122-migrator-via-uip
Open

leonard-apostoaie wants to merge 2 commits into
mainfrom
feat/STUD-82122-migrator-via-uip

Conversation

@leonard-apostoaie

@leonard-apostoaie leonard-apostoaie commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Why

The Activity Migrator now ships inside Helm (UiPath/Studio#31591, STUD-82122): UiPath.Studio.Helm.exe migrate analyze|upgrade|bulk|version. It is in every Windows Helm: the win32-x64 and win32-arm64 Helm npm packages that uip installs, and the Studio MSI's. uip rpa project migrate <verb> <args> runs it with the standalone tool's arguments, SARIF output and exit code. There is no separate npm package and no install command, so the skill gets the migrator from uip first. The public UiPath.Upgrade.exe archive (26.10.0) remains as the fallback.

What

  • scripts/ensure-migrator.mjs
    • The script first runs uip rpa project migrate version, with UIPATH_STUDIO_PID removed from the environment. When it prints a version, the result is source: "uip" with command: "uip rpa project migrate": no exe, no runtime check, nothing downloaded.
    • not-windows stops the run.
    • The archive path is used when uip reports helm-missing, when uip is missing or too old to have the command, or when its Helm has no migrate verb. That path works exactly as feat(uipath-activity-migrator): ask before downloading UiPath.Upgrade.exe #4536 describes (missing, --install/--force, offline precedence, update: true), and its results carry uip's reason in uipMessage.
    • The archive's .NET Desktop Runtime check now reads the version and roll-forward policy from UiPath.Upgrade.runtimeconfig.json instead of assuming .NET 8: the 26.10 archive targets .NET 10, the 25.10 ones .NET 8.
    • version is the last line of uip's output that reads as a version, so a notice printed after it does not hide it.
  • SKILL.md
    • <MIGRATOR> replaces <MIGRATOR_EXE>. It is env -u UIPATH_STUDIO_PID uip rpa project migrate for source uip (Rule 8, PowerShell form included), and "<exe>" for the archive.
    • Step 0's table now has the uip rows.
    • Rule 15 guards only the archive download, because the uip path downloads nothing.
  • references/acquisition-guide.md
    • Covers the Helm path through uip (online, internal registry, air-gapped CLI archive, Studio MSI through HELM_LOCAL_DIR) and what each uip failure means.
    • Then the archive fallback: the install question, which names uip update, or reinstalling uip with its optional Helm dependency, as the alternative to downloading. Also managed environments, the archive's variables, manual placement and the output contract.
  • scripts/summarize-sarif.mjs: a uip failure (its FailureOutput JSON) redirected into the .sarif exits 2 as failure reported by uip, with uip's code and message, instead of reading as a log without results. Steps 3 and 4 send that case back to Step 0.
  • references/tool-behavior-guide.md and the package guides: use <MIGRATOR>.
  • Tests and evals
    • The uip tests in the ensure-migrator suite are rewritten for the new contract; the archive tests are unchanged.
    • The eval patterns accept uip rpa project migrate analyze|upgrade.
    • studioweb-browser-commands.json allows the new uip rpa project migrate and uip update mentions; the Studio Web flavor stops this skill before Step 0. It also allows the prose uip codedapp pack pointer in uipath-coded-apps/references/widgets/decisions-and-reasons.md, which came with feat(uipath-coded-apps): decision capture with the decisions-and-reasons widget #4233 and pushed that skill one over its ceiling.

Verification

  • node --test on the ensure-migrator, summarize-sarif and studioweb-browser-commands suites: 94 tests, 93 passed, 0 failed, 1 skipped (the non-Windows case, on a Windows host).
  • npm run skills:validate, npm run skills:check-links and the description pre-commit hook pass. SKILL.md is 39,789 bytes; the description is 1,011 characters.
  • The behaviour the skill relies on was checked against a local Helm build in UiPath/Studio#31591: migrate version prints Helm's version, and migrate analyze / upgrade agree with the standalone tool on all 40 Upgrade test projects.
  • Open: with UIPATH_ACTIVITY_MIGRATOR_OFFLINE=1 the script still asks uip rpa project migrate version, which downloads nothing once rpa-tool and Helm are installed; whether uip installs a missing tool on first use offline is not verified here.
  • Coder-eval runs are not done yet. They need a uip with a Helm that carries the migrator, which UiPath/Studio#31591 produces.

🤖 Generated with Claude Code

…ect migrate, the archive as fallback

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Claude finished @leonard-apostoaie's task in 1m 26s —— View job


Coder-eval task lint (advisory)

12 task YAMLs changed (all modified, none added). Per-task verdicts: 0 Critical, 0 High, 9 Medium, 1 Low, 2 OK. One more High applies to the whole PR: no passing-run claim.

Rubric: .claude/commands/lint-task.md. This check is advisory and never blocks merge.

Every task change follows one pattern. \bmigrate is added as a command head for analyze/upgrade, and as a segment stop in the lookahead idiom. I checked these by reading them: env -u UIPATH_STUDIO_PID uip rpa project migrate analyze … --output-format sarif matches, … migrate analyze --help is exempt, and a chained && uip rpa project migrate upgrade still ends the segment. I could not run the patterns in this job because Python execution needed approval.

Evidence of passing run

  • ❌ High: the PR body says the opposite of a passing run: "Coder-eval runs are not done yet. They need a uip with a Helm that carries the migrator." Once a run exists, please add a line to the description like: Ran skill-migrator-migrate-classic-windows locally and it passed. A run against the archive fallback would also help. It would show the widened patterns didn't break the path the runners use today.

Per-task lint

tests/tasks/uipath-activity-migrator/migrate-classic/migrate_classic_windows.yaml — verdict: Medium

Issues:

  • [Medium] Meaningful coverage: the Rule 8 guard (L52) lists build|validate|run|debug|instances|execution|activities|uia but not project. A bare uip rpa project migrate analyze … with no UIPATH_STUDIO_PID clearing passes ungraded. SKILL.md L62 now requires the pin on <MIGRATOR> itself.
  • [Low] Meaningful coverage: the description (L7) still says "acquire UiPath.Upgrade.exe", and the prompt (L33) says "Download the Activity Migrator if it is not installed". On the uip path nothing is downloaded, and no criterion records which source the agent used.

Suggested fixes:

  • Add project\s+migrate to the L52 alternation: …(?:build|validate|run|debug|instances|execution|activities|uia|project\s+migrate)\b.
  • Reword L7 as "obtain the migrator (uip, or the archive fallback)". Keep the prompt's consent sentence, because the archive path still needs it.

tests/tasks/uipath-activity-migrator/left-classic/left_classic_smoke.yaml — verdict: Medium

Issues:

  • [Medium] Meaningful coverage: same Rule 8 gap. The guard regex has no project\s+migrate.
  • [Low] Meaningful coverage: the prompt (L35) still frames acquisition as a download.

Suggested fixes: same as migrate-classic.

tests/tasks/uipath-activity-migrator/migrate-gsuite-gmail/migrate_gsuite_gmail_integration.yaml — verdict: Medium

Issues:

  • [Medium] Meaningful coverage: same Rule 8 gap.
  • [Low] Meaningful coverage: the "download" wording in the prompt (L51) is now stale.

Suggested fixes: same as migrate-classic.

tests/tasks/uipath-activity-migrator/migrate-microsoft-activities/migrate_microsoft_activities_integration.yaml — verdict: Medium

Issues:

  • [Medium] Meaningful coverage: same Rule 8 gap.

Suggested fixes: add project\s+migrate to the Rule 8 command_not_executed alternation.

tests/tasks/uipath-activity-migrator/migrate-outlook-mail/migrate_outlook_mail_integration.yaml — verdict: Medium

Issues:

  • [Medium] Meaningful coverage: same Rule 8 gap.
  • [Low] Meaningful coverage: the "download" wording in the prompt (L45) is now stale.

Suggested fixes: same as migrate-classic.

tests/tasks/uipath-activity-migrator/migrate-selector-classes/migrate_selector_classes_e2e.yaml — verdict: Medium

Issues:

  • [Medium] Meaningful coverage: same Rule 8 gap.
  • [Low] Meaningful coverage: the "download" wording in the prompt (L38) is now stale.

Suggested fixes: same as migrate-classic.

tests/tasks/uipath-activity-migrator/migrate-with-fixes/migrate_with_fixes_e2e.yaml — verdict: Medium

Issues:

  • [Medium] Meaningful coverage: same Rule 8 gap.
  • [Low] Meaningful coverage: the "download" wording in the prompt (L38) is now stale.

Suggested fixes: same as migrate-classic.

tests/tasks/uipath-activity-migrator/plan-check-app-state/plan_check_app_state_local.yaml — verdict: Medium

Issues:

  • [Medium] Meaningful coverage: same Rule 8 gap. This task runs analyze and upgrade, so a migrator call without the pin is ungraded.

Suggested fixes: add project\s+migrate to the Rule 8 alternation.

tests/tasks/uipath-activity-migrator/runtime-pass/runtime_pass_local.yaml — verdict: Medium

Issues:

  • [Medium] Meaningful coverage: same Rule 8 gap. This task also runs analyze and upgrade.

Suggested fixes: add project\s+migrate to the Rule 8 alternation.

tests/tasks/uipath-activity-migrator/stop-missing-package/stop_missing_package_smoke.yaml — verdict: Low

Issues:

  • [Low] Could pass for the wrong reason: the new \bmigrate["']?\s+upgrade\b head in the "never ran upgrade" guard (L114) has no segment check. Any Bash string containing migrate upgrade also trips it, for example an echo of the next step. The old $VAR upgrade head had the same weakness.
  • [Low] Meaningful coverage: the "download" wording in the prompt (L33) is now stale.

Suggested fixes:

  • Anchor the head: (?:UiPath\.Upgrade\.exe|\brpa\s+project\s+migrate|\$\{?\w+\}?)["']?\s+upgrade\b.

tests/tasks/uipath-activity-migrator/post-migration-fix/post_migration_fix_only.yaml — verdict: OK

tests/tasks/uipath-activity-migrator/runtime-fix-loop/runtime_fix_loop_local.yaml — verdict: OK

Within-PR duplicates

  • No duplicate clusters detected. No tasks were added.

Themes

  • The Rule 8 guard misses the new migrator command (9 tasks). The skill now routes analyze and upgrade through uip rpa project migrate, and Rule 8 requires clearing UIPATH_STUDIO_PID for it. The command_not_executed guard copied across the suite has no project verb in its list, so that rule is unchecked for the migrator. Adding project\s+migrate to the alternation in one sweep fixes all 9 tasks.
  • No task covers the uip acquisition path. Every changed pattern accepts either path, but no criterion shows which source ensure-migrator.mjs returned. Consider adding one task, once a Helm with migrate exists on the runner, that asserts uip rpa project migrate was used and no archive was downloaded (command_not_executed on download\.uipath\.com/upgrade|ensure-migrator\.mjs[\s\S]{0,200}?--install).
  • Stale download wording in prompts (7 tasks). Keeping "Download the Activity Migrator if it is not installed" is fine as consent for the archive fallback. Descriptions that say "acquire UiPath.Upgrade.exe" should be reworded.

Conclusion

  • ⚠ 10 tasks have issues (9 Medium, 1 Low), and the PR has no passing-run claim (High). Advisory only, not blocking merge.

@github-actions

github-actions Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Claude finished @leonard-apostoaie's task in 2m 6s —— View job


Summary

The skill now gets the Activity Migrator from uip rpa project migrate (the migrator inside Helm) first, and falls back to the public UiPath.Upgrade.exe archive. <MIGRATOR> replaces <MIGRATOR_EXE> everywhere. The diff also changes how the archive's .NET runtime is checked: the script now reads the version from UiPath.Upgrade.runtimeconfig.json and follows its roll-forward policy, where before it hard-coded .NET 8.

Change-by-Change Review

1. A uip failure in Step 3/4 is routed to the wrong row — Medium

SKILL.md:139 puts the uip-failure guidance ("a uip failure (JSON, "Result":"Failure") may sit in the .sarif instead: rerun Step 0") in the Summarizer exits 2 row. That row never fires in this case:

  • When uip writes its FailureOutput to stdout, it lands in analyze-latest.sarif.
  • summarize-sarif.mjs:90-95 parses it as valid JSON and finds no runs.
  • It exits 0 with status: unknown and the reason "the log has no results: … as for a project without workflows" (summarize-sarif.mjs:288-290).
  • The agent then takes the status: unknown row, stops, and tells the user the project has no workflows. That is wrong: Helm is missing.

acquisition-guide.md and tool-behavior-guide.md:18 both say the failure can arrive "on stdout or stderr", so this is a real path. Step 4's table has the same gap. Two ways to fix it:

  • Preferred: in parseSarif, exit 2 when the parsed object has Result === 'Failure' and no runs, and print uip's Code/Message.
  • Or move the guidance into the status: unknown row.

Fix this →

2. scripts/ensure-migrator.mjs — OK, with notes

  • The uip probe is careful:
    • The command line is fixed, so shell: true sees no input.
    • UIPATH_STUDIO_PID is removed from the environment.
    • not-windows from uip is fatal; every other failure falls back to the archive.
    • uipMessage is attached to every later result.
  • The version check reads only the last stdout line (:118). If a future uip prints a trailing notice after Helm's version (an update banner, for example), the script falls back to the archive with an odd uipMessage. Low risk. Consider scanning for the last line that matches ^\d+\.\d+ instead.
  • uipFailure (:91-102) tries JSON.parse on every {…} pair, which is O(n²) on long output. That is fine for the version output it reads today.
  • The runtimeconfig/roll-forward rewrite (:248-315) looks correct, and the new tests cover .NET 8, .NET 10, DOTNET_ROLL_FORWARD and a missing runtimeconfig. The PR description does not mention it; see feature: Improve coded agent development from claude code experience #4.

3. SKILL.md, acquisition-guide.md, tool-behavior-guide.md, package guides — OK

  • <MIGRATOR> is used the same way throughout.
  • Rule 8's env -u UIPATH_STUDIO_PID prefix is built into <MIGRATOR>, in both its bash and PowerShell forms.
  • Rule 15 is correctly narrowed to the archive download.
  • The Step 0 table covers both sources.
  • Every link resolves, and there are no cross-skill references.
  • The description is 1,011 characters, under the 1,024 cap.

4. PR description does not match the diff — Low

  • The description says this PR removes the npm-package install flow, the shared-files.json restore, UIPATH_ACTIVITY_MIGRATOR_PACKAGE, _CACHE_DIR and _VERSION. None of these exist on origin/main (git grep finds nothing), so nothing is removed. They were probably in an earlier, unmerged draft.
  • The diff does contain the runtimeconfig-based runtime check, which the description leaves out.

Please correct the description so reviewers know what is actually changing.

5. Eval task patterns (12 YAMLs) — OK

  • \bmigrate was added both as a start alternative and as a terminator in the lookahead. The matched text starts at migrate analyze, after uip, so the \s(?:uip|\$UIP)\s terminator is never crossed.
  • The negative pattern ("analyze/upgrade without sarif") was updated the same way.

6. tests/scripts/studioweb-browser-commands.json — OK

The allow entries name their reason: the studioweb flavor stops the skill before Step 0.

What's Missing

  • No coder-eval passing-run claim. The PR says so itself. .claude/rules/test-writing.md step 5 requires one, and /lint-task flags its absence as High. The runs need a uip whose Helm carries migrate.
  • No eval task covers the fallback. Nothing exercises the case where uip fails and the archive is used: the uipMessage in the install question, and the uip update / reinstall-with-optional-deps alternative. The unit tests cover the script; nothing checks that the agent relays the reason.
  • No regression test for the uip-failure-in-SARIF case from feat(EvalsBreakdown): break down eval skill #1.

Area Ratings

Area Status Notes
Frontmatter OK 1,011 characters; triggers unchanged
E2E Tests Issue Patterns updated, but no coder-eval run and no task for the fallback
Skill Body Issue Step 3/4 routing for a uip failure on stdout (#1)
References & Assets OK Acquisition guide restructured clearly
Repo Hygiene OK No secrets; C:\Users\me in the output-contract examples is illustrative, same as on main

Issues for Manual Review

  • CLI availability. rpa project migrate is not in assets/uip-catalog-snapshot.json (CLI 1.207.0-dev.9850). Until a released CLI and Helm ship it, every user takes the fallback, which carries an "unknown command" uipMessage. Confirm the release timing before or soon after merging.
  • Offline mode. UIPATH_ACTIVITY_MIGRATOR_OFFLINE=1 still calls uip rpa …, on the premise that "migrate version downloads nothing". Please confirm that uip never installs @uipath/rpa-tool or Helm on demand the first time uip rpa runs. If it can, an admin's no-network setting is bypassed. If it can, skip the uip probe under OFFLINE unless Helm is already installed.
  • SARIF on stdout. The unit test feeds "Resolving Helm...\n27.0.207-dev", which implies uip may print progress text to stdout. The summarizer tolerates text before the JSON, so that is fine. Still confirm that uip never writes text after the SARIF, or anything between braces, during analyze/upgrade, or the parse breaks.
  • Argument passthrough. The claim that uip rpa project migrate passes stdout, stderr, the exit code and --name=value arguments through unchanged comes from UiPath/Studio#31591. I can't verify it here.

Conclusion

The direction and the script are solid, and the archive path is unchanged and well tested. I'm requesting changes for #1, the misrouted uip-failure case in Step 3/4: an agent following the current guidance would report a missing Helm as "project without workflows". Please also correct the PR description (#4) and get a coder-eval run in once a Helm build with migrate is available.

…ne, reads the last version line, allows a coded-apps prose mention

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant