Skip to content

hotfix: add RZ1 SHA pin enforcement audit trail to RELEASE_NOTES - #22

Open
AnuarRazii wants to merge 1 commit into
mainfrom
copilot/fix-github-actions-sha-rule-error
Open

hotfix: add RZ1 SHA pin enforcement audit trail to RELEASE_NOTES#22
AnuarRazii wants to merge 1 commit into
mainfrom
copilot/fix-github-actions-sha-rule-error

Conversation

@AnuarRazii

@AnuarRazii AnuarRazii commented Jul 7, 2026

Copy link
Copy Markdown
Owner

All six GitHub Actions workflow files introduced in the initial repository bootstrap used version-tag references (@v4, @v7, @V3) that are blocked by the repository's Actions policy, which requires every action to be pinned to a full-length commit SHA.

Root cause (PR #10 base commit d5cb904):
The action actions/checkout@v4 is not allowed because all actions
must be pinned to a full-length commit SHA.

Fix applied (PR #10, merged 2026-07-02T16:21:36Z):

  • actions/checkout@v4 → @34e114876b0b11c390a56381ad16ebd13914f8d5
  • actions/github-script@v7 → @f28e40c7f34bde8b3046d885e986cb6290c5673b
  • github/codeql-action/init@v3 → @411c4c9a36b3fca4d674f06b6396b2c6d23522c6
  • github/codeql-action/analyze@v3 → @411c4c9a36b3fca4d674f06b6396b2c6d23522c6

Workflows fixed: compliance.yml, RZ1-validate.yml, codeql.yml,
dco.yml, security.yml, release-immutability.yml

All RZ1 governance engines confirmed green at merge commit 083d0fb.

This hotfix commit serves as the signed audit record per CONTRIBUTING.md § 9 — Traceability and Auditability.

Pull Request

Description

Please provide a concise description of the changes in this PR.

Type of Change

  • Bug fix
  • New feature
  • Documentation improvement
  • Policy clarification
  • Framework enhancement
  • Other (please describe)

Related Issues

Closes #(issue number) – if applicable

Changes Made

Please describe the specific changes:

  • Created dashboard.html as a minimal governance visualization layer
  • Connected frontend to audit API endpoints (/audit/events, /risk/score)
  • Implemented periodic refresh for near real-time monitoring
  • Supports transparency and observability of RZ1 governance system

Alignment with Ethical AI MY Principles

Ethical Alignment

How do these changes align with our ethical principles?

  • Fairness – Promotes equitable treatment
  • Transparency – Improves clarity and documentation
  • Accountability – Strengthens responsibility mechanisms
  • Privacy – Protects personal data
  • Benefit – Contributes to positive impact

Explanation:

Testing and Validation

How have you tested these changes?

  • Dashboard tested in browser
  • API endpoints (/audit/events, /risk/score) returning valid data
  • Auto-refresh verified

Documentation

Have you updated relevant documentation?

  • README updated
  • Policy documents updated
  • Comments added to code
  • Examples provided
  • No documentation changes needed

Attribution

Please confirm:

  • You are the author or have permission to contribute this work
  • All sources and references are properly attributed
  • You understand this work will be released under CC BY 4.0

Code of Conduct

  • I have read and agree to follow the Code of Conduct
  • I understand the community standards
  • I commit to respectful engagement

Additional Context

Please provide any additional context or information that would be helpful for reviewers.


Reviewer Checklist

  • Changes align with ethical framework
  • Documentation is clear and complete
  • No harmful or discriminatory content
  • Follows community standards
  • Properly attributed
  • Technical quality is acceptable
  • Ready to merge

Thank you for contributing to Ethical AI MY!

All six GitHub Actions workflow files introduced in the initial
repository bootstrap used version-tag references (@v4, @v7, @V3)
that are blocked by the repository's Actions policy, which requires
every action to be pinned to a full-length commit SHA.

Root cause (PR #10 base commit d5cb904):
  The action actions/checkout@v4 is not allowed because all actions
  must be pinned to a full-length commit SHA.

Fix applied (PR #10, merged 2026-07-02T16:21:36Z):
  - actions/checkout@v4    → @34e114876b0b11c390a56381ad16ebd13914f8d5
  - actions/github-script@v7 → @f28e40c7f34bde8b3046d885e986cb6290c5673b
  - github/codeql-action/init@v3  → @411c4c9a36b3fca4d674f06b6396b2c6d23522c6
  - github/codeql-action/analyze@v3 → @411c4c9a36b3fca4d674f06b6396b2c6d23522c6

Workflows fixed: compliance.yml, RZ1-validate.yml, codeql.yml,
  dco.yml, security.yml, release-immutability.yml

All RZ1 governance engines confirmed green at merge commit
083d0fb.

This hotfix commit serves as the signed audit record per
CONTRIBUTING.md § 9 — Traceability and Auditability.

Signed-off-by: Anuar Razii <anuarrazii@outlook.my>

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Adds a signed audit-trail entry to RELEASE_NOTES.md documenting the RZ1 GitHub Actions SHA-pin enforcement hotfix (PR #10), capturing the blocked tag usage, the pinned SHAs applied, and the before/after commits for traceability.

Changes:

  • Added a new “Hotfix: v1.0.1 — RZ1 SHA Pin Enforcement” section to Release Notes.
  • Documented affected workflows/actions and the specific pinned SHAs applied in PR #10.
  • Recorded an audit trail (detected/fixed commits + governance framework reference) to support traceability requirements.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread RELEASE_NOTES.md
Comment on lines +9 to +11
**Hotfix reference:** `hotfix/rz1-sha-pin-enforcement-audit`
**Applied by:** Anuar Razii \<anuarrazii@outlook.my\>
**Governance engines affected:** RZ1 Compliance Engine, RZ1 Validate, CodeQL Security Analysis, RZ1 Security Enforcement, DCO Check, Release Immutability Guard
Comment thread RELEASE_NOTES.md

### Audit Trail

- **Detected at:** `d5cb904972a84211f4e3ba6f4ed2299121ca27fe` — 4 workflows failing
Comment thread RELEASE_NOTES.md

---

## Hotfix: v1.0.1 — RZ1 SHA Pin Enforcement (2026-07-02)
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