Skip to content

Pin GitHub Actions versions and add scheduled failure reporting - #13

Merged
oblomov-dev merged 3 commits into
mainfrom
claude/repos-overview-etbzqa
Jul 29, 2026
Merged

Pin GitHub Actions versions and add scheduled failure reporting#13
oblomov-dev merged 3 commits into
mainfrom
claude/repos-overview-etbzqa

Conversation

@oblomov-dev

Copy link
Copy Markdown
Member

Summary

This PR improves workflow reliability and observability by pinning GitHub Actions to specific commit hashes and adding automated issue reporting for scheduled job failures.

Key Changes

  • Pin action versions: Updated actions/checkout and actions/setup-node to use full commit hashes with version comments in both update_cap.yml and test.yml workflows for reproducibility and security
  • Add failure reporting: Integrated report-scheduled-failure action in update_cap.yml to automatically open issues when scheduled nightly runs fail
  • Update permissions: Added issues: write permission to update_cap.yml workflow to support issue creation on failures
  • Document mirror policy: Added "History growth of the committed mirror — recorded policy" section to AGENTS.md explaining the trade-offs and maintenance approach for the committed run/input/core mirror, including guidance on squashing bot-commit history when needed

Implementation Details

The failure reporting step only triggers on scheduled events (github.event_name == 'schedule'), preventing noise from manual workflow runs. The pinned action versions improve supply chain security and ensure consistent behavior across workflow runs.

https://claude.ai/code/session_013NA4sHtsK85U1f6YKxP7YW

claude added 3 commits July 29, 2026 14:42
update_cap commits the refreshed run/input/core mirror nightly. Point
to the policy recorded in builder-abap2UI5-js AGENTS.md: the mirror
stays committed, bot-commit history is disposable (squashable to a
baseline), and UPSTREAM_HEAD / UPSTREAM_COMMIT stay change-detection
tokens that are never resolved against this repo's history.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013NA4sHtsK85U1f6YKxP7YW
Same alerting the abap2UI5 org already has (report-scheduled-failure):
a red nightly means the CAP app stops following the core - surface it
instead of failing silently.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013NA4sHtsK85U1f6YKxP7YW
Tag references (@v4/@v5/...) are mutable - a hijacked tag ships
straight into CI. Pin every third-party action to the commit sha the
tag currently resolves to (version noted in a comment), matching the
convention the abap2UI5 org repos already follow. The ecosystem's own
report-scheduled-failure composite stays on @main by convention.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013NA4sHtsK85U1f6YKxP7YW
@oblomov-dev
oblomov-dev merged commit dd6326a into main Jul 29, 2026
1 check 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