fix: adjust pre-release to use updateWebsiteBanner

Author: RafaelGSS

lib/security_blog.js

@@ -11,8 +11,6 @@ import {
 import auth from './auth.js';
 import Request from './request.js';
 
-const kChanged = Symbol('changed');
-
 export default class SecurityBlog extends SecurityRelease {
   req;
 
@@ -54,20 +52,19 @@ export default class SecurityBlog extends SecurityRelease {
 
     const file = path.resolve(process.cwd(), nodejsOrgFolder, pathToBlogPosts, fileNameExt);
     const site = path.resolve(process.cwd(), nodejsOrgFolder, pathToBannerJson);
-    const siteJson = JSON.parse(fs.readFileSync(site));
 
     const endDate = new Date(data.annoucementDate);
     endDate.setDate(endDate.getDate() + 7);
-    const capitalizedMonth = month[0].toUpperCase() + month.slice(1);
-    siteJson.websiteBanners.index = {
+
+    this.updateWebsiteBanner(site, {
       startDate: data.annoucementDate,
       endDate: endDate.toISOString(),
-      text: `${capitalizedMonth} Security Release is available`,
+      text: `New security releases to be made available ${data.releaseDate}`,
       link: `https://nodejs.org/en/blog/vulnerability/${fileName}`,
       type: 'warning'
-    };
+    });
+
     fs.writeFileSync(file, preRelease);
-    fs.writeFileSync(site, JSON.stringify(siteJson, null, 2));
     cli.ok(`Announcement file created and banner has been updated. Folder: ${nodejsOrgFolder}`);
   }