feat: bump default max_retries from 3 to 12#2
Merged
Conversation
Increases the default push retry budget so concurrent-push scenarios (GitOps fan-out, parallel deploys) succeed without callers having to override the input. Callers can still pass a lower value if desired.
|
🎉 This PR is included in version 1.3.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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
1 participant
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.
Summary
max_retriesinput from3to12inaction.ymlso concurrent-push workloads (GitOps fan-out, parallel deploys) succeed out of the box.Release impact
feat:commit on merge →semantic-releaseproduces v1.3.0 (current latest:v1.2.0) and advances thev1/v1.3floating tags.Test plan
test.ymljobs exercise the action with its default inputs)Releaseworkflow runs onmain, publishesv1.3.0, and updatesv1to point at itNote
Low Risk
Low risk: this only changes the default value of
max_retries(no logic changes), which may slightly increase runtime in worst-case failure scenarios.Overview
Improves out-of-the-box resilience for concurrent pushes by raising the default
max_retriesinput from3to12inaction.yml.Updates the
READMEinputs table to reflect the new default.Reviewed by Cursor Bugbot for commit d4c2dbb. Bugbot is set up for automated code reviews on this repo. Configure here.