jupyter_core 4.10.0

[bollwyvl]

Checklist

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

[conda-forge-linter]

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.

[bollwyvl]

@conda-forge-admin please rerender

[blink1073]

Hmm, wonder why the bot didn't make a PR? The release was on April 18th. Either way, thanks!

[github-actions[bot]]

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!

[bollwyvl]

why the bot didn't make a PR

:confused: status page errors not very helpful in this case:

We found a problem parsing the recipe for version '4.10.0': 

AssertionError('\n')

traceback:
  File "/home/runner/work/autotick-bot/autotick-bot/cf-scripts/conda_forge_tick/migrators/version.py", line 509, in migrate
    cmeta = CondaMetaYAML(fp.read())
  File "/home/runner/work/autotick-bot/autotick-bot/cf-scripts/conda_forge_tick/recipe_parser/_parser.py", line 476, in __init__
    v, e = _parse_jinja2_variables(meta_yaml)
  File "/home/runner/work/autotick-bot/autotick-bot/cf-scripts/conda_forge_tick/recipe_parser/_parser.py", line 117, in _parse_jinja2_variables
    assert False, jinja2_data

but yeah, sometimes even small build-system changes are hard to reason about :wink: