Repository navigation
Ensure reproducible beamline deployments by pinning dependencies from uv.lock #1678
Description
Currently, deploying bluesky module in scratch on a beamline resolves dependencies directly from pyproject.toml. Because dependency can pull in newer updates,, this can lead to unexpected environment between release tags.
To ensure production releases remain stable and fully reproducible, an option should be available to install locked dependency versions derived from uv.lock rather than resolving dependencies dynamically at deploy time.
Acceptance Criteria
- A release deployment can be reproduced identically at any point in the future.
Activity
Relm-Arrowny commentedon Sep 22, 2026
No longer requred #1679 (comment) and I was wrong so it is back.
oliwenmandiamond commentedon Oct 7, 2026
As discussed in our standup today, this feels like a greater symptom of #1533. Our release is not a true release because the dependencies of blueapi and our plan repository release have their own dependencies and can drift and break because these two sets of dependencies are not tied together.
If Blueapi was a library rather than the application, the plan repository would be the single source of dependencies as this would be the application and have blueapi as a dependency. Making a release of our plan repository which pins blueapi would be a true release and the environment in theory can be replicated every time