Skip to content

Fix: Refresh release trust toolchains - #820

Merged
ashvardanian merged 1 commit into
unum-cloud:main-devfrom
grouville:security/build-toolchains-20261021
Oct 24, 2026
Merged

ashvardanian merged 1 commit into
unum-cloud:main-devfrom
grouville:security/build-toolchains-20261021

Conversation

@grouville

Copy link
Copy Markdown
Contributor

I was checking main-dev release paths after the October 2026 Node and Python certificate-tooling advisories. I did not find a confirmed library-level CVE in USearch, but the workflows and server image were still relying on floating Node 24 and older installer defaults.

This pins Node to 24.22.1, requires pip 26.2.2 before Python test and packaging installs, and refreshes the Docker image's system CA bundle. The image now installs Python packages in an isolated virtual environment, which lets it use the patched pip release without modifying Ubuntu's distro-owned Python installation.

Validation:

  • parsed both modified workflow files as YAML
  • docker build --check .
  • built the complete image from ubuntu:24.04
  • verified pip 26.2.2, the system CA path, and the ucall/usearch imports inside the built image

References: Node.js October 2026 security releases and Python packaging guidance for the emSign incident.

The server image installed `ucall` and `usearch` into Ubuntu's system
Python with `--break-system-packages`. It now creates a venv, upgrades
its pip to pick up a current certificate bundle, and installs both
packages there.
@ashvardanian
ashvardanian force-pushed the security/build-toolchains-20261021 branch from 5b22034 to 0e78035 Compare October 24, 2026 22:21
@ashvardanian
ashvardanian merged commit 3a4cb6e into unum-cloud:main-dev Oct 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants