Manage Package: RunTime Rule; How does it work

Can somebody explain Manage Package RunTime rule while installing a activity package. How does it work?
What is the difference between “Strict” & "Lowest applicable Version "?
image

have a look here

it introduces into the rules and its resolutions

For details look here:

1 Like

Thanks @ppr and @Areej_fatima , I have checked Manage Dependency documentation on UiPath.
But not able to understand the practical scenario, how to use it.
Can you give me example if possible.

I tested as below.

Steps:

  1. Created custom Library, Published to local folder.
    (Created 3 version of same, 1.0.1 , 1.0.2, 1.0.3)
  2. Added the path to Package Feeds, to use it in the project.
  3. Installed Custom Library package of Version 1.0.1 with RunTime Rule as “Lowest application version”
  4. Opened the Uipath project to run main worklfow.
    Package loaded to below folder automatically for use.

C:\Users\XXXXX.nuget\packages\testlibrary
1.0.1
1.0.2
1.0.3

Project ran successfully.
5. Now i deleted the 1.0.1 version from ( C:\Users\XXXXX.nuget\packages\testlibrary) and unchecked local library path from feeds, to avoid restoring 1.0.1 package to .nuget folder.

  1. I ran it again, but this time on project load, its giving me dependency error.

But it should refer to higher version > 1.0.2 as per the RunTime rule, which is not happening.
So can you please guide here, what i am missing or what is the correct way or scenario to use this.

Please refer below screenshot.

Higher version >1.0.1 is available.

@loginerror Pleas help

I was able to do some close similar replication of your observation
But was forced to do some side check, where it was necessairy to work with the nuget.exe to ensure that changes are applied

as nuget is authored from else one also have a look here:

maybe the existence and the resolution of a package are different independent things