Repository navigation
Conversation
lelia
had a problem deploying
to
socket-firewall
October 21, 2026 02:23 — with
GitHub Actions
Failure
lelia
force-pushed
the
dc-larsen/emudhra-ca-trust
branch
from
October 21, 2026 02:51
fe2451d to
8e82296
Compare
lelia
force-pushed
the
lelia/release-3.4.1
branch
from
October 21, 2026 02:52
42e477a to
b387d57
Compare
lelia
had a problem deploying
to
socket-firewall
October 21, 2026 02:52 — with
GitHub Actions
Failure
lelia
had a problem deploying
to
socket-firewall
October 21, 2026 03:13 — with
GitHub Actions
Failure
lelia
force-pushed
the
lelia/release-3.4.1
branch
from
October 21, 2026 20:39
0b5ff6c to
b781ad0
Compare
Stamps [Unreleased] as [3.4.1], bumps the version files and uv.lock, and synchronizes the current-release references across README.md and docs/**. Also bumps the Socket Python CLI in the heavy and app-tests images from 2.9.0 to 2.11.2, which carries the eMudhra CA fix for the CLI's own image.
Points all three images at the trivy-dist toolchain rebuild of v0.73.0 on Go 1.26.10 (SocketDev/trivy-dist#24). The digest is a placeholder until that image is published. check_core_tools now ranks -socket.N GHCR tags above their base version and drops the suffix from the upstream Go module purl.
Upstream's v0.76.1 is built on Go 1.27.3, so Basics takes Socket's build of it instead of a 0.73.0 toolchain rebuild (SocketDev/trivy-dist#25). The digest stays a placeholder until that build publishes.
uv.lock moves once socketdev 3.6.1 is on PyPI.
lelia
force-pushed
the
lelia/release-3.4.1
branch
from
October 21, 2026 21:46
73a58ee to
b79d835
Compare
2.11.3 requires certifi>=2026.10.19 and SDK 3.6.1, which requires it too. Relocked with uv 0.12.1, the version the images use, which also restores lock format revision 3.
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Draft. Do not merge yet. Staged release for the eMudhra intermediate CA fix. Stacked on #128; retarget to
mainonce #128 merges.What's in it
ca-certificates >= 20250419+deb13u1in both images, certifi 2026.10.19, a certifi floor on heavy's system interpreter, and a Node 22.23.4 floor in both images.uv.lock. Both requirecertifi>=2026.10.19; 2.11.3 also upgrades its own image's pip (Stop trusting the compromised eMudhra intermediate CAs socket-python-cli#415, #418). Relocked with uv 0.12.1, which keeps lock format revision 3 likemain.TRIVY_VERSION, tests and docs are updated; the digest is a placeholder.scripts/prep_release.py --version 3.4.1: version files,uv.lock,action.yml(socket-basics:3.4.1), README and docs.check_release_docs.py --checkandsync_release_version.py --checkpass.Before this ships
main.v3.6.1: patchedcertifi,uvandvirtualenv; requirecertifi>=2026.10.19socket-sdk-python#120).0.76.1(SocketDev/trivy-dist#25), replace the placeholdersha256:0000…digest inDockerfile,Dockerfile.heavyandapp_tests/Dockerfile(markedTODO(release 3.4.1)). Image builds fail until then. Run regression tests on the final images, since this is three upstream minor versions; trivy-dist#25 has the CLI and report-format review.check_core_tools.pykeeps its-socket.Nsupport for future toolchain rebuilds.NODE_OPTIONS.uv sync --frozenverifies hashes; OpenGrep and the Socket npm CLI carry no CA store of their own (the npm CLI runs on the image's Node). The broader refresh stays in chore(deps): refresh bundled tool pins and make them Dependabot-readable #118.scripts/prep_release.py --version 3.4.1 --date <ship date>to restamp the CHANGELOG date (currently 2026-10-20).v3.4.1to trigger publish.Verification for the final build
On the published
3.4.1and3.4.1-heavyimages, every client should fail certificate verification against bothdv-g3b-emudhra.we-have-a-problem.comanddv-g3b-aaa-emudhra.we-have-a-problem.com:docker run --rm --entrypoint sh ghcr.io/socketdev/socket-basics:3.4.1 -c 'H=dv-g3b-emudhra.we-have-a-problem.com; curl -sS -o /dev/null -w "curl %{http_code}\n" https://$H/; /socket-basics/.venv/bin/python -c "import requests; print(\"python\", requests.get(\"https://$H/\").status_code)"; node -e "fetch(\"https://$H/\").then(r=>console.log(\"node\",r.status),e=>console.log(\"node rejects\"))"; trivy image --download-db-only --db-repository $H/trivy-db 2>&1 | tail -1'Local builds of #128's branch already pass this for the standard and heavy images (results in the #128 thread).