fastlane warns on every run that it will soon require Ruby 3.3.0 or newer; both release workflows pinned 3.2. Bumping now means that break lands on a quiet commit instead of mid-release. fastlane 2.234 already supports 3.3 and no gem in either lockfile is version-sensitive, so this stands alone — the lockfiles are unchanged. Also gives the weekly dry-run somewhere to report. It broke on the release after 5.1.0 and stayed red for weeks without surfacing, which is the failure mode of any heartbeat nobody reads: it looks green by default. Scheduled failures now open a tracking issue, or comment on the existing one for each week it stays red. Dispatched runs are excluded — those are already in front of whoever started them. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| ci.yml | ||
| claude-code-review.yml | ||
| claude.yml | ||
| gh-release.yml | ||
| pr-check.yml | ||
| release-dryrun.yml | ||
| store-release.yml | ||