Support new field: `content.sha256hex`
conartist6 opened this issue · 0 comments
conartist6 commented
SHA1 is weak now, so any functionality based on it will likely need to be upgraded to SHA256 sooner or later. I'm reading that git is also slowly moving towards SHA256.