Skip to content

Track Package.resolved so Dependabot can detect updates#14

Merged
luizmb merged 1 commit into
mainfrom
fix/dependabot-track-package-resolved
May 21, 2026
Merged

Track Package.resolved so Dependabot can detect updates#14
luizmb merged 1 commit into
mainfrom
fix/dependabot-track-package-resolved

Conversation

@luizmb
Copy link
Copy Markdown
Owner

@luizmb luizmb commented May 21, 2026

Summary

  • Removes *.resolved from .gitignore so SwiftPM's pinning file is committed.
  • Commits the current Package.resolved.

Why

Dependabot's Swift ecosystem uses Package.resolved as the version baseline. With it excluded, Dependabot could only see the manifest requirement (from: \"1.8.1\") — never what was actually pinned — so FP updates published since 1.8.1 were never surfaced as PRs.

Restoring the resolved file gives Dependabot something to diff against.

Test plan

  • git ls-files Package.resolved returns the path
  • After merge: Insights → Dependency graph → Dependabot → "Check for updates" runs cleanly; next FP tag opens a PR within 24h

🤖 Generated with Claude Code

Dependabot's Swift ecosystem uses Package.resolved as the version baseline.
With *.resolved excluded by .gitignore, the file was never committed, so
Dependabot could only see the manifest requirement (from: "1.8.1") — not what
was actually pinned — and never opened FP-update PRs even after several FP
tags shipped.

Removing the *.resolved exclusion and committing the current Package.resolved
restores the baseline.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@luizmb luizmb merged commit 5e20b09 into main May 21, 2026
2 checks passed
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.

1 participant