[Review] SE-0534: Opt-in exact matching for version identifiers with build metadata

Hello, Swift community!

The review of SE-0534: Opt-in exact matching for version identifiers with build metadata begins now and runs through July 6, 2026.

Reviews are an important part of the Swift evolution process. All review feedback should be either on this forum thread or, if you would like to keep your feedback private, directly to me as the review manager by email or DM. When contacting the review manager directly, please put "SE-0534" in the subject line.

What goes into a review?

The goal of the review process is to improve the proposal under review through constructive criticism and, eventually, determine the direction of Swift. When writing your review, here are some questions you might want to answer in your review:

  • What is your evaluation of the proposal?
  • Is the problem being addressed significant enough to warrant a change to Swift?
  • Does this proposal fit well with the feel and direction of Swift?
  • If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?
  • How much effort did you put into your review? A glance, a quick reading, or an in-depth study?

More information about the Swift evolution process is available at:

swift-evolution/process.md at main · swiftlang/swift-evolution · GitHub

Thank you,

Franz

4 Likes

Yes please, this has been sorely missed! Is there a future direction to standardize the metadata evaluation ordering? I would be nice to support a few standard strategies.

1 Like

+1

If I understand the behavior currently it will just pick one of 1.0.0+debug and `1.0.0+release` and you have no way to control which it picks. I know of friends that this has bit so this seems like a worthwhile change to SwiftPM.

1 Like