Bug 2519832

Summary: rust-h2-0.4.17 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: rust-h2Assignee: Rust SIG <rust-sig>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: decathorpe, rust-sig
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rust-h2-0.4.17-1.el10_2 rust-h2-0.4.17-1.el10_3 rust-h2-0.4.17-1.el9 rust-h2-0.4.17-1.fc43 rust-h2-0.4.17-1.fc44 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-08-28 00:25:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Upstream Release Monitoring 2026-08-19 18:28:08 UTC 
Releases retrieved: 0.4.17
Upstream release that is considered latest: 0.4.17
Current version/release in rawhide: 0.4.15-2.fc45
URL: https://crates.io/crates/h2

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/17439/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/rust-h2
Comment 1 Fedora Update System 2026-08-19 23:40:57 UTC 
FEDORA-EPEL-2026-60c29a92fa (rust-h2-0.4.17-1.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-60c29a92fa
Comment 2 Fedora Update System 2026-08-19 23:40:57 UTC 
FEDORA-EPEL-2026-05b2ce23e5 (rust-h2-0.4.17-1.el10_2) has been submitted as an update to Fedora EPEL 10.2.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-05b2ce23e5
Comment 3 Fedora Update System 2026-08-19 23:40:58 UTC 
FEDORA-2026-4757e7a415 (rust-h2-0.4.17-1.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-4757e7a415
Comment 4 Fedora Update System 2026-08-19 23:40:58 UTC 
FEDORA-EPEL-2026-7e8d44c091 (rust-h2-0.4.17-1.el10_3) has been submitted as an update to Fedora EPEL 10.3.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-7e8d44c091
Comment 5 Fedora Update System 2026-08-20 15:29:27 UTC 
FEDORA-EPEL-2026-05b2ce23e5 has been pushed to the Fedora EPEL 10.2 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-05b2ce23e5

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 6 Fedora Update System 2026-08-20 15:58:34 UTC 
FEDORA-EPEL-2026-7e8d44c091 has been pushed to the Fedora EPEL 10.3 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-7e8d44c091

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 7 Fedora Update System 2026-08-20 16:04:23 UTC 
FEDORA-EPEL-2026-60c29a92fa has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-60c29a92fa

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 8 Fedora Update System 2026-08-20 16:40:11 UTC 
FEDORA-2026-4757e7a415 has been pushed to the Fedora 44 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-4757e7a415`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-4757e7a415

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 9 Fedora Update System 2026-08-20 16:40:29 UTC 
FEDORA-2026-c3233bfa3f has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-c3233bfa3f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-c3233bfa3f

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 10 Fedora Update System 2026-08-28 00:25:30 UTC 
FEDORA-EPEL-2026-05b2ce23e5 (rust-h2-0.4.17-1.el10_2) has been pushed to the Fedora EPEL 10.2 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 11 Fedora Update System 2026-08-28 00:35:49 UTC 
FEDORA-EPEL-2026-7e8d44c091 (rust-h2-0.4.17-1.el10_3) has been pushed to the Fedora EPEL 10.3 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 12 Fedora Update System 2026-08-28 00:48:09 UTC 
FEDORA-EPEL-2026-60c29a92fa (rust-h2-0.4.17-1.el9) has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 13 Fedora Update System 2026-08-28 01:16:12 UTC 
FEDORA-2026-c3233bfa3f (rust-h2-0.4.17-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 14 Fedora Update System 2026-08-28 16:07:00 UTC 
FEDORA-2026-4757e7a415 (rust-h2-0.4.17-1.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.