RCC v21.4.2 released

RCC v21.4.2 is a security release. The robot templates now pin OpenSSL to the long-term support line, so new robots no longer get an end-of-life OpenSSL.

There are no functional changes and no breaking changes in RCC itself. Upgrading is a straight swap.

Why

The templates that rcc robot initialize uses did not pin OpenSSL, so the conda solver picked the newest version that Python allows. python=3.12.8 accepts any OpenSSL 3.x from 3.4.0, so environments built from the templates got OpenSSL 3.6.5. The OpenSSL 3.6 line has reached end of life and no longer receives security fixes.

What changed

• The standard, python and extended templates pin openssl=3.5.9. OpenSSL 3.5 is the long-term support line.
• The environment that rcc configure speedtest builds pins the same version.

Existing robots

This release changes only the templates that new robots start from. A robot you have already created keeps its own conda.yaml, and gets OpenSSL 3.6 if that file does not pin OpenSSL. To move such a robot to the long-term support line, add the pin under dependencies:

RCC builds a new environment the next time the robot runs.

To check which OpenSSL an environment uses, run this in it, for example with rcc task shell:

Getting v21.4.2

Signed and pre-built executables are available directly:

• Windows — rcc.exe
• macOS (Apple Silicon) — rcc
• Linux — rcc

macOS and Windows builds are code-signed, and the macOS build is notarized. RCC supports macOS on Apple Silicon only; Intel builds were discontinued in v21.0.0.

The complete changelog ships inside the executable itself. Run rcc docs changelog to read the full list of changes for the version you have installed.