Zeek bugfix release v8.0.3 is now available:
https://zeek.org/get-zeek
https://download.zeek.org/zeek-8.0.3.tar.gz
See the release notes for details of the new functionality, breaking changes, and changed functionality
Release v8.0.3 - zeek/zeek - GitHub
Binary packages for the new releases will also be available shortly:
Hi,
I have a question regarding versioning convention.
I believe 8.0.3 requires Python3.10 minimum to build while 8.0.1 could be built with minimum Python3.9. Wouldn’t such change normally happen in next minor (8.1) series? Or because Python broker bindings are optional (disabled through --disable-python), this change is not considered sort of “breaking” and can be part of patch release?
Thanks
Yes, you are correct that we definitely missed putting a note in the NEWS about it and that we typically don’t make such changes in patch releases.
The change was an unfortunate side-effect of we pulled in the fixes for https://github.com/zeek/trace-summary/pull/12. Instead of just pulling into that one change into a version of trace-summary and zeekctl specific for release/8.0, I opted to just pull the whole current version of Zeekctl at the time. This included a version bump for the pysubnettree python module which now requires Python 3.10 due to some other recent changes, as well as the fact that Python 3.9 will be end-of-life before the current Zeek LTS cycle ends (i.e. before Zeek 9.0 comes out). I’ll discuss with the team about a good way forward (either reverting this and making a more targeted fix), or with better messaging about what changed.
We discussed it and I’m planning to revert that change and make some more targeted fixes to Zeekctl without the Python version increase. This will be released as 8.0.4, probably early next week.