Osquery uses basic SQL commands to leverage a relational data-model to describe a device.

osquery

I just cut <https://github.com/osquery/osquery/releases/tag/5.5.1> This includes a sqlite update. We do not believe osquery to be effected, but like ever, people like to know we’re on top of these.

I don't see assets on the release page -- is there another step we need to complete?

From the codesign repo I see the last job failed; seems some internal error at Github?

In meeting. Feel free to rerun or something

Yeah, github actions is having "degraded performance" <https://www.githubstatus.com/>

I’ve also noticed a warning on the previous successful job: <https://github.com/actions/runner-images/issues/6002>. It’s probably unrelated (as Sharvil shows)

Packages exist now. <https://github.com/osquery/osquery/releases/tag/5.5.1>

<@U0JFM04MS> This process looks like:
1. Human cuts release tag
2. Automation runs build on `master` they take about an hour
3. Human triggers codesign build (depends on 2)
4. automation codesigns and uploads to the release


Can we use a repository_dispatch event to trigger the codesign?

I believe that might have been manual, as a failsafe

`repository_dispatch` is surprisingly hard — it requires permissions that get dicy. If we wanted to automate it, I’d probably look at something cron based. Not perfect, but maybe good enough.