Skip to content

fix(ci): unbreak workflow YAML and add a complete actions.lock #11

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
hyperpolymath merged 1 commit into from
Aug 27, 2026
Merged

fix(ci): unbreak workflow YAML and add a complete actions.lock #11

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions .github/workflows/actions.lock
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
# This file is machine-generated by `gh actions-lock`.
# Do not edit by hand; run `gh actions-lock` to update.
# Docs: https://gh.io/actions-lockfile
version: 'v0.0.2'
workflows:
'.github/workflows/secret-scanner.yml': []
'.github/workflows/push-email-notify.yml':
- 'dawidd6/action-send-mail@v3.12.0'
dependencies:
'dawidd6/action-send-mail@v3.12.0':
ref: 'v3.12.0'
commit: 'sha1-6e502825a508b867ab2954ad6343b68787624c01'
owner_id: 9713907
repo_id: 222439721
3 changes: 2 additions & 1 deletion .github/workflows/push-email-notify.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,5 @@
# SPDX-License-Identifier: MPL-2.0
# This workflow is managed by gh actions-lock.
# Dormant push-email notification. ARMED by setting the repo variable
# PUSH_EMAIL_ENABLED=true (the single on/off switch). Addresses are pre-filled;
# sending needs the org SMTP secrets (SMTP_HOST/PORT/USER/PASS). Inherited by
Expand All @@ -15,7 +16,7 @@
runs-on: ubuntu-latest
steps:
- name: Send push notification email
uses: dawidd6/action-send-mail@6e502825a508b867ab2954ad6343b68787624c01 # pinned
uses: dawidd6/action-send-mail@v3.12.0

Check warning on line 19 in .github/workflows/push-email-notify.yml

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

.github/workflows/push-email-notify.yml#L19 

An action sourced from a third-party repository on GitHub is not pinned to a full length commit SHA. Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release.

@codacy-production codacy-production Bot Aug 27, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🔴 HIGH RISK

Pinning third-party actions to a full commit SHA is a security best practice. While tags like v3.12.0 are convenient, they are mutable and could be changed to point to malicious code. Using a SHA ensures the integrity of the action used in your CI/CD pipeline.

Try running the following prompt in your IDE agent:

Find the commit SHA for dawidd6/action-send-mail version v3.12.0 and update the uses statement in .github/workflows/push-email-notify.yml to use that SHA instead of the tag, while keeping @v3.12.0 as a comment for reference.

See Issue in Codacy

with:
server_address: ${{ secrets.SMTP_HOST }}
server_port: ${{ secrets.SMTP_PORT }}
Expand Down
2 changes: 2 additions & 0 deletions .github/workflows/secret-scanner.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,5 @@
# SPDX-License-Identifier: MPL-2.0
# This workflow is managed by gh actions-lock.
# Calls the estate's shared secret scanner (gitleaks + rust-secrets +
# shell-secrets). Added because this repository had NO leak scanning at all.
#
Expand All @@ -13,6 +14,7 @@ concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
permissions:
actions: read
contents: read
jobs:
secret-scan:
Expand Down