Merged
Conversation
|
So we merged this but haven't tagged the repository yet? |
Owner
Author
@krish7919 actually, the stuff hasn't been merged yet into the main repo. The PR is approved (Khan#406) but not yet merged into the main branch, which means that some upgrades needed to run with recent Golang versions aren't yet part of the most recently released package. That's actually the only reason for the existence of this repo: being able to use it with a reasonably recent set of modules that include a lot of CVE fixes. |
This file contains hidden or 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
3 participants
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.
The people want a release! (See discussion on Khan#394, Khan#383, fixes Khan#396.)
I'll wait to merge this until the discussion on Khan#402 is resolved, since the test flake looks like a deadlock, and I can't tell offhand if it could affect real usage.
I have: