fix: mention CI green on security --cleanup

RafaelGSS · RafaelGSS · commit 72a6284476dd · 2025-05-15T11:37:51.000-03:00
Very often we add new properties to vulnerabilities.json
and having a green ci before merging the PR is a must.
diff --git a/lib/prepare_security.js b/lib/prepare_security.js
@@ -70,7 +70,7 @@ export default class PrepareSecurityRelease extends SecurityRelease {
         { cli: this.cli, repository: this.repository }
       );
     }
-    this.cli.info(`Merge pull request with:
+    this.cli.info(`If the PR is ready (CI is green): merge pull request with:
         - git checkout main
         - git merge ${NEXT_SECURITY_RELEASE_BRANCH} --no-ff -m "chore: add latest security release"
         - git push origin main`);

Original file line number	Diff line number	Diff line change
`@@ -70,7 +70,7 @@ export default class PrepareSecurityRelease extends SecurityRelease {`
`70`	`70`	`{ cli: this.cli, repository: this.repository }`
`71`	`71`	`);`
`72`	`72`	`}`
`73`		- this.cli.info(`Merge pull request with:
	`73`	+ this.cli.info(`If the PR is ready (CI is green): merge pull request with:
`74`	`74`	`- git checkout main`
`75`	`75`	`- git merge ${NEXT_SECURITY_RELEASE_BRANCH} --no-ff -m "chore: add latest security release"`
`76`	`76`	- git push origin main`);