You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have decided not to maintain system-requirements-lock.txt as a checked-in file. Keeping the lock file synchronized with requirements.txt introduces significant maintenance overhead, and the lock file itself is inherently environment specific. Dependency resolution can vary across operating systems, Python versions, hardware configurations, and over time as package repositories evolve, making a static shared lock file difficult to keep accurate.
Instead, we will move to a runtime-generated approach. The system dependencies will be resolved in the target environment when needed, likely by installing the system requirements into a temporary environment and generating the fully resolved dependency list using pip freeze. This ensures that conflict detection is performed against the actual installed dependency set for the current environment rather than against a potentially stale or inaccurate lock file.
Activity
SarahAsad23 commentedon Jun 10, 2026
/take
chenlica commentedon Jun 10, 2026
@SarahAsad23 If this issue is related to an earlier issue/PR, please add the link here.
SarahAsad23 commentedon Jun 10, 2026
The system-requirements-lock.txt file was introduced in PR #4902. A related issue: #5034
refactor(amber): Remove system-requirements-lock.txt (apache#5613)
refactor(amber): Remove system-requirements-lock.txt (apache#5613)