ci: use discord-bot's shared security-advisories action
Context & Requests for Reviewers
Follow-up to #1523. I moved the scripts into a shared security-advisories action on roostorg/discord-bot's so we can reuse across Coop and Osprey.
No behavior changes.
Tests
- The action's 14 tests pass in roostorg/discord-bot#20. They include an end-to-end run of the list and post steps against a fake GitHub API and a fake Discord webhook.
- zizmor 1.25.2 and actionlint report nothing on the workflow.
Release notes
Checklist
Only check items that apply to this PR; leave the rest unchecked.
-
If you changed anything user-facing (i.e. user interface or APIs):
Did you update related docs? -
If the change is notable (refer to Keep a Changelog conventions):
Did you fill in the Release notes section above? -
If this PR fixes a security vulnerability:
Did you apply thesecurity-updatelabel, or ask a maintainer to? Don't describe the vulnerability here before its advisory is published. -
If you changed
db/src/scripts/**and usedCREATE TABLE,ADD COLUMN, orALTER COLUMN:
Are as many columns markedNOT NULLas possible? If some columns can sometimes be null depending on other columns, are thereCHECKconstraints capturing those relationships, and are these also reflected using unions in the associated Kysely types? -
If you added a new signal in
server/services/signalsService/signals/**:
Did you classify every error case as a permanent error (SignalPermanentError, no retry) or a normal error (retryable)? Any case where the signal can't determine a score should be aSignalPermanentError.