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

osquery

Okay! How to release:

1. Tag the release
2. Wait for CI to build
3. Make official builds -- <https://github.com/osquery/osquery-codesign/actions/workflows/build-and-sign.yml>
4. Push to test bucket <https://github.com/osquery/osquery-codesign/actions/workflows/release-to-buckets.yml>
5. Announce and get beta testers
6. Wait for people to declare it’s stable
7. Mark release stable in <https://github.com/osquery/osquery/releases>
8. Push to stable bucket <https://github.com/osquery/osquery-codesign/actions/workflows/release-to-buckets.yml>
9. Push to website:
	a. <https://github.com/osquery/osquery-site/actions/workflows/release.yml>
	b. go through the website deploy process
1. Announce on slack

Separately from this, we have the CHANGELOG. I wrote a simple go tool. It gathers the commits from github. and dumps whatever is missing from the CHANGELOG file to stdout.

I think there’s some easy ways to smooth/automate this.

• I wonder if we can find a way to trigger (3) and (4) from the GH release.
• Maybe we can trigger (8) and (9) from the release 
• 9b should be automated

Any kind of slack announcements we should be able to automate as well