Update Chroma dependency before next release #5019
Labels
Comments
No. He should consider doing releases himself. Last Chroma is from March. With Chroma and Dep I have to manually edit Gopackage.toml file with the hash, which I do now because I'm nice :-) |
bep
added a commit
to bep/hugo
that referenced
this issue
Aug 1, 2018
And since I have updated Dep locally, I get a bunch of other totally unrelated diffs. Which looks innocent enough. Fixes gohugoio#5019
Merged
bep
added a commit
that referenced
this issue
Aug 1, 2018
And since I have updated Dep locally, I get a bunch of other totally unrelated diffs. Which looks innocent enough. Fixes #5019
|
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Can you update the chroma dependency before the next release so that alecthomas/chroma@e4dff9a gets included?
For future, is the latest chroma HEAD auto-fetched before each release?
The text was updated successfully, but these errors were encountered: