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.
Description
This logs the sha256 of every created package, no matter if called from conda-build or done via transmute.
It allows to co-relate build/transmute logs with cryptographic safety, meaning any package in the wild can via its sha256 traced back to its build log with very high probability as sha256 collisions are very unlikely/hard to generate.
Not yet 100% sure if that is the right place to do... it could be also done within conda-build right after the create call.. though doing it in cph also covers the transmute case.
@jaimergp maybe also interesting for you :)
Checklist - did you ...
news
directory (using the template) for the next release's release notes?