build: unpin FileType from fork now that upstream 2.2.1 ships the Linux fix#553
Merged
Merged
Conversation
…ux fix The fork existed only to rename FileType's system zlib module (CZlib -> FTZlib) so it wouldn't collide with ZIPFoundation's CZlib on Linux. velocityzen/FileType merged that rename (PR jocosocial#3) and released it in 2.2.1, so Swiftarr can depend on upstream directly again. Switches the pin from penguinboi/FileType@acfd132 to velocityzen/FileType from 2.2.1, restoring SemVer range resolution to match the other dependencies. Verified with a full swift build and the pure-helper test suite (170 tests, 0 failures).
cohoe
approved these changes
Jul 1, 2026
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
3 participants
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.
What
Switches the
FileTypedependency from my personal fork back to upstreamvelocityzen/FileType, pinnedfrom: "2.2.1".Why
The fork (
penguinboi/FileType@acfd132) existed for one reason: it renamed FileType's system zlib module (CZlib→FTZlib) so it wouldn't collide with ZIPFoundation's ownCZlibmodule and break the Linux build.Upstream has since merged that exact rename (velocityzen/FileType#3, merged 2026-06-21) and shipped it in tag 2.2.1, whose
Sources/contains the renamedFTZlibmodule. So Swiftarr can depend on upstream directly again — no more reliance on a personal fork, andfrom:restores normal SemVer range resolution to match every other dependency in the manifest.Changes
Package.swift— fork+revision pin →.package(url: "https://github.com/velocityzen/FileType", from: "2.2.1"); removed the now-obsolete "pinned to a fork" comment.Package.resolved— regenerated. Only the FileType pin moves (fork → upstream 2.2.1); no other dependency versions change.Verification
swift build— clean (fullswiftarrtarget links; FileType 2.2.1 and ZIPFoundation — the old collision pair — compile together).swift test --filter …, same set CI runs) — 170 tests, 0 failures.swift:6.2-nobleCI job here is the definitive check.