ENH: Update nightly runner to use a local install of python 3.13#96
Conversation
WalkthroughThe nightly health workflow now uses Python 3.13 for Windows virtual environment creation and Ubuntu dashboard generation. Test execution, artifact production, dashboard generation, and status publishing remain unchanged. ChangesNightly health runtime
Estimated code review effort: 1 (Trivial) | ~3 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/nightly-health.yml:
- Around line 58-61: Update the virtual-environment setup command in the
workflow’s Python installation step to use a guaranteed pip-capable Python
installation, such as the installed Python 3.13 executable under C:\Program
Files\Python313, instead of the undefined embeddable runtime path. Preserve the
existing venv target and Python 3.13 requirement.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 77837632-bb6d-4d83-a864-c4e2aa4bcd9e
📒 Files selected for processing (1)
.github/workflows/nightly-health.yml
Use an embedded python in the action directory on the remote machine.
Summary by CodeRabbit