Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure Pipielines: Replace soon-unsupported macOS 10.13 with 10.14 #7646

Merged
merged 1 commit into from
Jan 25, 2020

Conversation

hugovk
Copy link
Contributor

@hugovk hugovk commented Jan 24, 2020

Azure DevOps Blog:

We have decided to remove the macOS-10.13 image because less than 5% of users use macOS High Sierra 10.13 and there is a later macOS version image – macOS-10.14 available. In addition, we will be adding the latest macOS version – Catalina or macOS-10.15 on February 3, 2020.

More about upcoming changes:


Does this need a news entry or a trivial file/label?

@pradyunsg
Copy link
Member

The mobile UI doesn't let me add the label (unless I tap a lot of buttons, and it's late and I'm sleepy). This should be trivial (this isn't a user facing change that we'd call out in the news file).

Also, thanks for spotting this and filing this PR! This was definitely not on my radar. :)

@pfmoore pfmoore added the skip news Does not need a NEWS file entry (eg: trivial changes) label Jan 24, 2020
@hugovk
Copy link
Contributor Author

hugovk commented Jan 24, 2020

I only knew because Microsoft emailed me about another repo:

Based on our telemetry, your organization has used one of these images in the past month and will be impacted by this change. To ensure your pipeline isn’t impacted by this change, please update your pipelines using the following steps.

In that one, I changed it to macOS-latest (and ubuntu-latest and windows-latest) but I guess pip should pin for stability.

@pradyunsg pradyunsg merged commit 87fa5ce into pypa:master Jan 25, 2020
@hugovk hugovk deleted the update-azure-pipelines branch January 25, 2020 06:41
@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Feb 24, 2020
@lock lock bot locked as resolved and limited conversation to collaborators Feb 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-locked Outdated issues that have been locked by automation skip news Does not need a NEWS file entry (eg: trivial changes)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants