Skip to content

CI: artifact timeouts (variable, default 20), no Publish on Dependabot PRs, actions v1.2.0 - #280

Merged
bernardladenthin merged 2 commits into
mainfrom
claude/upbeat-hypatia-z1ie5h
Nov 9, 2026
Merged

bernardladenthin merged 2 commits into
mainfrom
claude/upbeat-hypatia-z1ie5h

Conversation

@bernardladenthin

@bernardladenthin bernardladenthin commented Nov 9, 2026 •

Copy link
Copy Markdown
Owner

An artifact transfer step has no timeout of its own. In java-llama.cpp's Publish run 42675444364, an upload-artifact step hung for hours, and the only limit was GitHub's 360 minutes.

Artifact timeouts

  • The 7 upload-artifact / download-artifact steps in publish.yml carry timeout-minutes: ${{ fromJSON(env.ARTIFACT_TIMEOUT_MINUTES) }}.
  • The top-level env reads ARTIFACT_TIMEOUT_MINUTES: ${{ vars.ARTIFACT_TIMEOUT_MINUTES || '20' }}: the repository variable if it is set, otherwise 20 minutes.
  • repository-checks runs common/check-artifact-timeouts from bernardladenthin/actions v1.2.0.

No Publish on Dependabot PRs

  • startgate, which every job needs, now has if: github.event_name != 'pull_request' || github.actor != 'dependabot[bot]'. So a PR that Dependabot opens or rebases skips all jobs.
  • Such a run gets none of the repository's secrets, and Dependabot rebases each of its PRs on every change of main.
  • The pipeline still runs on the merge to main, on a push by a person to the branch, and on a dispatch on the branch.

actions v1.2.0: every action and reusable workflow of bernardladenthin/actions is pinned at 68dde11.

Checked locally against actions v1.2.0:

  • templates: 0 problems
  • release gate: 0 violations
  • run scripts: 0 errors
  • artifact timeouts: 7 steps, 0 problems
  • publication wiring: 0 problems
  • YAML parses

CLAUDE.md and CHANGELOG are updated.

🤖 Generated with Claude Code

https://claude.ai/code/session_01S8cAMcSFpCBzLfQXyyLd32

…lt 20

An artifact transfer step has no timeout of its own. In java-llama.cpp's Publish run 42675444364 an
upload-artifact step hung for hours after a build of a minute and a half, and GitHub's 360 minutes
were the only limit; the longest transfer measured over two complete runs of that pipeline took
18 s. A job-level limit would have to cover the job's build and would not catch the hang sooner.

Each workflow that transfers artifacts now reads the repository variable in its top-level env,

    ARTIFACT_TIMEOUT_MINUTES: ${{ vars.ARTIFACT_TIMEOUT_MINUTES || '20' }}

and every upload-artifact / download-artifact step carries
timeout-minutes: ${{ fromJSON(env.ARTIFACT_TIMEOUT_MINUTES) }}, so the value can be changed in the
repository's settings without a commit. This is the layout bernardladenthin/actions'
common/check-artifact-timeouts checks (bernardladenthin/actions#16); the check joins
repository-checks with that release. scorecard.yml (a template; scorecard-action refuses a
top-level env) is left out.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01S8cAMcSFpCBzLfQXyyLd32
@coderabbitai

coderabbitai Bot commented Nov 9, 2026 •

Copy link
Copy Markdown

Important

  • Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 3d0cd7a9-5ecd-401b-9607-36a30ae738bf
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

…ests, actions v1.2.0

- repository-checks runs common/check-artifact-timeouts of bernardladenthin/actions v1.2.0: every
  upload-artifact / download-artifact step carries timeout-minutes: ${{ fromJSON(env.ARTIFACT_TIMEOUT_MINUTES) }}
  and the workflow's top-level env reads the repository variable with the default 20.
- startgate, which every job of publish.yml needs, is skipped for a pull request Dependabot opens or
  rebases (github.event_name == 'pull_request' && github.actor == 'dependabot[bot]'), so all jobs
  are skipped. Such a run gets none of the repository's secrets and Dependabot rebases each of its
  pull requests on every change of main. The merge to main runs the pipeline; a push of a person to
  the branch, or a dispatch on it, runs it too.
- Every action and reusable workflow of bernardladenthin/actions is pinned at v1.2.0 (68dde11).

Checked locally with actions v1.2.0: templates, release gate, run scripts, artifact timeouts and
the publication wiring report no problem; the workflows load as YAML.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01S8cAMcSFpCBzLfQXyyLd32
@bernardladenthin bernardladenthin changed the title CI: artifact transfers time out after ARTIFACT_TIMEOUT_MINUTES, default 20 CI: artifact timeouts (variable, default 20), no Publish on Dependabot PRs, actions v1.2.0 Nov 9, 2026
@sonarqubecloud

sonarqubecloud Bot commented Nov 9, 2026

Copy link
Copy Markdown

@bernardladenthin
bernardladenthin merged commit 9e65417 into main Nov 9, 2026
13 of 16 checks passed
@bernardladenthin
bernardladenthin deleted the claude/upbeat-hypatia-z1ie5h branch November 9, 2026 21:29

This branch was successfully deployed

No deployments
startgate — 2f4e2ca2 Deployed Nov 9, 2026 by bernardladenthin via Start gate (abort window) #651
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants