ci(shared): bump vendored ci files - #150
Closed
galoybot-app[bot] wants to merge 1 commit into
Closed
galoybot-app[bot] wants to merge 1 commit into
galoybot-app[bot] wants to merge 1 commit into
Conversation
galoybot
force-pushed
the
bump-shared-tasks
branch
from
September 19, 2026 12:36
b2ae13b to
46fc4dd
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
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.
Bump Shared Tasks
This PR syncs in this repository, shared CI tasks from concourse-shared.
Note
Low Risk
Mostly vendored CI pins and fuzz runaway guards; no application runtime or auth/data-path changes, though fuzz jobs may exit earlier on hung targets.
Overview
Syncs vendored shared CI from galoy-concourse-shared at commit
8aaee2b(includes the spelling workflow fix).Spell check: GitHub Actions now use
crate-ci/typos@v1instead of@master, in both the main workflow and the vendored copy.Fuzz pipeline: The Concourse fuzz task gets a job-level wall-clock timeout of
fuzz_seconds + 2hso wedged work (nix, tar, etc.) cannot run forever while still allowing corpus/artifact upload steps after a per-target watchdog trip.fuzz.shadds a per-target GNUtimeout/gtimeoutbound atFUZZ_SECONDS + FUZZ_WATCHDOG_GRACE_SECONDS(grace default 1800s), documents the new env var, maps failed workers back to target names, and broadens failure messaging from “crash” to crash/OOM/timeout.Reviewed by Cursor Bugbot for commit 46fc4dd. Bugbot is set up for automated code reviews on this repo. Configure here.