Bug 2451702

Summary: hut-0.8.0 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: hutAssignee: Maxwell G <maxwell>
Status: CLOSED ERRATA QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: go-sig, maxwell
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: hut-0.8.0-1.fc45 hut-0.8.0-1.fc44 hut-0.8.0-1.fc43 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-06-23 03:49:14 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-03-26 13:45:07 UTC
Releases retrieved: 0.8.0
Upstream release that is considered latest: 0.8.0
Current version/release in rawhide: 0.7.0-4.fc44
URL: https://sr.ht/~xenrox/hut/

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/292446/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/hut

Comment 1 Fedora Update System 2026-06-23 03:45:11 UTC
FEDORA-2026-09eedf55be (hut-0.8.0-1.fc45) has been submitted as an update to Fedora 45.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-09eedf55be

Comment 2 Fedora Update System 2026-06-23 03:47:48 UTC
FEDORA-2026-ed208f5337 (hut-0.8.0-1.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-ed208f5337

Comment 3 Fedora Update System 2026-06-23 03:48:05 UTC
FEDORA-2026-32113d4817 (hut-0.8.0-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-32113d4817

Comment 4 Fedora Update System 2026-06-23 03:49:14 UTC
FEDORA-2026-09eedf55be (hut-0.8.0-1.fc45) has been pushed to the Fedora 45 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 5 Fedora Update System 2026-06-24 01:19:25 UTC
FEDORA-2026-ed208f5337 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-ed208f5337`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-ed208f5337

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2026-06-24 02:00:07 UTC
FEDORA-2026-32113d4817 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-32113d4817`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-32113d4817

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2026-07-02 01:07:29 UTC
FEDORA-2026-ed208f5337 (hut-0.8.0-1.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2026-07-02 01:07:56 UTC
FEDORA-2026-32113d4817 (hut-0.8.0-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.