Pin setup-python action to a commit hash - part 3

[ShaharNaveh]

extracted from #7491

Summary by CodeRabbit

• Chores
  • Updated CI/CD workflow configuration for improved build reliability.

[coderabbitai]

📝 Walkthrough

Walkthrough

A GitHub Actions workflow step in the PR format pipeline was updated to pin the Python setup action to a specific commit SHA instead of a version tag, maintaining the same Python version configuration.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflow .github/workflows/pr-format.yaml	Updated actions/setup-python from version tag v6.2.0 to pinned commit SHA a309ff8b426b58ec0e2a45f0f869d46889d02405 for reproducibility.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A version tag once did flutter free,
Now pinned to a commit, precise as can be!
No surprises at runtime, no drifting about,
The workflow runs steady—of that there's no doubt! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The title 'Pin setup-python action to a commit hash - part 3' clearly and specifically describes the main change: pinning a GitHub Action to a commit hash, and indicates this is part 3 of a multi-part effort.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.}