Skip to content

[ci skip] Backport ABI migrations to branch 2.25.x#345

Merged
jdblischak merged 1 commit intoconda-forge:mainfrom
jdblischak:backport-2.25
Sep 13, 2024
Merged

[ci skip] Backport ABI migrations to branch 2.25.x#345
jdblischak merged 1 commit intoconda-forge:mainfrom
jdblischak:backport-2.25

Conversation

@jdblischak
Copy link
Copy Markdown
Member

Checklist

  • Used a personal fork of the feedstock to propose changes
  • Bumped the build number (if the version is unchanged)
  • Reset the build number to 0 (if the version changed)
  • Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
  • Ensured the license file is being packaged.

Backporting ABI migrations to the newly created branch 2.25.x

git checkout -b 2.25.x 60f4faafbf65980c36a4dd5ed2ca37c637618b19
rm -r ~/.cache/conda-smithy/
conda smithy rerender --commit auto

xref: #344

@jdblischak jdblischak added the automerge Merge the PR when CI passes label Sep 13, 2024
@jdblischak
Copy link
Copy Markdown
Member Author

The win-64 build is failing because the Azure image version is 20240912.1.0 (actions/runner-images#10608). The 2.25.x branch is failing for the same reason (106f819). The solution is in #341. But I'm hesitant to make the change now since Azure has been consistently rolling back their images shortly after they deploy them.

@jdblischak
Copy link
Copy Markdown
Member Author

Merging since its [ci skip] anyway. I'll deal with the win-64 Visual Studio problem next week if this latest Azure image update proves to be stable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automerge Merge the PR when CI passes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants