Repository navigation
ci: use discord-bot's shared security-advisories action - #1578
Merged
Merged
Conversation
The listing script, its tests and the cache steps now live in roostorg/discord-bot's security-advisories action, shared with osprey. Cache keys and HMAC state are unchanged, so nothing is reposted. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The previous commit removed the script but left the workflow calling it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
reitblatt
marked this pull request as ready for review
November 16, 2026 22:22
…sory-action # Conflicts: # .github/workflows/security-advisory-notify.yml
reitblatt
enabled auto-merge (squash)
November 16, 2026 22:50
juanmrad
approved these changes
Nov 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context & Requests for Reviewers
Follow-up to #1523. I moved the scripts into a shared
security-advisoriesaction on roostorg/discord-bot's so we can reuse across Coop and Osprey.No behavior changes.
Tests
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 the
security-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 marked
NOT 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.