Skip to content

Conversation

@h-vetinari
Copy link
Member

Backport of #39, because arrow still depends on that version, and we've never actually closed the migrations for 2.37 and 2.38 because something is going wrong in google-cloud-cpp: conda-forge/google-cloud-cpp-feedstock#198

@h-vetinari h-vetinari requested a review from a team as a code owner July 6, 2025 10:58
@h-vetinari h-vetinari added the automerge Merge the PR when CI passes label Jul 6, 2025
@conda-forge-admin
Copy link
Contributor

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

  • ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/16098286790. Examine the logs at this URL for more detail.

@conda-forge-admin conda-forge-admin merged commit 5819e06 into conda-forge:v2.36.x Jul 6, 2025
9 checks passed
@conda-forge-admin
Copy link
Contributor

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

  • linter: passed
  • azure: passed

Thus the PR was passing and merged! Have a great day!

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