[lvrach]

What changed

The Profiles IDE image now pins the TLS trust for Python tooling:

• apt-get upgrade and an explicit ca-certificates install take Ubuntu's 20260816ubuntu0.22.04.1 store, which drops the emSign roots.
• pip>=26.2.2 and certifi>=2026.10.23 replace the plain pip3 install --upgrade pip.
• uv 0.13.4 is copied from ghcr.io/astral-sh/uv by index digest into /usr/local/bin. setup.sh finds it and skips its unpinned astral.sh install. uv keeps its bundled roots, so its trust does not depend on the apt layer.
• uv lock --upgrade-package 'certifi>=2026.10.23' raises certifi in the profiles-mcp v1.4.0 lock before setup.sh, so uv sync and uv run in start.sh keep it.

Why

The IDE runs pip and uv at run time, and the bundled profiles-mcp server resolves mcp[cli] from PyPI on every start. The current image trusts the compromised eMudhra intermediate chains in pip 26.1.2, uv 0.11.26, certifi 2025.04.26 (profiles-mcp venv) and the Ubuntu CA store. Ticket: SEC-707 (parent SEC-607).

How to verify

The image was verified locally with the probe harness on a Mac mini. The build used the same base digest and the same apt, pip, uv and profiles-mcp steps as this Dockerfile (arm64). Results:

• versions: ca-certificates 20260816ubuntu0.22.04.1, pip 26.2.2, uv 0.13.4, certifi 2026.10.19 in the system Python and in the profiles-mcp .venv;
• pip and uv fail TLS against both eMudhra test hosts and resolve from pypi.org;
• stdlib ssl and certifi reject the test hosts and reach a normal host;
• uv run --with "mcp[cli]" in the profiles-mcp project starts and keeps certifi 2026.10.19.

The Dockerfile carries pins only. It has no build-time version checks.

Release path

This is a fix: commit, so release-please opens the next patch release PR. Publishing that release runs build-docker.yaml, which pushes profiles-code-server:v<version> to ECR. Then the rudder:release-profiles-ide-infra flow bumps RSOURCES_EXT_WHT_CODESERVERIMAGENAME in rudderstack-operator operator-helm/valuefiles/values.sources.yaml (prod runs v1.20.3 today) and the image warmers in rudder-devops helm-charts/cluster-overprovisioner/values.*.yaml (v1.20.2 today).

Not covered

• The image runs Python 3.10, which is end of life. Moving to a supported Python is a follow-up.
• The certifi bump in the profiles-mcp repo lock. The image raises it at build time instead.
• The full image (code-server .deb, Cline extension, pb-proxy) was not built locally. CI builds it on both architectures.

certifi 2026.10.23 also drops the emSign C1 and C3 roots. The pin skips the 7-day Dependabot cooldown because this is a security fix.

🤖 Generated with Claude Code

[Copilot]

🔵 Needs a closer look

Security-sensitive trust changes need human confirmation of full-image builds and certificate-rejection behavior on both supported architectures.

No open issues 🎉

What changed in this PR

Updates the Profiles IDE image’s Python tooling and certificate trust to reject eMudhra chains, including the bundled profiles-mcp environment.

Changes:

• Upgrades Ubuntu packages and explicitly installs ca-certificates.
• Sets minimum pip and certifi versions and copies uv 0.13.4 from a digest-pinned image.
• Updates certifi in the profiles-mcp lockfile before setup so subsequent syncs retain the updated version.

File	Description
Dockerfile	Updates system and Python trust dependencies and the profiles-mcp lockfile.

_{Review effort: Balanced}

[github-actions]

Docker Preview Images Ready

Preview Docker images have been built for this PR:

ECR (internal):

docker pull 422074288268.dkr.ecr.us-east-1.amazonaws.com/rudderstack/profiles-code-server:pr-239

Image Details:

• Tag: pr-239
• Platforms: linux/amd64, linux/arm64

Test the image:

docker run --rm -p 8080:8080 422074288268.dkr.ecr.us-east-1.amazonaws.com/rudderstack/profiles-code-server:pr-239

Note: These preview images will be overwritten on subsequent pushes to this PR.