pyodide-build 0.29.0, add maintainers

[bollwyvl]

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.

Changes:

• added maintainers per pyodide-build 0.29.0 #19 (comment) (please each add a comment in the affirmative below, or emoji if you can't be bothered)
  • @agriyakhetarpal
  • @hoodmane
  • @ryanking13

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

[bollwyvl]

@conda-forge-admin please rerender

[github-actions]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/pyodide-build-feedstock/actions/runs/10942746217.

[agriyakhetarpal]

Thank you! I affirm that I would like to be added.

[bollwyvl]

Gotta do $DAY_JOB stuff, will check back in when i get the chance.

[bollwyvl]

Back for a sec: with 100% more maintainers, we can push the others out to separate PRs (these can be automated with @conda-forge-admin please add maintainer @{who})

[bollwyvl]

@conda-forge-admin please rerender

[github-actions]

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!

[agriyakhetarpal]

Thanks for this, again! Separate PRs sounds good to me.