fix: add Package@swift-6.1.swift for Xcode 26 compatibility

[uny]

Problem

Xcode 26 (Swift 6.1) enforces SE-0450 Package Traits. When resolving SPM packages, it uses the version-specific manifest Package@swift-6.1.swift if available, and rejects packages that declare no traits with the error:

Disabled default traits on package 'sentry-cocoa' (Sentry) that declares no traits.
This is prohibited to allow packages to adopt traits initially without causing an API break.

This affects all users of sentry-cocoa 8.x on Xcode 26.

Solution

Add Package@swift-6.1.swift — a version-specific manifest that SPM uses when the Swift 6.1 compiler is active (Xcode 26). This is the same approach used on the main branch for 9.x.

The manifest:

• Uses swift-tools-version:6.1 (required for traits parameter)
• Declares traits: [.default(enabledTraits: [])] (satisfies SE-0450)
• Adds swiftLanguageModes: [.v5] (maintains Swift 5 compatibility)
• Points to the same 8.58.0 xcframework binaries (no SDK change)

The original Package.swift (swift-tools-version:5.3) is untouched and continues to work with older Xcode versions.

Verification

Tested on macOS 26 + Xcode 26 (Swift 6.1):

• swift package dump-package ✅
• SPM resolution in Xcode 26 ✅ (no traits error)

Fixes: getsentry/sentry-kotlin-multiplatform#535

[sdk-maintainer-bot]

This PR has been automatically closed. The referenced issue is already assigned to someone else.

If you believe this assignment is outdated, please comment on the issue to discuss before opening a new PR.

Please review our contributing guidelines for more details.

[github-actions]

Semver Impact of This PR

🟢 Patch (bug fixes)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).

---

Bug Fixes 🐛

• Add Package@swift-6.1.swift for Xcode 26 compatibility by uny in #7768

---

_{🤖 This preview updates automatically when you update the PR.}

[itaybre]

Looks like this got closed automatically

I am reopening it

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 2652b58. Configure here.}

[cursor]

Missing checksum comment markers break release automation scripts

High Severity

The checksum lines in Package@swift-6.1.swift are missing the comment markers (e.g., //Sentry-Static, //Sentry-Dynamic, etc.) that Package.swift has. The release script scripts/update-package-sha.sh uses sed patterns matching these exact comments to update checksums during releases. Since the new file is discovered by the script (via find . -name "Package@swift-*.swift") but lacks the markers, the sed replacements will silently fail, leaving stale checksums. The scripts/verify-package-sha.sh script will then fail when it can't grep for these markers, blocking the release pipeline.

Additional Locations (1)

• Package@swift-6.1.swift#L29-L45

 

^{Reviewed by Cursor Bugbot for commit 2652b58. Configure here.}

[cursor]

New manifest not in VersionBump files list

High Severity

The Utils/VersionBump/main.swift utility, which is invoked during releases via scripts/bump.sh, has a hardcoded files array that includes ./Package.swift but not ./Package@swift-6.1.swift. The updateVersion function does string replacement of the old version number with the new one in each listed file. Since the new manifest isn't listed, its download URLs (containing the version like 8.58.0) will remain stale after future version bumps, causing Xcode 26 users to download the wrong xcframework binaries.

Additional Locations (1)

• Package@swift-6.1.swift#L28-L45

 

^{Reviewed by Cursor Bugbot for commit 2652b58. Configure here.}