Bump to 0.4.0 (which includes pin to python <3.12 in setup.py)~~Pin python<3.12~~

[jbusecke]

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-webservices]

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

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

• requirements: host: python<3.12 must contain a space between the name and the pin, i.e. python <3.12
• requirements: run: python<3.12 must contain a space between the name and the pin, i.e. python <3.12

[conda-forge-webservices]

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

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

• Non noarch packages should have python requirement without any version constraints.
• Non noarch packages should have python requirement without any version constraints.

[jbusecke]

Hmm this does not seem to be the intended way to pin python versions. I hope that xgcm/aerobulk-python#68 and the new release will resolve this.

[conda-forge-webservices]

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) and found it was in an excellent condition.

[jbusecke]

@conda-forge-admin, please rerender