Skip to content

ci: fix missing astral-sh/setup-uv@v8 by pinning to fac544c07dec837d0ccb6301d7b5580bf5edae39#1

Merged
qkal merged 2 commits into
masterfrom
fix/ci/pin-setup-uv
Jun 19, 2026
Merged

ci: fix missing astral-sh/setup-uv@v8 by pinning to fac544c07dec837d0ccb6301d7b5580bf5edae39#1
qkal merged 2 commits into
masterfrom
fix/ci/pin-setup-uv

Conversation

@qkal

@qkal qkal commented Jun 18, 2026

Copy link
Copy Markdown
Owner

Summary

Fixes the CI failure caused by astral-sh/setup-uv@v8 resolving to a missing action ref. The upstream action now publishes immutable release tags such as v8.2.0 instead of the major tag v8.

What changed

Pinned to SHA to avoid breakage from future action tag changes; consider updating to a named release later.

Testing

  • Validated refs/tags/v8 is absent and refs/tags/v8.2.0 exists with git ls-remote.
  • Ran uv --version locally.
  • Ran uv sync --extra dev.
  • Ran uv run ruff check ..
  • Ran uv run pyright --pythonpath .venv/bin/python.
  • Ran uv run pytest -v (239 passed).
  • Ran git diff --check and git diff --cached --check.

Please trigger/confirm a quick CI run; this should now proceed beyond the Install uv step and run lint, typecheck, and tests.


Open in Devin Review

Summary by CodeRabbit

  • Chores
    • Updated CI workflow infrastructure for improved build consistency and reliability.

@coderabbitai

coderabbitai Bot commented Jun 18, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@qkal, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 53 minutes and 56 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: b05af370-03c2-43d7-b215-578ec50a6cb3

📥 Commits

Reviewing files that changed from the base of the PR and between 5e08e3e and 2c6b77f.

📒 Files selected for processing (1)
  • tests/unit/test_runner.py
📝 Walkthrough

Walkthrough

The astral-sh/setup-uv GitHub Action reference in the CI workflow's test job is changed from the floating v8 tag to a pinned commit SHA on line 26 of .github/workflows/ci.yml.

Changes

CI Action Pin

Layer / File(s) Summary
Pin setup-uv action to commit SHA
.github/workflows/ci.yml
The astral-sh/setup-uv action reference is changed from the v8 tag to a specific pinned commit SHA.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐇 A tag once floated, now it's nailed down tight,
A SHA replaces "v8" overnight.
No drifting actions, no surprise deploy,
Just one fixed commit — oh, what pure joy!
Hop hop, the workflow is locked up right! ✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: pinning astral-sh/setup-uv to a specific commit SHA to fix a CI failure caused by the missing v8 tag.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ 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/ci/pin-setup-uv

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

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

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Open in Devin Review

@qkal

qkal commented Jun 19, 2026

Copy link
Copy Markdown
Owner Author

CI update after opening this PR:

  • The original failure is fixed: Install uv completed successfully with the pinned setup-uv SHA.
  • The workflow proceeded through dependency install, lint, and type check successfully.
  • The run now fails later in uv run pytest -v on tests/unit/test_runner.py::test_command_runner_uses_safe_argument_subprocess_and_records_previews, where Linux CI reports PATH=/usr/bin instead of the test expectation PATH=/bin.

Run: https://github.com/qkal/techne/actions/runs/27796727296

@qkal qkal merged commit f4c7cd0 into master Jun 19, 2026
3 checks passed
@qkal qkal deleted the fix/ci/pin-setup-uv branch June 19, 2026 00:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant