Skip to content

Conversation

@musicinmybrain
Copy link
Contributor

The breaking change in retry-polices 0.5 was that build_with_total_retry_duration_and_max_retries was renamed to build_with_total_retry_duration_and_limit_retries. Since rust-keylime doesn’t use this function, no source-code changes are required.

https://github.com/TrueLayer/retry-policies/blob/v0.5.1/CHANGELOG.md

The SemVer break in reqwest-retry is simply because it re-exports retry-policies.

https://github.com/TrueLayer/reqwest-middleware/blob/1485f61e20c8cd31cabb663788f06206c19cabaf/reqwest-retry/CHANGELOG.md

@musicinmybrain musicinmybrain force-pushed the reqwest-retry0.8 branch 2 times, most recently from ce1613d to 0885fc0 Compare December 18, 2025 10:30
@musicinmybrain
Copy link
Contributor Author

(Regarding availability of these versions downstream in Fedora, that’s the motivation for this PR: I have updated them with compat packages, and would like to work toward retiring the compat packages in Rawhide. See also https://src.fedoraproject.org/rpms/keylime-agent-rust/pull-request/45.)

@codecov
Copy link

codecov bot commented Jan 13, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 57.10%. Comparing base (43a12dd) to head (0804f7a).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files
Flag Coverage Δ
e2e-testsuite 37.37% <ø> (ø)
upstream-unit-tests 65.92% <ø> (-0.05%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 6 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@ansasaki ansasaki merged commit c8c1bfc into keylime:master Jan 13, 2026
14 of 15 checks passed
@ansasaki
Copy link
Contributor

@musicinmybrain Thank you for your contribution!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants