workflow/action for publishing bundled plugins

[illume]

Currently we have to build plugins locally, then manually add them to releases. It would be good if there was an action or scripts to help automate this.

So that people can release plugins without so many manual error prone and slow steps.

Describe the solution you'd like

Some way to help us more rapidly publish plugins like app-catalog, prometheus, and plugin-catalog all at once (or one at a time more rapidly).

It would be good to be able to use this for all plugins.

What users will benefit from this feature?

People doing releases for Headlamp, and hopefully anyone who has to release a plugin.

Additional context

It might be useful to provide this to others so they can publish their plugins too.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale