Skip to content

ci: make pixi lockfile updates predictable (#2298) - #2780

Open
jpascucci-nv wants to merge 6 commits into
NVIDIA:mainfrom
jpascucci-nv:issue2298
Open

ci: make pixi lockfile updates predictable (#2298)#2780
jpascucci-nv wants to merge 6 commits into
NVIDIA:mainfrom
jpascucci-nv:issue2298

Conversation

@jpascucci-nv

@jpascucci-nv jpascucci-nv commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

Description

closes #2298

  • Fail CI when a committed pixi.lock is stale (pixi lock --check per workspace).
  • Run pixi source-build CI with PIXI_LOCKED=1 so jobs install from the lockfile instead of refreshing it.
  • Open monthly (and on-demand) lockfile-only PRs, one workspace at a time, via pixi update --no-install.
  • Document the contributor policy in CONTRIBUTING.md.
  • Backreved setup-pixi to a rev that actually runs.

Used codex(auto-balance) for changes.

Checklist

  • New or existing tests cover these changes.
  • The documentation is up to date with these changes.

@copy-pr-bot

copy-pr-bot Bot commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

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

Contributors can view more details about this message here.

@github-actions github-actions Bot added the CI/CD CI/CD infrastructure label Sep 8, 2026
@jpascucci-nv
jpascucci-nv requested a review from rwgk September 8, 2026 17:00
@jpascucci-nv
jpascucci-nv marked this pull request as ready for review September 8, 2026 17:00
@jpascucci-nv jpascucci-nv added this to the cuda.core 1.3.0 milestone Sep 8, 2026

@rwgk rwgk left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a human-only review.

Comment thread .github/workflows/ci-pixi-lockfile-freshness-check.yml
Comment thread .github/workflows/ci-pixi-lockfile.yml Outdated
Comment thread .github/workflows/ci-workflow-health.yml
Comment thread .github/workflows/ci-pixi-source-test.yml Outdated
Comment thread .github/workflows/ci-pixi-source-test.yml
Comment thread CONTRIBUTING.md Outdated
Comment thread .github/workflows/ci-pixi-lockfile-refresh.yml Outdated
Comment thread .github/workflows/ci-pixi-lockfile-refresh.yml Outdated
Comment thread .github/workflows/ci-pixi-lockfile-refresh.yml
Comment thread .github/workflows/ci-pixi-lockfile-freshness-check.yml
@github-actions

github-actions Bot commented Sep 8, 2026

Copy link
Copy Markdown

- Fail CI when a committed `pixi.lock` is stale (`pixi lock --check` per workspace).
- Run pixi source-build CI with `PIXI_LOCKED=1` so jobs install from the lockfile instead of refreshing it.
- Open monthly (and on-demand) lockfile-only PRs, one workspace at a time, via `pixi update --no-install`.
- Document the contributor policy in `CONTRIBUTING.md`.

Used codex(auto-balance) for changes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI/CD CI/CD infrastructure

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Make pixi lockfile updates predictable and auditable

2 participants