Skip to content

Pin GitHub Actions versions and add scheduled failure reporting #13

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
oblomov-dev merged 3 commits into from
Jul 29, 2026
Merged

Pin GitHub Actions versions and add scheduled failure reporting #13

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
160c326
docs: record history-growth policy for the committed core mirror
claude Jul 29, 2026
b6a01f4
ci: open an issue when the scheduled update_cap run fails
claude Jul 29, 2026
ac91a35
ci: pin third-party actions to commit SHAs
claude Jul 29, 2026
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
4 changes: 2 additions & 2 deletions .github/workflows/test.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,8 +20,8 @@ jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v5
- uses: actions/setup-node@v5
- uses: actions/checkout@fbc6f3992d24b796d5a048ff273f7fcc4a7b6c09 # v5.1.0
- uses: actions/setup-node@a0853c24544627f65ddf259abe73b1d18a591444 # v5.0.0
with:
node-version: 22
# the builder's own dev deps (jest for the script tests, eslint)
Expand Down
8 changes: 6 additions & 2 deletions .github/workflows/update_cap.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,7 @@ on:

permissions:
contents: write
issues: write # report-scheduled-failure opens an issue on a red nightly

concurrency:
group: update-cap
Expand All @@ -35,10 +36,10 @@ jobs:
run:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v5
- uses: actions/checkout@fbc6f3992d24b796d5a048ff273f7fcc4a7b6c09 # v5.1.0
with:
ref: main
- uses: actions/setup-node@v5
- uses: actions/setup-node@a0853c24544627f65ddf259abe73b1d18a591444 # v5.0.0
with:
node-version: 22
# the builder's own dev deps (jest for the script tests, run by `npm test`)
Expand Down Expand Up @@ -112,3 +113,6 @@ jobs:
git push origin HEAD:main
echo "published to cap2UI5/cap2UI5@main: $(git rev-parse --short HEAD)" >> "$GITHUB_STEP_SUMMARY"
fi
- name: report scheduled failure as issue
if: failure() && github.event_name == 'schedule'
uses: abap2UI5/abap2UI5/.github/actions/report-scheduled-failure@main
12 changes: 12 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,6 +74,18 @@ npm run build_cap # assemble + publish
(secret `ACTION_KEY_APP`; skipped with a warning when unset).
- `test`: PR gate — assemble from the committed mirror + `npm ci` + jest.

## History growth of the committed mirror — recorded policy

`update_cap` commits the refreshed `run/input/core` mirror on every run,
so bot commits accumulate nightly. Same trade-off and same policy as
documented in builder-abap2UI5-js AGENTS.md ("History growth of the
committed build trees"): the committed mirror stays (diff-reviewable,
reproducible, no artifact storage), bot-commit history is disposable and
may be squashed to a baseline by a maintainer when clone size becomes a
nuisance, and nothing may ever resolve old commits of this repo —
`UPSTREAM_HEAD` and `run/input/UPSTREAM_COMMIT` are change-detection
tokens / upstream shas, not references into this repo's history.

## Rules

- Never edit the cap2UI5 app repo directly — change `src/` here and
Expand Down