@scott-huberty @drammock A little while back, we moved the uv lockfile updating for the 'old' CI job from the scheduled_updates workflow to the autofix workflow, because of concern that dependencies could be updated outside of a scheduled_updates PR, but that it would take until the next scheduled_updates PR run for the new dependencies to be reflected in the 'old' lockfile.
#13704 includes the pixi.toml and pixi.lock updating in the scheduled_updates workflow, so there could be a similar issue there with out-of-date pixi info between scheduled_updates workflow runs. I know #13704 was a while in the making, so I wonder whether this was a hold-over from when uv lockfile updating was also present there?
Could we consolidate things by also moving the pixi updates to the autofix workflow?
@scott-huberty @drammock A little while back, we moved the uv lockfile updating for the 'old' CI job from the
scheduled_updatesworkflow to theautofixworkflow, because of concern that dependencies could be updated outside of ascheduled_updatesPR, but that it would take until the nextscheduled_updatesPR run for the new dependencies to be reflected in the 'old' lockfile.#13704 includes the pixi.toml and pixi.lock updating in the
scheduled_updatesworkflow, so there could be a similar issue there with out-of-date pixi info betweenscheduled_updatesworkflow runs. I know #13704 was a while in the making, so I wonder whether this was a hold-over from when uv lockfile updating was also present there?Could we consolidate things by also moving the pixi updates to the
autofixworkflow?