Skip to content

chore: update GitHub Action pins#89

Open
nikzen wants to merge 2 commits into
mainfrom
chore/update-github-actions-shas
Open

chore: update GitHub Action pins#89
nikzen wants to merge 2 commits into
mainfrom
chore/update-github-actions-shas

Conversation

@nikzen

@nikzen nikzen commented May 26, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Update GitHub Actions in workflows to the latest upstream default-branch commit SHAs.
  • Keep existing action paths and only replace refs after @.

Verification

  • Checked generated diff to include only .github/**/*.yml / .github/**/*.yaml workflow action refs.
  • CI on this PR should validate the updated action versions.

@nikzen nikzen requested a review from a team as a code owner May 26, 2026 08:54
Pin listed workflow actions to current upstream default-branch SHAs.
@nikzen nikzen force-pushed the chore/update-github-actions-shas branch from d019ffd to c34ebef Compare May 26, 2026 09:08
@codecov

codecov Bot commented May 26, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.28%. Comparing base (84a327e) to head (6826944).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #89   +/-   ##
=======================================
  Coverage   73.28%   73.28%           
=======================================
  Files           5        5           
  Lines         756      756           
  Branches      145      145           
=======================================
  Hits          554      554           
  Misses        143      143           
  Partials       59       59           

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 84a327e...6826944. Read the comment docs.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Pin all external workflow actions to current upstream default-branch SHAs.

- name: Formatting
uses: famedly/black@stable
uses: famedly/black@6af7d1109693c4ad3af08ecbc34649c232b47a6d

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

why do we use a fork of black, should we move to using the upstream gh action?

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.

2 participants