Run Package.resolved update on the production toolchain#1242
Merged
Conversation
The weekly "Update Package.resolved" job installed the macOS Swift.org toolchain via SwiftyLab/setup-swift@latest (currently swift-6.3.2-RELEASE). Its bundled Foundation lacks `Data.bytes`, which swift-configuration 1.2.0 (pulled transitively through vapor -> async-http-client >= 1.31.0) uses in FileProvider.swift. `swift package update && swift build` therefore failed with "value of type 'Data' has no member 'bytes'", so no update PR was ever created (failing every week since early May 2026). The app ships on swift:6.3-jammy (see Dockerfile) and the Test workflow builds green there, so the resolution is fine for production. Run the resolve/build inside that same image so Package.resolved is validated against the toolchain we actually deploy, instead of a floating macOS toolchain with a different Foundation. PR creation and automerge stay on the host runner where the gh CLI is available. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Problem
The weekly Update Package.resolved workflow (
spm.yml) has been failing every run since early May 2026 (e.g. run 27925733603, 27520002020). TheBuildstep dies with:so it never reaches Create Pull Request — dependency-update PRs have not been opened for ~7 weeks.
Root cause
swift-configurationis an indirect dependency:vapor→async-http-client→apple/swift-configuration.async-http-clientadded this dependency in 1.31.0.swift package update, which resolvesswift-configurationto 1.2.0. That version usesData.bytesinFileProvider.swift.SwiftyLab/setup-swift@latest(currentlyswift-6.3.2-RELEASE), whose bundled Foundation does not exposeData.bytes→ compile error.swift:6.3-jammy(seeDockerfile), and the Test workflow builds green there, so the resolved graph is fine for production — only the floating macOS Swift.org toolchain trips on it.Fix
Run the resolve/build inside the same
swift:6.3-jammyimage the app deploys on, soPackage.resolvedis validated against the real production toolchain instead of a floating macOS toolchain with a different Foundation. PR creation and automerge stay on the host runner where theghCLI is available.🤖 Generated with Claude Code