Skip to content

Support more flexible version selection #452

Open

Description

@jshier

Since Fastlane moved to using xcodes for version selection and install, we've lost the ability to be more flexible in the versions we select. For instance, attempting to select version 26.0 when 26.0.1 is installed will fail. I'd like to suggest one of three improvements:

  1. Automatically allow any patch version when selecting an Xcode minor version. e.g. 26.0 would match 26.0.2 but not 26.1.
  2. Like 1, but require a version level match. e.g. 26.0.0 would match the latest patch version, but 26.0 would still require a specific version.
  3. Match the previous Ruby tool behavior and allow the use of the ~> operator with a provided version. e.g. ~> 26 would match the latest major version available, ~> 26.0 would match the latest minor version available, and ~> 26.0.0 would match the latest patch version of 26.0.

This would allow CI to remain within a supported version range without an explicit update.

Activity

  1. rgoldberg commented on Apr 23, 2026

    @rgoldberg

    I don't know exactly what your option 2 means, but here are examples of an alternative syntax for your option 3:

    • +: newest version
    • 26.+: newest minor & patch for 26
    • 26.4.+: newest patch for 26.4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions