Dependency versioning

Libraries teach new skills to your robots. Often, you will use external libraries. You make libraries available to your robot by adding Python packages as dependencies in the conda.yaml configuration file.

What version of dependencies is my robot using?

You can determine which version of dependencies, such as Python packages, your robot is using by viewing the conda.yaml configuration file:

channels:
  - conda-forge
dependencies:
  - python=3.9.13
  - pip=22.1.2
  - pip:
      - rpaframework==16.0.0

In this case, the robot is using python version 3.9.13, pip version 22.1.2, and rpaframework version 16.0.0.

Always use fixed version numbers (such as 16.0.0) instead of floating numbers (12.*) to make your projects more stable. Fixed versions mitigate the risk of some dependency updating without you knowing it.

Semantic versioning

Robocorp uses Semantic versioning principles. The version number has three components: MAJOR.MINOR.PATCH

Changes in each of these numbers signal different levels of possible internal updates to the package:

• MAJOR updates can change or remove core existing features or functionality and therefore can cause compatibility issues with earlier major versions of the package.
• MINOR updates can add new features, but should not break any of the package's existing functionality.
• PATCH updates can fix existing features or bugs, but should neither add to nor break any of the package's existing functionality.

Determining the exact version of dependencies in use

In VS Code:

NOTE: This requires the Robocorp Visual Studio Code extensions to be installed in VS Code.

1. Run the robot.
2. The dependencies are shown in the Terminal panel.
3. The environment_*_freeze.yaml in the output directory shows the exact dependency versions.

When and how should I update my dependencies?

Update the dependency versions whenever you see an update that will be useful to you (new feature, bug fix, performance boost...).

View the RPA Framework release notes!