Bump stash/restore to retry-capable revision with fail-on-download#65268
Merged
potiuk merged 2 commits intoapache:mainfrom Apr 18, 2026
Merged
Bump stash/restore to retry-capable revision with fail-on-download#65268potiuk merged 2 commits intoapache:mainfrom
potiuk merged 2 commits intoapache:mainfrom
Conversation
boring-cyborg
Bot
added
area:dev-tools
backport-to-v3-2-test
5 tasks
potiuk
requested review from
amoghrajesh,
ashb,
bugraoz93,
gopidesupavan,
jason810496,
jscheffl and
kaxil
as code owners
potiuk
commented
Apr 14, 2026
kaxil
approved these changes
Apr 14, 2026
Lee-W
approved these changes
Apr 15, 2026
bugraoz93
approved these changes
Apr 15, 2026
Bumps stash/restore and stash/save to the PR apache#716 revision which adds retry-count (default 3) and fail-on-download inputs to stash/restore. Sets fail-on-download: true on the two restore sites where the next step (breeze ci-image load) cannot continue without the artifact: prepare_breeze_and_image and prepare_single_ci_image. Other call sites are true caches (cache-mount, docs inventory, node_modules, prek cache) where a missed download only means a slower/cold run, so they keep the default behaviour.
PR apache/infrastructure-actions#716 (retry-count and fail-on-download inputs on stash/restore) is now merged. Bump the pinned SHA from the old PR branch head to the current main tip. No behaviour change from the previous commit — just keeps the pinned SHA in sync with upstream.
potiuk
force-pushed
the
bump-stash-restore-fail-on-download
branch
from
b50ca51 to
d8394be
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps
apache/infrastructure-actions/stash/restoreandstash/savetothe revision from infrastructure-actions#716,
which adds
retry-count(default 3, retries transientgh run downloadfailures) and
fail-on-downloadinputs to the restore action.Sets
fail-on-download: 'true'on the two restore sites where thefollowing step (
breeze <image>-image load) cannot continue without thedownloaded artifact:
.github/actions/prepare_breeze_and_image/action.yml.github/actions/prepare_single_ci_image/action.ymlAll other call sites are true caches (cache-mount, docs inventory,
node_modules, prek cache) where a failed download only means a slower,
cold run — they keep the default (
fail-on-download: false) so atransient artifact fetch issue won't take the whole job down.
Note: PR apache/infrastructure-actions#716 is not merged yet, so the SHA pin (
d79f0a5b...) pointsat the current head of its branch and will need to be rebumped once the
PR lands on
apache/infrastructure-actionsmain.Was generative AI tooling used to co-author this PR?
Generated-by: Claude Opus 4.6 following the guidelines