Suppose I initially published my project to Orchestrator as version v2.1.0, made further updates, and kept releasing new versions until reaching v2.1.5, which is now stable. If I decide to remove all previous versions that are no longer needed, and re-publish the current stable version as v2.1.0 while deleting the other versions, what potential risks or complications should I consider with this approach?
No risk as such but you will have to make sure you delete the package from machine where it ran. If not deleted and triggered bot, it will run with older version 2.1.0 not the latest you modified.
It’s generally not advisable to overwrite older versions of packages. Doing so can lead to issues since Orchestrator may still reference a higher version, while you’re attempting to publish a lower one. I experienced a similar situation where it caused significant problems until I eventually published a new version with an incremented version number.
If you’re set on removing the older versions, a better approach would be to rename your project and publish it under this new name. Then, create a process based on this newly named version, which would avoid potential versioning conflicts.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.