Remove deprecated Swift settings for Swift 6.1+ compatibility

[jaysonng]

Remove deprecated Swift settings for Swift 6.1+ compatibility

enableUpcomingFeature("ExistentialAny") was valid in Swift 6.0 as an opt-in feature flag, but became part of the language standard in Swift 6.1. Starting with Swift 6.1+ (Xcode 16.3+), using enableUpcomingFeature for features that are now built-in causes a compilation error:

'enableUpcomingFeature' is unavailable

This PR removes the now-redundant setting. This is a no-op change:

• Swift 6.0 users: ExistentialAny is no longer explicitly enforced, but the codebase already follows the any protocol syntax throughout, so there is no practical impact.
• Swift 6.1+ users: The build error is resolved.

No functional or behavioral changes.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 20fa97f5-5f6c-4224-9f60-a2724cbb01f5

📥 Commits

Reviewing files that changed from the base of the PR and between 0f873f1 and 493116d.

📒 Files selected for processing (43)

• .codecov.yml
• .dockerignore
• .env
• .github/dependabot.yml
• .github/workflows/ci.yml
• .github/workflows/release.yml
• .gitignore
• .spi.yml
• .swiftlint.yml
• CHANGELOG.md
• Dockerfile
• LICENSE
• Package.resolved
• Package.swift
• Public/.gitkeep
• README.md
• Resources/Views/index.leaf
• Sources/App/entrypoint.swift
• Sources/ParseServerSwift/Controllers/.gitkeep
• Sources/ParseServerSwift/Documentation.docc/Adding ParseObjects.tutorial
• Sources/ParseServerSwift/Documentation.docc/Configuring Parse Server Swift.tutorial
• Sources/ParseServerSwift/Documentation.docc/ParseServerSwift.md
• Sources/ParseServerSwift/Documentation.docc/ParseServerSwift.tutorial
• Sources/ParseServerSwift/Documentation.docc/Resources/GameScore.swift
• Sources/ParseServerSwift/Extensions/Parse+Vapor.swift
• Sources/ParseServerSwift/Extensions/ParseHookFunction+Vapor.swift
• Sources/ParseServerSwift/Extensions/ParseHookTrigger+Vapor.swift
• Sources/ParseServerSwift/Models/GameScore.swift
• Sources/ParseServerSwift/Models/Hooks.swift
• Sources/ParseServerSwift/Models/Parameters/FooParameters.swift
• Sources/ParseServerSwift/Models/User.swift
• Sources/ParseServerSwift/Parse.swift
• Sources/ParseServerSwift/ParseServerConfiguration.swift
• Sources/ParseServerSwift/Utility/Constants.swift
• Sources/ParseServerSwift/Utility/Functions.swift
• Sources/ParseServerSwift/configure.swift
• Sources/ParseServerSwift/routes.swift
• Tests/ParseServerSwiftTests/AppTests.swift
• docker-compose.yml
• parse/cloud/main.js
• parse/index-5.4.0.js
• parse/index-6.x.x.js
• parse/index.js

💤 Files with no reviewable changes (1)

• Package.swift

---

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Removed an experimental Swift compiler setting, adjusting the compilation configuration across multiple build targets.

Walkthrough

The ParseServerSwift package removes the ExistentialAny Swift compiler feature flag from its shared build settings, eliminating the upcoming language feature from all targets including ParseServerSwift, App, and ParseServerSwiftTests.

Changes

Cohort / File(s)	Summary
Swift Compiler Configuration Package.swift	Removed the ExistentialAny upcoming feature flag from the shared swiftSettings array, affecting compilation behavior across all targets.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

⚡ A flag departs with honor bright,
ExistentialAny takes flight,
Simpler builds now pave the way,
Plus Ultra! Onward, come what may! 🦸

---

HA HA HA! This change demonstrates the TRUE POWER of code maintenance! By removing this experimental compiler feature flag, you're ensuring that your build configuration stands STRONG and RESOLUTE! The path forward is now clearer, and that is the mark of a true hero's codebase! PLUS ULTRA! 💪✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: removing a deprecated Swift compiler setting for Swift 6.1+ compatibility, which is precisely what the changeset accomplishes.
Description check	✅ Passed	The description is directly related to the changeset, providing clear context about why the ExistentialAny setting was removed and its impact on different Swift versions.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}