Skip to content

chore: pin GitHub Actions workflows to full commit SHAs#53

Merged
feanil merged 1 commit into
openedx:mainfrom
irfanuddinahmad:pin-actions-to-sha
May 30, 2026
Merged

chore: pin GitHub Actions workflows to full commit SHAs#53
feanil merged 1 commit into
openedx:mainfrom
irfanuddinahmad:pin-actions-to-sha

Conversation

@irfanuddinahmad

Copy link
Copy Markdown
Contributor

Pins all uses: action refs to their full commit SHA with the version tag preserved as a comment. Part of org-wide SHA-pinning migration: openedx/.github#165

@codecov

codecov Bot commented May 19, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.04%. Comparing base (b5eae7c) to head (09b7d78).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #53   +/-   ##
=======================================
  Coverage   93.04%   93.04%           
=======================================
  Files          16       16           
  Lines         503      503           
  Branches       18       18           
=======================================
  Hits          468      468           
  Misses         24       24           
  Partials       11       11           
Flag Coverage Δ
unittests 93.04% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@feanil
feanil merged commit 00aa944 into openedx:main May 30, 2026
9 checks passed
feanil pushed a commit that referenced this pull request Jul 15, 2026
The dedicated SHA-pinning PR (#53) pinned every other action in this
workflow (checkout, python-semantic-release, publish-action,
upload-artifact, download-artifact, setup-node) but missed this one --
likely because @release/v1 looks like a branch name rather than the
@vx version-tag pattern the other lines used, so it slipped past
whatever tool/regex did that sweep.

This isn't just a style nit: openedx/xblocks-core's real release just
failed with "docker: manifest unknown" because @release/v1 resolved to
a commit whose Docker image wasn't published on ghcr.io yet. Since this
repo is the reference implementation every "modernize Python tooling"
migration copies (openedx/public-engineering#506), the same unpinned ref
propagates into every repo that follows this template.

pypa/gh-action-pypi-publish's own README shows @release/v1 in its usage
examples, but its own "pro tip" note recommends pinning to a tag or SHA
rather than tracking a branch pointer -- there's no upstream guidance
that this action is meant to be an exception to normal pinning practice.

Co-authored-by: Irfan Ahmad <irfan.ahmad@A006-01919.local>
Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
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.

3 participants