Add Socket Firewall enforcement to CI and releases#1681
Open
paul-paliychuk wants to merge 2 commits into
Open
Conversation
Route dependency installs and official image builds through Socket while preserving fork PR and public Docker fallbacks. Co-authored-by: Cursor <cursoragent@cursor.com>
paul-paliychuk
temporarily deployed
to
development
July 24, 2026 16:42 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
paul-paliychuk
temporarily deployed
to
development
July 24, 2026 16:42 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
paul-paliychuk
temporarily deployed
to
development
July 24, 2026 16:42 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
sfw can only inspect packages that are actually downloaded, so a release image could ship a package flagged after its layer was first built. Two caches hid dependencies from enforced builds: the BuildKit layer cache skipped the install step outright, and the uv cache mount let uv resolve wheels from disk without contacting PyPI even when the step did run. Enforced builds now set a per-run SOCKET_SCAN_ID to invalidate the install layer and export UV_NO_CACHE=1. Community builds leave SOCKET_SCAN_ID empty and keep both caches. The connectivity smoke test compares a stamp written inside the install layer rather than grepping the build log, since BuildKit echoes instruction text for CACHED steps too, and asserts an unchanged scan id still hits the cache so the check cannot pass vacuously. Co-authored-by: Cursor <cursoragent@cursor.com>
paul-paliychuk
temporarily deployed
to
development
July 24, 2026 21:37 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
paul-paliychuk
temporarily deployed
to
development
July 24, 2026 21:37 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
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
1 participant
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.
Summary
Motivation
Graphiti dependency downloads should use the same Socket policy enforcement as Zep's internal repositories without breaking outside contributors or public image builds that do not have access to Socket credentials.
Impact
Same-repository CI and official release builds use
SOCKET_API_KEY. Fork PRs soft-skip the wrapper, while Docker builds default to direct installs unless release workflows explicitly enable enforcement. The enforcement build argument separates public and release paths in the BuildKit cache.Testing
actionlinton modified workflowsRisks / follow-ups
SOCKET_API_KEYmust remain configured as a repository secret and in thedevelopmentandreleaseenvironments. Fork PRs intentionally run without Socket enforcement because GitHub does not expose secrets to forks.Made with Cursor