Closed alerque closed 1 year ago
The failing CI check for cargo fmt has nothing to do with this PR.
Yeah, I'm honestly annoyed at cargo fmt
for a while now. In one PR it requests a change, in the next one it wants that change back. The problem is that we are depending on some feature only available on nightly, so it is inherently unstable …
Base: 52.57% // Head: 42.71% // Decreases project coverage by -9.85%
:warning:
Coverage data is based on head (
166ae55
) compared to base (a784263
). Patch has no changes to coverable lines.
:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
Change has been merged, even though GitHub has not gotten the memo yet (tbf I did some rebasing and cherry-picking, but I don't remember having changed the commit itself).
Upstream finally tagged a release that includes the fixes that were forcing a Git HEAD usage here. In order for distro packages to be reproducible it is important to use tagged dependency versions, especially at tagged release points.
https://github.com/ActuallyAllie/cli-clipboard/issues/13