Use spin pluginify for CI?

[vdice]

Would spin pluginify be a good fit to replace the current script used to create new plugin release manifests? It would be great to use the same tool both in local dev mode and in CI.

We'd need pluginify to:

• Create a manifest with all supported os/arch combos for a given release version and download url (not sure if this can already be accomplished by the tool today)
• Support overriding the following values in spin-pluginify.toml when creating a manifest as described above: version and homepage (to support canary releases for the former and support publishing the plugin from forks for the latter)

Thoughts @itowlson @karthik2804 ?

[karthik2804]

That would be great to have a common tool do it across all the plugins. I do believe that Pluginify has the ability to unify multiple manifests into a "super" manifest (for lack of a better word).

[itowlson]

It does, but the resultant workflow isn't elegant, e.g. https://github.com/fermyon/spin-trigger-sqs/blob/main/.github/workflows/build.yml

But I'm sure we could make it better with wiser eyes than mine on it!

[rajatjindal]

FWIW, on the side I am working on https://github.com/rajatjindal/spin-plugin-release-bot. This will enable publishing new releases as PR to spin-plugin repo, which we can then review/merge (also candidate for automation and on my radar).