Skip to content

Add max_compatibility_level = 3 for rules_swift dep#3298

Closed
jpsim wants to merge 1 commit intoMobileNativeFoundation:mainfrom
jpsim:jp/rules-swift-max-compat-level
Closed

Add max_compatibility_level = 3 for rules_swift dep#3298
jpsim wants to merge 1 commit intoMobileNativeFoundation:mainfrom
jpsim:jp/rules-swift-max-compat-level

Conversation

@jpsim
Copy link
Copy Markdown
Contributor

@jpsim jpsim commented Mar 29, 2026

Summary

  • Add max_compatibility_level = 3 to the rules_swift bazel_dep in MODULE.bazel
  • The upcoming rules_swift release bumps compatibility_level from 2 to 3, which breaks Bzlmod resolution for downstream projects unless dependents declare max_compatibility_level = 3
  • Other modules in the ecosystem (rules_apple, rules_swift_package_manager, swift-syntax, swift-index-store) already declare this

Test plan

  • Verify Bzlmod resolution succeeds with a rules_swift git override at a commit past the compatibility_level = 3 bump (e.g. 00e74b8)

@jpsim jpsim requested a review from a team as a code owner March 29, 2026 17:19
The upcoming `rules_swift` release bumps `compatibility_level`
from 2 to 3. Without `max_compatibility_level = 3` on the
`bazel_dep`, Bzlmod rejects the resolution when downstream
projects use that release (or a git override at a commit past
the bump). Other modules in the ecosystem (`rules_apple`,
`rules_swift_package_manager`, `swift-syntax`,
`swift-index-store`) already declare this.

Signed-off-by: JP Simard <jp@jpsim.com>
@jpsim jpsim force-pushed the jp/rules-swift-max-compat-level branch from a772281 to ab25736 Compare March 29, 2026 17:21
@jpsim jpsim closed this Mar 29, 2026
@jpsim jpsim deleted the jp/rules-swift-max-compat-level branch March 29, 2026 17:31
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.

1 participant