chore: disable locked flag to bypass https://github.com/prefix-dev/pixi/issues/5256

[cpcloud]

Temporary workaround to get CI passing

[cpcloud]

/ok to test

[copy-pr-bot]

Auto-sync is disabled for ready for review pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

[greptile-apps]

Greptile Overview

Greptile Summary

This PR adds locked: false to all three GitHub Actions workflows that use the setup-pixi action, bypassing the pixi lockfile to work around pixi issue #5256.

What Changed:

• .github/workflows/conda-python-tests.yaml: Added locked: false parameter
• .github/workflows/docs-build.yaml: Added locked: false parameter
• .github/workflows/simulator-test.yaml: Added locked: false parameter

Impact:
The change is applied consistently across all workflow files that use setup-pixi. By disabling the lockfile, CI will resolve dependencies dynamically instead of using the committed pixi.lock file. This is described as a temporary workaround to get CI passing.

Concerns:

1. Lack of inline documentation: The workflow files don't include comments explaining this is temporary or linking to the upstream issue, which could lead to the workaround becoming permanent
2. Reproducibility: Without the lockfile, different CI runs may resolve slightly different dependency versions, potentially causing inconsistent behavior between runs or between local development (which uses the lockfile by default) and CI
3. Lockfile maintenance burden: The repository maintains an active lockfile (recent PRs ci: relock pixi #712, chore(deps): bump numba-cuda version and relock pixi #707, chore(deps): bump deps in pixi lockfile #693), but CI now ignores it

Recommendation:
Consider adding TODO comments in the workflow files to track when this workaround can be reverted once the upstream pixi issue is resolved.

Confidence Score: 4/5

• This PR is safe to merge as a temporary workaround to unblock CI, but lacks inline documentation for future maintainability
• The changes are minimal, consistent across all affected files, and address a specific CI blocking issue. The implementation is straightforward - simply adding locked: false to bypass the pixi lockfile. However, the score is not 5 because: (1) the temporary nature is only documented in the commit message, not in the workflow files themselves, which could lead to this workaround becoming permanent, and (2) disabling the lockfile introduces potential reproducibility concerns between CI runs and between CI and local development environments. These are maintainability and operational concerns rather than critical bugs, making this safe to merge while acknowledging the technical debt being introduced.
• All three workflow files would benefit from inline TODO comments to ensure this temporary workaround is reverted once the upstream pixi issue is resolved

Important Files Changed

File Analysis

Filename	Score	Overview
.github/workflows/conda-python-tests.yaml	4/5	Added locked: false to setup-pixi action to bypass pixi issue #5256 - temporary workaround that may cause non-reproducible builds
.github/workflows/docs-build.yaml	4/5	Added locked: false to setup-pixi action to bypass pixi issue #5256 - temporary workaround that may cause non-reproducible builds
.github/workflows/simulator-test.yaml	4/5	Added locked: false to setup-pixi action to bypass pixi issue #5256 - temporary workaround that may cause non-reproducible builds

[greptile-apps]

_{3 files reviewed, 3 comments}

_{Edit Code Review Agent Settings | Greptile}