Skip to content

Update default Xcode versions in workflow to Xcode 27 Beta 2#293

Merged
shahmishal merged 1 commit into
mainfrom
shahmishal-patch-1
Jun 26, 2026
Merged

Update default Xcode versions in workflow to Xcode 27 Beta 2#293
shahmishal merged 1 commit into
mainfrom
shahmishal-patch-1

Conversation

@shahmishal

Copy link
Copy Markdown
Member

Added Xcode version '27.b2' to the default list.

Added Xcode version '27.b2' to the default list.
@shahmishal shahmishal requested a review from a team as a code owner June 26, 2026 20:42
@shahmishal shahmishal merged commit 1ec62c9 into main Jun 26, 2026
394 of 395 checks passed
@shahmishal shahmishal deleted the shahmishal-patch-1 branch June 26, 2026 21:16
type: string
description: "Xcode version list (JSON)"
default: "[\"16.4\", \"26.3\", \"26.4\"]"
default: "[\"16.4\", \"26.3\", \"26.4\", \"27.b2\"]"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could this use the "latest" symlink instead so that we don't have to update every time the Xcode beta version changes?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to use a specific version so that people can exclude it and clearly understand what they are getting with a specific tag.

@madrob madrob Jun 27, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So that means we need to have at least two beta versions on each runner? What are the update window guarantees that we must provide? How many versions at a time will the runner need to carry so that consumers of this have enough time to update their workflows?

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.

2 participants