Add Dependabot for GitHub Actions and SwiftPM - #402
Merged
Conversation
Third-party actions went years without a bump. At the 3.0 release five of them were between two and six majors behind, and two workflows were already broken by drift nobody was watching for: ci.yml pinned an Xcode that no longer exists on the runner image, and release.yml did the same. Minor and patch updates are grouped into a single PR per ecosystem so a quiet week costs one review rather than nine. Majors stay ungrouped, since those are the ones that break workflows and deserve individual attention. Verified Package.resolved is parseable before relying on it: the file is schema version 1 (Swift 5.5 era), and dependabot-core's Swift parser supports versions 1, 2 and 3, mapping v1 to the repositoryURL/package keys this file uses. No regeneration needed. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe pull request adds Dependabot version 2 configuration for weekly GitHub Actions and Swift dependency updates. It applies labels, groups minor and patch updates, and limits open pull requests to five. ChangesDependabot configuration
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related issues
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
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
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.
First of the maintenance-automation batch. Closes part of #384.
Why
Third-party actions in this repo went years without a bump. At the 3.0 release, five were between two and six major versions behind:
Apple-Actions/import-codesign-certssoftprops/action-gh-releasepeter-evans/create-pull-requestdawidd6/action-homebrew-bump-formulareecetech/version-incrementAnd two workflows were already broken by drift nobody was watching for —
ci.ymlandrelease.ymlboth pinned Xcode versions that no longer exist onmacos-latest, the second of which would have failed during a release.Dependabot is the cheapest fix for this class of rot, and unlike a drift detector it arrives with the fix already written.
Grouping
Minor and patch updates are grouped into one PR per ecosystem, so a quiet week costs one review instead of nine. Majors stay ungrouped — those are the ones that break workflows and deserve individual attention.
Weekly, Mondays. Labels reuse the repo's existing
dependenciesandgithub_actions.On
Package.resolvedThis repo's
Package.resolvedis schema version 1 — the Swift 5.5-era format, where pins live underobject.pinswithrepositoryURL/packagekeys rather than the modern top-levelpinswithlocation/identity.Rather than assume Dependabot could read it, I checked
dependabot-core:v1 is supported and maps to exactly the keys this file uses, so no regeneration is needed. Regenerating would have churned pinned versions for no benefit.
Not in this PR
SHA-pinning the actions (the other half of #384) comes after the lint workflow lands — it rewrites every
uses:line and would conflict with anything adding CI steps.🤖 Generated with Claude Code
Summary by CodeRabbit