Conversation
"A 15-minute timeout-minutes to every CI job" in 26.2 was applied to ci.yml only. release.yml and the Dependabot workflow were left on GitHub's 6 hour default, in all five Zostera repos. A job that hangs rather than fails burns the whole allowance before anyone notices. release.yml gets 20 rather than 15. It does everything the ci.yml build job does, then uploads to PyPI, and a bound that fires during a publish is worse than one that never fires at all. Dependabot gets 15, against a runtime in seconds. PACKAGING.md now says every job in every workflow carries a bound, so the rule does not get read as "every job in ci.yml" a second time. Found while bounding the jobs in observation/wrnpro and observation/meetnetten, where the same gap was wider. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This branch has not been deployed
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.
26.2 added "a 15-minute
timeout-minutesto every CI job", and that got applied toci.ymlonly.release.ymland the Dependabot workflow were left on GitHub's 6 hour default, in all five Zostera repos. A job that hangs rather than fails burns the whole allowance before anyone notices it is stuck, which is the case the bound exists for, andrelease.ymlis the workflow that publishes to PyPI.release.ymlgets 20 rather than 15. It does everything theci.ymlbuildjob does,uv build, twine check, check-manifest, check-wheel-contents and both smoke tests, and then uploads to PyPI. A bound that fires part way through a publish is worse than one that never fires, so it gets headroom over the job it otherwise mirrors. The Dependabot job gets 15 against a runtime measured in seconds.PACKAGING.md now states the rule as every job in every workflow, with the values and the reason, so it does not get read as "every job in
ci.yml" a second time.Found while bounding jobs in observation/wrnpro and observation/meetnetten, where the same gap was wider. Both files are on PACKAGING.md's copy-verbatim list, so this propagates unchanged to the four siblings once the current queue of pull requests there is merged.
🤖 Generated with Claude Code