Skip to content

Pin swift-build to a fixed revision - #14

Merged
silentswordfish merged 1 commit into
mainfrom
pin-swift-build-dependency
Aug 5, 2026
Merged

silentswordfish merged 1 commit into
mainfrom
pin-swift-build-dependency

Conversation

@silentswordfish

Copy link
Copy Markdown
Contributor

Summary

  • swift-build was floating on branch: "main", so any upstream commit could change build behavior between local dev and CI, or between separate CI runs, with no diff in this repo to explain it.
  • Pins to 7f96ee0e8aa8a35fe84f3e80932eb9e456356d10 via SPM's revision: parameter.

Test plan

  • swift package resolve — resolves swift-build at exactly the pinned revision
  • swift build — succeeds
  • swift test — 40/40 pass
  • swiftlint lint — clean

swift-build was floating on main, so any upstream commit could
silently change build behavior between local dev and CI, or between
CI runs, with no diff in this repo. Pin to
7f96ee0e8aa8a35fe84f3e80932eb9e456356d10 for reproducible builds.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Comment thread Package.swift
],
dependencies: [
.package(url: "https://github.com/swiftlang/swift-build.git", branch: "main"),
.package(url: "https://github.com/swiftlang/swift-build.git", revision: "7f96ee0e8aa8a35fe84f3e80932eb9e456356d10"),

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Appreciate the pin for the direct dependency! Its transitive deps still track main though, so a clean resolve can still drift with no diff here. CI already keys the cache on Package.resolved. Do we want the lockfile in this PR so local and CI resolve the same graph?

@silentswordfish
silentswordfish merged commit 410c10a into main Aug 5, 2026
2 checks passed
@silentswordfish
silentswordfish deleted the pin-swift-build-dependency branch August 5, 2026 14:59
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.

2 participants