Skip to content

cherry-pick(release/v1.206): run a package with no project in the default project (#4630) - #4750

Merged
ganeshborle merged 1 commit into
release/v1.206from
cherry-pick/v1.206-uipath-test-run-default-project
Nov 16, 2026
Merged

ganeshborle merged 1 commit into
release/v1.206from
cherry-pick/v1.206-uipath-test-run-default-project

Conversation

@KunalSM99

Copy link
Copy Markdown
Contributor

Port of #4630 to release/v1.206, to go with the CLI cherry-pick UiPath/cli#6094: with no project named, the agent leaves out --project-key on uip tm run --type package, which then runs in the tenant's default project, and tells the user Data.ProjectKey. Other new work with no project still uses get-default.

Not a plain cherry-pick

The 1.206 uipath-test/SKILL.md is laid out differently from main (bullets, and its own "Default project" section), so git cherry-pick conflicts. The same two edits are made by hand to the 1.206 text:

  • Default project section: running a package no longer goes through get-default; it points to "Run an uploaded package".
  • Run an uploaded package: [--project-key <PROJECT_KEY>] in the usage line, and the "No project named" bullet now says to leave it out, name Data.ProjectKey to the user, and stop on a permission_denied about the default project (Rule 10).

Merge order

Merge after UiPath/cli#6094, so the skill never tells an agent to drop --project-key on a 1.206 CLI that still needs it.

Verification

  • check-skill-links.mjs and check-sensitive-content.py pass.
  • check-skill-verbs.py skills/uipath-test: the same 8 findings in SKILL.md before and after this change (all already on 1.206).
  • Not run: check-cli-verbs.py (needs PyYAML locally); CI runs it.

🤖 Generated with Claude Code

…ct (#4630)

Port of #4630 to release/v1.206, for the CLI change in UiPath/cli#6094:
with no project named, `uip tm run --type package` leaves out
--project-key and runs in the tenant's default project, and the agent
tells the user Data.ProjectKey. Other new work with no project still
goes through `get-default`.

The 1.206 SKILL.md is laid out differently from main (bullets and its
own Default project section), so the same two edits are applied by
hand to the 1.206 text.

(ported from commit 48e6cae)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@KunalSM99
KunalSM99 requested a review from a team as a code owner November 16, 2026 07:18
@github-actions

github-actions Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Claude finished @KunalSM99's task in 49s —— View job


Summary

This PR ports #4630 to release/v1.206 by hand. When a user asks to run a package and names no project, the skill now tells the agent to leave out --project-key and report Data.ProjectKey, instead of running get-default first. Creating test cases, test sets or requirements with no project named still goes through get-default.

Change-by-Change Review

1. skills/uipath-test/SKILL.md:35 — Default project bullet

OK. "or to run a package" is removed from the get-default sentence, and a new sentence sends package runs to "Run an uploaded package". The wording matches the original commit 48e6cae91, adjusted for the 1.206 bullet layout. Quick Start step 2 (line 187) still sends "new work with no project named" to the Default project section, and that section now points package runs onward, so the routing holds together.

2. skills/uipath-test/SKILL.md:105 — usage line

OK. [--project-key <PROJECT_KEY>] uses square brackets to mark the flag optional. The skill's other usage lines show optional flags the same way, and the placeholder style is unchanged.

3. skills/uipath-test/SKILL.md:107 — "No project named" bullet

OK. The text matches the main-branch wording word for word:

  • leave out the flag;
  • the run uses the default project and creates it if needed, like get-default;
  • tell the user Data.ProjectKey;
  • stop on permission_denied (Rule 10).

The behaviour of creating a default project matches the `` comment at line 34, so the agent is not left with an unflagged side effect.

What's Missing

  • No coder_eval task covers a package run with no project named. Both run_package_ci_smoke.yaml and run_package_failing_smoke.yaml give a project in the prompt, and their command_pattern requires --project-(key|id). They still pass after this change. The original feat(uipath-test): run a package with no project in the default project #4630 on main shipped without a task too, so this is not a regression; a follow-up on main would be worth having. Low.

Area Ratings

Area Status Notes
Frontmatter OK Unchanged
E2E Tests OK Existing run-package tasks still apply; the no-project path has no test (see above)
Skill Body OK Faithful port of both edits
References & Assets OK Same section on a single page; no new links
Repo Hygiene OK One file, scoped to the skill; no secrets; uipath-test has no flavor overrides

Issues for Manual Review

  • Merge order: do not merge before UiPath/cli#6094 is released on the 1.206 CLI line. Otherwise a 1.206 CLI that still requires --project-key would reject the command the skill now tells agents to run.
  • CLI behaviour: I could not check the claim that Data.ProjectKey is present in the --output json envelope on 1.206. It needs confirming against the cherry-picked CLI.

Conclusion

Approve, subject to the merge-order condition above. This is a correct, minimal port with no issues found in the diff.

@ganeshborle
ganeshborle merged commit 157496d into release/v1.206 Nov 16, 2026
50 checks passed
@ganeshborle
ganeshborle deleted the cherry-pick/v1.206-uipath-test-run-default-project branch November 16, 2026 07:55
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.

2 participants