Update version to 2.22.4 in meta.yaml

[claytonparnell]

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.

[conda-forge-admin]

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:

• ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
  • For the host section of <output 3 output, you should usually use the pin python {{ python_min }} for the python entry.
  • For the run section of <output 3 output, you should usually use the pin python >={{ python_min }} for the python entry.
  • For the test.requires section of <output 3 output, you should usually use the pin python {{ python_min }} for the python entry.
  • For the host section of <output 4 output, you should usually use the pin python {{ python_min }} for the python entry.
  • For the run section of <output 4 output, you should usually use the pin python >={{ python_min }} for the python entry.
  • For the test.requires section of <output 4 output, you should usually use the pin python {{ python_min }} for the python entry.
  • If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).
• ℹ️ 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.
• ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

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

[xhochy]

@conda-forge-admin please rerender

[claytonparnell]

looks like databricks-sdk has some additional protobuf constraints in their main repo that aren't reflected in their feedstock, causing pip check failure in test:

databricks-sdk 0.74.0 has requirement protobuf!=5.26.*,!=5.27.*,!=5.28.*,!=5.29.0,!=5.29.1,!=5.29.2,!=5.29.3,!=5.29.4,!=6.30.0,!=6.30.1,!=6.31.0,<7.0,>=4.25.8, but you have protobuf 5.29.3.

[claytonparnell]

@conda-forge-admin, please restart ci

[claytonparnell]

The build here still picked up the older databricks-sdk build with incorrect dependency; hoping after conda-forge/conda-forge-repodata-patches-feedstock#1128 merged it'll be fixed

[xhochy]

Still getting databricks-sdk problems here.

[claytonparnell]

gonna try again now that databricks-sdk 0.76.0 is now on conda forge; I am not sure why the repodata patch is not being picked up by anaconda