That’s terrible. I thought the Mass Update Tool would be the solution, but it isn’t. It doesn’t actually work with Orchestrator. It should, or there needs to be some other way to automatically update the dependencies in projects without having to open them in Studio and republish them.
Why on Earth would you remove such a feature? Keeping dependencies updated is a massive hassle, especially now with the new UI object libraries features. This is how it should work:
UI library created
30 Projects created using UI library
Application that’s part of those 30 projects is upgraded, and descriptors change
UI library is updated with new descriptors
All 30 Projects automatically get new version of UI library and continue functioning
But here’s how it actually works:
UI library created
30 Projects created using UI library
Application that’s part of those 30 projects is upgraded, and descriptors change
UI library is updated with new descriptors
All 30 Projects break and won’t run
Open all 30 Projects manually and update dependencies manually
Republish - including our required Change Management process - all 30 automations
Same issue with standard libraries, too. All libraries, activity libraries, UI libraries, standard or custom.
No way to tell Processes to use the latest, no way to bulk update Processes in Orchestrator except for the bulk update tool, but that works out of SVN which presents a problem. The code in SVN may not be the same code that’s in production Orchestrator, so updating in SVN then publishing to Orchestrator is not a safe solution.
Nope. I figure all that tool does is go through your code repository and update the project.json files. You’d still need to open and republish the code with Studio/Orchestrator.
In our organization, we also have to manually upgrade the libraries in all the processes if there is a change in custom library.
Do we have any solution so far?
My mistake - I found out what I did wrong all the time and maybe you did it too: @loginerror@Nikhat_Ansari
In the UiPath Mass Update tool we have to publish to the UiPath Orchestrator Tenant Process Feed, not Library as it set up by default.
So it’s what UiPath say should happen, but even the mass updating tool republishes.
Personally, I’d say this should apply for patch releases and maybe minor releases, but not major ones. I would suggest that this be configurable somehow.
We are using scm git to store library and process code for UiPath cloud
Library Update Process: Developers update the library in UiPath Studio, commit changes to Git, and publish to the development environment. A GitHub Action triggers on commit to download the updated library and deploy it to the production tenant. - work well as expected
Updating Dependencies with the Library: We can identify all repositories using the library as a dependency and update the library version and ProjectVersion in the project.json file. However, we are unsure of the
next steps: should we trigger the solution pipeline to build and publish these changes automatically,
or do developers need to manually open and publish the updated processes/repositories?
is there any way after update project.json we can directly change in orchestrator using some supported api’s ?
Please suggest if anyone crack the solution already.
In my company, we already use a self-hosted Renovate instance for our repos (primarily Go backend services). Renovate works wonders - renovating repos every week with dependency updates automatically.
I’ve been working on extending our bot’s capabilities to also renovate our UiPath process repos in GitHub, covering both internal libraries and official UiPath packages.
Official UiPath libraries work perfectly! When a new update is pushed to packages like UiPath.System.Activities, Renovate creates a PR that we can merge - very cool!
While implementing support for our private NuGet feed (the default one provided by Orchestrator), we hit a roadblock. UiPath’s private NuGet feeds return malformed JSON (UTF-8 BOM) that breaks Renovate’s JSON parser.
I’ve filed a bug report with UiPath Support - excited to see where this leads!
A workaround could be to use our own private NuGet feed - i.e. hosted by GitHub - and plug Renovate into that, but that’s too much work for us right now.
Just wanted to share that automated dependency review pipelines for UiPath ARE possible! The infrastructure works great - we just need UiPath to fix this one API issue.
@loginerror / @alexandru perhaps you can help push on your end? My support ticket has ID 02683772
