Publish schema.json so pulumi/registry can pick up v2 updates

[borisschlosser]

The Pulumi Registry's nightly metadata job consumes provider schemas by fetching schema.json from a path inside the source tree (configured in community-packages/package-list.json). After the v2 restructure in c4273d8 (splitting into defang-aws, defang-azure, defang-gcp), no schema.json is reachable for any of the three new providers:

• provider/cmd/pulumi-resource-defang-aws/schema.json → 404 (not committed; make schema generates it locally)
• same for -azure and -gcp
• not present in the v2.0.0-beta.4 release assets either

This broke the registry's auto-update job (example failing run: https://github.com/pulumi/registry/actions/runs/25245562869/job/74029146966). To stop the noise, I've temporarily removed defang from the nightly check list in pulumi/registry#10890. The registry page is currently pinned at v1.0.0.

To get back into the registry update flow, please either:

1. Commit schema.json for each provider under provider/cmd/pulumi-resource-defang-{aws,azure,gcp}/schema.json, or
2. Attach schema.json files as release assets and let us know the URL pattern.

Once schemas are reachable, we'll re-add the entries (one per provider) to community-packages/package-list.json.

Side note: v2.0.0-beta.4 is currently marked as the "latest" GitHub release (not flagged as prerelease), which is why the registry's pkgversion check picks it up over v1.0.0. You may want to mark beta tags as prereleases going forward so releases/latest returns the last stable.

[lionello]

@borisschlosser this was fixed: we now commit the schema.json into GIT, as well as added them to the release artifacts.

We no longer support the previous stable v1 release, that's why the new v2 beta releases are marked as latest and not prerelease.

Is there anything else we need to do, or will this get picked up automatically?

[lionello]

I've reopened at PR to add us back to the registry @borisschlosser : pulumi/registry#11109