GitHub Security Advisories, which launched in beta earlier this year, are now generally available. And we’ve made some exciting changes based on feedback from maintainers. First, we’ve added the ability to automatically request a CVE identifier for any Security Advisory. We’ve also refined the process of creating and publishing a Security Advisory, so that it’s clearer when the advisory will become public and easier to provide the information needed to power automatic dependency updates via the GitHub Advisory Database.
GitHub Actions no longer triggers the release event for draft releases