GHSA structured template required option dropdown doesn't work as expected

[StanFromIreland]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Other

Discussion Details

We recently added a VULNERABILITY_REPORT.yml to CPython (shortly after the announcement), with the following field:

  - type: dropdown
    id: versions
    attributes:
      label: "CPython versions tested on:"
      description: >
        If any tested version was not vulnerable, say which in the summary. Only [supported versions](https://devguide.python.org/versions/) accept reports.
      multiple: true
      options:
        - "3.11"
        - "3.12"
        - "3.13"
        - "3.14"
        - "3.15"
        - "3.16"
        - "CPython main branch"
    validations:
      required: true

However, unlike the same field in our issue templates, making the multiple and required true means all options have to be selected (as otherwise a reporter can't submit). This isn't consistent, and makes the feature unusable for us.

[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. ⭐

[jamalkamaladdin]

As a workaround, use a required textarea for tested versions instead of this dropdown:

- type: textarea
  id: versions
  attributes:
    label: "CPython versions tested on:"
    description: List tested versions and indicate which were vulnerable.
  validations:
    required: true

Private vulnerability reports support required textareas.