You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ruby -e 'require "yaml"; YAML.load_file(".github/workflows/release.yml"); puts "yaml ok"'\n\nThis PR was generated by an AI coding assistant.
Note
Low Risk
Single CI timeout tweak with no application, auth, or release-script logic changes.
Overview
Raises the release job limit in .github/workflows/release.yml from 10 to 30 minutes so tag releases can finish GitHub release creation, asset uploads, and related steps without being canceled at the old cap.
Reviewed by Cursor Bugbot for commit 7cb3407. Bugbot is set up for automated code reviews on this repo. Configure here.
Summary by CodeRabbit
Release Notes
Chores
Improved release process stability by increasing timeout allowance for release job completion.
timeout-minutes for the release job is changed from 10 to 30.
Estimated code review effort
🎯 1 (Trivial) | ⏱️ ~1 minutes
Poem
🐇 Ten minutes felt rushed, the release cried with doubt,
So I hopped to the YAML and stretched the time out.
Now thirty whole minutes to build, tag, and ship—
No more timed-out deploys on this bunny's trip!
✨ Carrots for all when the release goes through!
This PR bumps the release workflow job's timeout-minutes from 10 to 30 to prevent the job from being canceled prematurely when asset uploads or release-note generation run long.
Increases timeout-minutes on the release job from 10 to 30 in .github/workflows/release.yml.
Confidence Score: 5/5
Minimal-risk one-line change to a CI configuration value; no logic is altered.
The change is a single integer bump in a YAML workflow file. A runaway release job would now be allowed to run for up to 30 minutes before being canceled, which matches the stated real-world observation and is a common, safe ceiling for release workflows that upload artifacts.
No files require special attention.
Important Files Changed
Filename
Overview
.github/workflows/release.yml
Increases the release job timeout from 10 to 30 minutes to prevent premature cancellation during asset uploads and release-note generation.
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
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
releaseworkflow job timeout from 10 minutes to 30 minutesContext
The release job in https://github.com/jdx/mise/actions/runs/27487189873/job/81247212839 was canceled after running a little over 10 minutes, while it was still creating the GitHub release. The current timeout is too tight for release publishing when asset upload or release-note generation runs long.
Validation
ruby -e 'require "yaml"; YAML.load_file(".github/workflows/release.yml"); puts "yaml ok"'\n\nThis PR was generated by an AI coding assistant.Note
Low Risk
Single CI timeout tweak with no application, auth, or release-script logic changes.
Overview
Raises the
releasejob limit in.github/workflows/release.ymlfrom 10 to 30 minutes so tag releases can finish GitHub release creation, asset uploads, and related steps without being canceled at the old cap.Reviewed by Cursor Bugbot for commit 7cb3407. Bugbot is set up for automated code reviews on this repo. Configure here.
Summary by CodeRabbit
Release Notes