Add pontoneer v0.3.6

[winding-lines]

Checklist

• My recipe.yaml file specifies which version(s) of MAX is compatible with my project (see here for an example). If not, my package is compatible with both 24.5 and 24.6.
• License file is packaged (see here for an example).
• Set the build number to 0 (for new packages, or if the version changed).
• Bumped the build number (if the version is unchanged).

[sstadick]

@winding-lines Could you add CodeQL to your repo? You can follow the instructions here https://docs.github.com/en/code-security/code-scanning/enabling-code-scanning/configuring-default-setup-for-code-scanning. Then add the badge to your README.md: ![CodeQL]([https://github.com/{username}/{repo name}/workflows/CodeQL/badge.svg](https://github.com/ossf/scorecard/workflows/CodeQL/badge.svg?branch=main))

This is something that Modular has asked for from any projects that are not Mojo only.

[winding-lines]

Thanks @sstadick , enabled CodeQL and added the badge.

[sstadick]

suggestion(non-blocking): for future versions, update this to mojo-compiler as it's a lighter dep, and also concider pinning the mojo version. Example: https://github.com/modular/modular-community/blob/main/recipes/emberjson/recipe.yaml

[sstadick]

And the package upload failed with the exact issue you pointed out in the forum.

I'll look into this tomorrow and see if it's fixable by us(community), or if we need modular. I thought we'd resolved this once already.

[sstadick]

Following up for completeness:

The ci job from the merge into master failed because the Pontoneer package failed to build and CI tried to add it to the failed deps list (which doesn't work at the moment since CI can't push to master).

#224 is open to fix the Pontoneer package