Repository navigation
chore: refresh uip CLI catalog (1.207.0-dev.9850) - #4747
Conversation
Re-keys tests/scripts/studioweb-browser-commands.json to the new catalog's command paths.
|
Claude finished @uipreliga's task in 21s —— View job SummaryAutomated catalog refresh. The only change is the Change-by-Change Review1.
|
| Area | Status | Notes |
|---|---|---|
| Frontmatter | OK | No skill files touched |
| E2E Tests | OK | Not applicable |
| Skill Body | OK | No skill files touched |
| References & Assets | OK | Only the timestamp changed |
| Repo Hygiene | OK | No secrets or paths; change stays within the refresh's scope |
Issues for Manual Review
None found. Optionally, the refresh workflow could skip opening a PR when only generated_at changes, which would cut daily noise.
Conclusion
No issues found. Safe to auto-merge once checks pass.
Automated refresh against
@uipath/cli@1.207.0-dev.9850. The catalog has 1881 reachable verbs after installing all available plugins.Also re-keys
tests/scripts/studioweb-browser-commands.jsonto the new catalog's command paths: mentions only moved between keys, none were added.Merges automatically once all checks pass (handled by
automerge-catalog-refresh.yml). If a check fails, the failure is real drift:.claude/rules/cli-renames.md./lint-taskand the gate annotations surface the affected references.studioweb-browser-commands.test.mjs(in Build and inspect every skill package): a studioweb mention the new catalog turned from prose into a command. Fix the guidance, or allowlist the mention intests/scripts/studioweb-browser-commands.json. Not acli-renames.mdcase.