Make a stable release with security coverage

Created on 20 June 2017, about 8 years ago
Updated 23 July 2025, 11 days ago

For sites that require modules to be covered by the Drupal security team, using any of these extras is currently a no-no.

What, if any, are the barriers to making a full stable release with security coverage?

📌 Task
Status

Needs work

Version

1.0

Component

Code

Created by

🇳🇿New Zealand john pitcairn

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇷🇴Romania vasike Ramnicu Valcea

    isn't this done?

    I think the project page should updated by removing the note about this ...

    Stable releases for this project are covered by the security advisory policy.
    Look for the shield icon below.

  • heddn Nicaragua

    This is done.

  • 🇷🇴Romania vasike Ramnicu Valcea

    As I said previously the project page should remove the the note about this issue

  • heddn Nicaragua

    That label is added on d.o pages to educate visitors about what is a stable project. It can't be removed.

  • 🇷🇴Romania vasike Ramnicu Valcea

    I meant this text

    Note: This project is not yet stable. See #2887926: Make a stable release with security coverage

    which was added by a maintainer and includes this issue link ....

    And not the usual d.o text ... besides the versions/releases

    This project is not covered by the security advisory policy.
    Use at your own risk! It may have publicly disclosed vulnerabilities.

    And it's not case anymore as text is

    Stable releases for this project are covered by the security advisory policy.
    Look for the shield icon below.

    p.s. sorry for the noise ... but it could drive away people that really need this module ... and thanks

  • heddn Nicaragua

    Sorry, I missed that. Fixed. Thanks for your patience.

Production build 0.71.5 2024