This is a useful module, it would be beneficial if it had security advisory coverage the 2.0.x branch was marked as "recommended" so that the 2.0.0 release showed with a green bar instead of a yellow bar.

Comments

DamienMcKenna created an issue. See original summary.

hardik_patel_12’s picture

hardik_patel_12 commented

HI @DamienMcKenna, I think this module is already covering all points suggested by the security advisory policy . Can you please provide more details for security advisory coverage that needs to be cover for this module?

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Title: Opt into security advisory coverage » Make 2.0.0 release "recommended"
Issue summary: View changes

I corrected the issue - the 2.0.0 release don't show with a green background because there isn't a recommended branch associated with it, not because it isn't opted into security coverage.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented

BTW to make this work as intended you might need to create a new 2.0.x branch.

hardik_patel_12’s picture

hardik_patel_12 commented

Ok, got it. I will create the 2.0.x branch with some new features and release them.
Thanks, @DamienMcKenna.

hardik_patel_12’s picture

hardik_patel_12 commented
Status: Active » Fixed

Created 2.X.0 branch and released a new version of this module called "2.0.2" with some new features like default configuration schema, and marking as recommended by the project’s maintainer.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.