Skip to content

fix(deps, ci, v1.2): refresh expired and expiring action pins - #7581

Merged
xuang7 merged 1 commit into
apache:release/v1.2from
xuang7:ci/v12-refresh-action-pins
Aug 12, 2026
Merged

fix(deps, ci, v1.2): refresh expired and expiring action pins#7581
xuang7 merged 1 commit into
apache:release/v1.2from
xuang7:ci/v12-refresh-action-pins

Conversation

@xuang7

@xuang7 xuang7 commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

What changes were proposed in this PR?

CI on release/v1.2 fails at workflow parse because the branch pins coursier/cache-action v8.1.0, whose ASF actions-allowlist entry expired on 2026-08-05 (v8.1.1 was approved in July with a one-month grace for the old SHA). The docker action pins on the branch have allowlist expiry dates of Aug 16/19, so they are bumped in the same pass instead of waiting for the next breakage.

All five pins move to the SHAs main already uses (allowlisted, exercised on main daily):

Action v1.2 pin New pin (= main)
coursier/cache-action v8.1.0 (expired Aug 5) v8.1.1
docker/build-push-action v7.1.0 (expires Aug 16) v7.3.0
docker/login-action v4.1.0 (expires Aug 16) v4.4.0
docker/setup-buildx-action v4.0.0 (expires Aug 16) v4.2.0
docker/setup-qemu-action v4.0.0 (expires Aug 19) v4.2.0

Only uses: lines change; no job logic is touched.

Any related issues, documentation, discussions?

Fixes #7572.

How was this PR tested?

YAML validated; every new SHA checked against the current apache/infrastructure-actions allowlist (actions.yml): the coursier/build-push/buildx/qemu entries carry no expiry, and login-action matches main's Oct 16 lease. The coursier bump is exercised by this PR's own sbt CI legs; the docker pins are the same SHAs main's daily image publishing runs.

Was this PR authored or co-authored using generative AI tooling?

Generated-by: Claude Code (Opus 4.8)

coursier/cache-action v8.1.0's ASF allowlist entry expired on
2026-08-05, so every workflow on this branch fails at parse. The
docker action pins expire on 2026-08-16/19. Bump all five to the
allowlisted SHAs main already uses, following apache#6990's targeted
approach for setup-sbt.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@github-actions github-actions Bot added the ci changes related to CI label Aug 11, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Automated Reviewer Suggestions

Based on the git blame history of the changed files, we recommend the following reviewers:

  • Contributors with relevant context: @Yicong-Huang
    You can notify them by mentioning @Yicong-Huang in a comment.

@codecov-commenter

codecov-commenter commented Aug 11, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 52.87%. Comparing base (33d5f1b) to head (91f801e).

Additional details and impacted files
@@                Coverage Diff                 @@
##             release/v1.2    #7581      +/-   ##
==================================================
- Coverage           52.88%   52.87%   -0.01%     
+ Complexity           2529     2528       -1     
==================================================
  Files                1078     1078              
  Lines               42367    42367              
  Branches             4565     4565              
==================================================
- Hits                22404    22400       -4     
- Misses              18646    18647       +1     
- Partials             1317     1320       +3     
Flag Coverage Δ *Carryforward flag
access-control-service 64.35% <ø> (ø)
agent-service 34.36% <ø> (ø)
amber 52.94% <ø> (-0.03%) ⬇️
computing-unit-managing-service 1.65% <ø> (ø)
config-service 56.06% <ø> (ø)
file-service 61.72% <ø> (ø)
frontend 47.32% <ø> (ø)
pyamber 93.07% <ø> (ø)
python 90.88% <ø> (ø) Carriedforward from 33d5f1b
workflow-compiling-service 58.69% <ø> (ø)

*This pull request uses carry forward flags. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@xuang7
xuang7 requested a review from Yicong-Huang August 11, 2026 22:05
@Yicong-Huang Yicong-Huang changed the title ci(v1.2): refresh expired and expiring action pins fix(deps, ci, v1.2): refresh expired and expiring action pins Aug 12, 2026
@Yicong-Huang
Yicong-Huang added this pull request to the merge queue Aug 12, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Aug 12, 2026
@xuang7
xuang7 added this pull request to the merge queue Aug 12, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Aug 12, 2026
@xuang7
xuang7 added this pull request to the merge queue Aug 12, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Aug 12, 2026
@xuang7
xuang7 added this pull request to the merge queue Aug 12, 2026
Merged via the queue into apache:release/v1.2 with commit 9ead9e9 Aug 12, 2026
51 of 53 checks passed
@xuang7
xuang7 deleted the ci/v12-refresh-action-pins branch August 12, 2026 21:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci changes related to CI

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants