Set the new env for clusTCR - #105
Merged
Merged
Conversation
erohinaelena
approved these changes
Aug 25, 2026
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.
Greptile Summary
The PR adds and publishes a focused Python 3.12.10 environment for the clusTCR Clustering block.
3.12.10-clustcrruntime package with pinned clusTCR, scientific-computing, FAISS, and Polars dependencies.3.12.10-clustcrenvironment.immunewatch-clustcrand imported throughimw_clustcr. Version 1.0.1 is added as the environment’s primary workload dependency.noDeps— Builder policy that installs a selected package without resolving its declared dependencies. The new profile applies it to clusTCR so its Python-3.12-incompatible SciPy metadata does not control resolution.faiss-cpu==1.15.0.strictMissing.3.12.10-clustcr.Confidence Score: 5/5
The PR appears safe to merge because its runtime package, supported platform roots, CI matrix, workspace registration, catalogue reference, and release metadata are internally aligned.
No concrete blocking or independently actionable non-blocking defect remains after checking dependency-resolution semantics and the package’s build and publication wiring.
Important Files Changed
Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart LR Config[clusTCR dependency profile] --> Builder[Shared Python runtime builder] Builder --> LinuxX64[Linux x64 root] Builder --> LinuxArm64[Linux ARM64 root] Builder --> MacX64[macOS x64 root] Builder --> MacArm64[macOS ARM64 root] LinuxX64 --> Runtime[Published clusTCR runtime package] LinuxArm64 --> Runtime MacX64 --> Runtime MacArm64 --> Runtime Runtime --> Catalogue[3.12.10-clustcr catalogue entrypoint] Catalogue --> Block[clusTCR Clustering block]Reviews (1): Last reviewed commit: "Set the new env for clusTCR" | Re-trigger Greptile
Context used (6)