Awesome Copilot Marketplace Update Process: Best Practices and the way forward

[flovogt]

In the current contributing process #751 the update strategy is not mentioned clearly. As far as I see, every plugin has to create an new issue when a new version of a plugin has been released. So, that's some manual work and I hope we can establish a more robust an autonomous process here.

Ideas

• Current Setup: Every plugin has to create an issue manually to update the plugin
• Every plugin has to create a GitHub action creating an issue automatically when a new release is published
• github/awesome-copilot implements an update GitHub action like Anthropic does it in the Claude marketplace (see https://github.com/anthropics/claude-plugins-official/blob/main/.github/workflows/bump-plugin-shas.yml, example PR: bump(ui5): 9b3d7d80 → 6d72751f anthropics/claude-plugins-official#2564).
• many more

Looking forward to your feedback!