Skip to content

Pin GitHub Actions to full-length commit SHAs and add Dependabot cooldown - #106

Merged
Qingtao Li (QingtaoLi1) merged 6 commits into
mainfrom
qingtaoli/fix_security_issue
Oct 28, 2026
Merged

Qingtao Li (QingtaoLi1) merged 6 commits into
mainfrom
qingtaoli/fix_security_issue

Conversation

@QingtaoLi1

Copy link
Copy Markdown
Contributor

Summary

Adapt the hardening proposed in #94 to the current workflows: pin remote
GitHub Actions to full-length commit SHAs and configure weekly, grouped
Dependabot updates with a seven-day cooldown.

Why?

Mutable action tags can be retargeted to different commits, creating a
supply-chain risk. Pinning actions to verified commit SHAs improves
reproducibility and prevents tag changes from silently changing the code
executed by our workflows.

The cooldown provides time for newly published releases to receive
community scrutiny before Dependabot proposes version updates.

What changed?

  • Pin all eight remote action references across the lint, release,
    pre-release, and security regression workflows:
    • actions/checkout: v4.4.0
    • actions/setup-python: v5.6.0
    • DavidAnson/markdownlint-cli2-action: v19.1.0
  • Retain version comments alongside each SHA for readability.
  • Extend the original PR's coverage to the security regression workflow
    and setup-python references added since its base version.
  • Configure weekly, grouped GitHub Actions updates with a seven-day cooldown.
  • Document how to verify and maintain action pins.

No action major versions are upgraded. Local reusable workflow references,
triggers, permissions, security gates, and release steps remain unchanged.

Validation

  • Verified pinned SHAs against upstream release and major-version tags.
  • Validated all four workflow configurations and Dependabot configuration
    against their JSON schemas.
  • Compared parsed workflows against the previous revision to confirm that
    only remote action references changed.
  • Ran the same markdownlint-cli2 version and configuration used by CI:
    26 Markdown files checked, zero errors.
  • Passed git diff --check.

Remote GitHub Actions workflows have not been run for this commit.

Related

Supersedes the changes proposed in #94, adapted to the current codebase.

Require explicit user-local or trusted process provider selection, construct closed CLI invocations, and support known Windows npm entry points without shell wrappers. Make Git hooks opt-in and sync-only, retain provider permission checks, and gate releases on isolated security regressions and artifact checks.
Update multilingual onboarding, local provider selection and migration guidance, opt-in sync hooks, Windows npm compatibility, and approval-aware command templates. Correct CLI help and permission messaging without changing control flow; document the separate Release ZIP permission scope.
Validate directory-entry operations without resolving the final symlink while retaining target checks for content writes. Add sandbox boundary and cleanup regressions, and correct Markdown lint errors in the Windows UTF-8 repro guide.
Resolve product tools outside the workspace, pin CLI self-invocation and use trusted assets for initial encoding. Validate all sh/ps release ZIPs and add isolated execution regressions.
Adapt PR #94 to the current workflows, including security regressions and setup-python references. Preserve existing workflow behavior and document the action update policy.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@QingtaoLi1
Qingtao Li (QingtaoLi1) merged commit a6c83cc into main Oct 28, 2026
5 checks passed
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