fix(ci): regenerate pixi.lock during semantic-release version bumps

[Abdelsalam-Abbas]

Summary

• Adds build_command = "pixi lock" to [tool.semantic_release] in pyproject.toml so the lockfile is regenerated before semantic-release commits the version bump
• Installs pixi (without running install) in the release workflow so pixi lock is available
• Regenerates the currently stale pixi.lock from the 0.4.2 bump

Context

The 0.4.2 release bumped version in pyproject.toml but didn't update pixi.lock. Since sampleworks is an editable self-dependency, the version change invalidated the lockfile, breaking all CI jobs with lock-file not up-to-date with the workspace.

Test plan

• CI passes on this PR (proves the regenerated lockfile is valid)
• Next semantic-release run includes an updated pixi.lock in the version commit

Summary by CodeRabbit

• Chores
  • Updated release automation configuration with pixi integration and explicit build command for improved release process reliability.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: aa4d0ce3-8928-4b6f-a1be-4dd145574dea

📥 Commits

Reviewing files that changed from the base of the PR and between 95e8b86 and da483ce.

⛔ Files ignored due to path filters (1)

• pixi.lock is excluded by !**/*.lock

📒 Files selected for processing (2)

• .github/workflows/release.yml
• pyproject.toml

---

📝 Walkthrough

Walkthrough

Two configuration changes were made to integrate pixi into the release process: a new workflow step installs pixi before semantic release runs, and a build_command directive adds pixi lock to the semantic-release configuration in pyproject.toml.

Changes

Cohort / File(s)	Summary
Release Workflow Setup .github/workflows/release.yml	Added pixi installation step using prefix-dev/setup-pixi@v0.8.8 action with run-install: false flag before semantic release execution.
Semantic Release Configuration pyproject.toml	Added build_command = "pixi lock" to [tool.semantic_release] section to run pixi lock during release builds.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• feat(ci): automated semantic release and versioned Docker tags #144: Introduced the initial python-semantic-release setup in the release workflow and pyproject.toml configuration that this PR extends with pixi integration.

Suggested reviewers

• marcuscollins

Poem

🐰 With pixi locked and ready to go,
Our releases now flow smooth as snow,
A gentle install, a build command true,
Dependencies bundled, the workflow renewed! ✨🔐

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and specifically describes the main change: adding pixi.lock regeneration during semantic-release version bumps via workflow and configuration updates.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/release-pixi-lock

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}