curl -L https://crates.io/api/v1/crates/secrecy/${VERSION}/download | tar -xf -
with VERSION as 0.8.0 and 0.10.3, then
diffing via git. It revealed nothing suspicious,
with changes as claimed per their CHANGELOG.md.
0.10.0 had some breaking changes. Secret<T> is
no longer a thing, instead there's SecretBox<T>. It turned out secrecy usage in bors is limited,
and private keys are fed as PEM-encoded Strings. For this, there's SecretString, which is just an alias for SecretBox<str>. Accepting it and
converting to bytes in create_github_client
simplifies code at the call sites a bit.
I diffed the actual crates.io contents via
with
VERSION
as0.8.0
and0.10.3
, then diffing via git. It revealed nothing suspicious, with changes as claimed per their CHANGELOG.md.0.10.0 had some breaking changes.
Secret<T>
is no longer a thing, instead there'sSecretBox<T>
. It turned out secrecy usage in bors is limited, and private keys are fed as PEM-encodedString
s. For this, there'sSecretString
, which is just an alias forSecretBox<str>
. Accepting it and converting to bytes increate_github_client
simplifies code at the call sites a bit.