Force user to reauthenticate (sudo mode) to create/edit a release

[iTrooz]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Supply chain security

Discussion Details

It would be nice to have a repository feature to force a repository's maintainer to re-authenticate themselves (e.g. sudo mode) before creating or editing a release (or toggling that parameter off !). This would prevent an attacker hijacking a maintainer's account from creating a new release with malicious code (and since publishing to other platforms is usually handled by CI, to publish that malicious artifact to other platforms).

I know editing releases is already covered by immutable releases, but I think this is only a partial protection because the setting can be disabled without re-auth, and doesn't cover creating new releases anyway.

this feature would be greatly appreciated. Here is one such project that would greatly benefit from this feature if you need more info about a use case: https://github.com/WerWolv/ImHex

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐