Skip to content

Ensure reproducible beamline deployments by pinning dependencies from uv.lock #1678

Description

@Relm-Arrowny

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions