Repository navigation
Conversation
zlareb1
force-pushed
the
fix/security-dependency-pins
branch
from
November 20, 2026 20:08
94b4ca9 to
a0b478a
Compare
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
zlareb1
force-pushed
the
fix/security-dependency-pins
branch
2 times, most recently
from
November 20, 2026 23:01
d0dd728 to
2723496
Compare
Lock complete helper dependency sets and require verified wheels for workflow and course installs. Use the shared pinned uv action for SDK package builds and a multi-platform digest for the document benchmark base. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Route the workflow module invocation through the existing fake installer and assert that helper installs require hashes. Preserve SDK prerelease and final PEP 440 checks. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Shared client schema reads run with an independent context. Record only decision-tagged statements while retaining unbounded decision reads as failures. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com> (cherry picked from commit 57327d5) Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
zlareb1
force-pushed
the
fix/security-dependency-pins
branch
from
November 21, 2026 00:08
2723496 to
be0ec73
Compare
This branch has not been 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.
Related: #1076
Changelog category (leave one):
Why
Version constraints alone do not verify downloaded helper packages. CI, release preparation and the course setup install Python tooling from complete hash-checked requirement locks. The SDK packaging matrix uses the existing commit-pinned installer action and shared tool version. The document-parsing benchmark base uses a multi-platform image digest.
Scope and risk
Replicated-erasure lease provisioning and its unit regression controls are on main. This branch preserves them unchanged. It also scopes person-query observations to the authorization decision, retaining unbounded-read negative controls. No production authorization, lease or erasure rule changes.
This changes helper installation commands and their requirement inputs and generated locks. Runtime server and SDK dependency declarations are unchanged. Dify testing and the course setup retain their declared dependency ranges as inputs, while their installation locks fix every resolved dependency and artifact hash. Hash checking and binary-only installation fail if a compatible verified wheel is unavailable. The benchmark image digest is the registry's multi-platform index, including amd64 and arm64. Sandbox requirement changes trigger the existing image checks.
Compatibility, rollout and rollback
uv pip compile <input> --generate-hashes --universal --python-version <version> --no-header --no-annotate --output-file <lock>with Python 3.12 for Dify and 3.11 for the other locks.Tests
This head matches the exact three-way composition of the preceding qualified source and current main. The erasure fixture and its canonical unit regression module are inherited from main. On this composed head, all three erasure unit cases, scoped Ruff, Python formatting, committed-range whitespace and public-body prose checks pass. Workflow parsing, hash-pin and shell checks pass. The workflow retains the hash-locked dependencies and setup action pins alongside the upstream credential-persistence restriction. Full required hosted CI and a fresh independent whole review remain required for this exact head.
Earlier feature qualification
The following feature-specific results were recorded before this composition. They are prior-source receipts, not new tests of this composed head.
pip download --require-hashes --only-binary=:all:on a clean private Python 3.12 environment, checking dependency closure and downloaded wheel hashes. No fresh download is claimed for this composition.python -m pip. The test keeps its PEP 440 assertions and checks the hash-required install arguments. The preceding CI run exposed that its original fake handled only the bare pip command.sh -n; Ruff, the prose checker andgit diff --checkpass.AI assistance in the code (leave one; writing this description with AI is fine):
AI-generated: Codex changed helper installation commands, generated requirement locks and verified the hashes and workflow syntax.
I can explain every line of this diff and how it interacts with the rest of Loom.
Checklist