Patch release v1.3.1 #2859
Merged
Patch release v1.3.1 #2859
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.
Ordinarily I'd make changes like the CHANGELOG updates and advancing the
versionstring in a "prep" branch that's merged tomain, then base therelease/branch onmainafter that merges. However, since my goal here is to create a true patch release that only contains the fix in #2858, I'm approaching things in reverse.In this branch I've cherry-picked the changes from #2858 and then made the necessary CHANGELOG and
versionchanges. The draft release artifacts are at https://github.com/brimdata/zui/releases/tag/untagged-edbac20bc65f91d4104d, which I've smoke tested and confirmed run clean on VirusTotal and also clean on Record Future Triage.One this PR is approved, I'll click Publish Release so those artifacts go live, then I'll merge this PR so
mainwill have the updated CHANGELOG andversionstring going forward.