So, osquery 5.19.0 I've had this on Koliude beta ...
# core
s
So, osquery 5.19.0 I've had this on Koliude beta for a week or so. I think Fleet has had it running for at least that long. How are folks feeling about stable?
l
Hi folks! Fleet has been running 5.19.0 on
edge
for three weeks. Not aware of any issues so far. So g2g on our end.
🙌 1
z
Let's call it stable?!
2
s
I went through the release steps! 🚀 Give things a couple minutes to settle and we should have a 5.19.0
A bit of a detour to fixing node, but site is up!
f
changelog is still on 5.16, are the updates for 5.19 consolidated somewhere else? Thanks https://github.com/osquery/osquery/blob/master/CHANGELOG.md
l
@FG Lately we've been using the releases to document that changes: https://github.com/osquery/osquery/releases
f
gotcha, could i suggest adding a line to CHANGELOG.md with a link there for clarity? i don't recall if i signed the CLA for osquery but if I get time this afternoon i could file a PR myself.
👍 1
l
LGTM. Will defer to @seph @zwass in case it was an oversight and we want to continue tracking updates there.
s
mmmmm. My inclintion is to track in both and improve automation
We used to write the CHANGELOG and use it to paste into the release notes. But it's gotten a but out of order since I think we're mostly using the GH auto generated ones?
But a GHA to make a CHANGELOG.md PR from the changelog doesn't seem wrong?
z
Ah yes for sure or we can just document that as part of the process.
Thank you Seph!