Build from Zeek v6.0.3 #8
Merged
Conversation
This file contains 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.
Zeek v6.0.3 was just published today. It doesn't appear to have functional changes that will significantly affect Zui workflows. However, I'd like us to be good citizens in doing timely releases particularly when one of their releases has security fixes, such as this one does.
I've already created and smoke tested a Brimcap v1.6.0-beta2 pre-release artifact that uses a Zeek v6.0.3-brim1 artifact made from this branch and I've loaded test pcaps in Zui successfully with it. See brimdata/zui#2984.