Bug 2334967

Summary: python-ruamel-yaml-0.18.10 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: python-ruamel-yamlAssignee: Ondrej Mosnáček <omosnacek>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: code, epel-packagers-sig, jmontleo, omosnacek, openstack-sig, ssbarnea
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-ruamel-yaml-0.18.10-1.fc42 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-01-06 15:16:55 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:
Attachments:
Description Flags
Update to 0.18.7 (#2334967)
none
Update to 0.18.9 (#2334967)
none
Update to 0.18.10 (#2334967) none

Description Upstream Release Monitoring 2024-12-30 18:30:23 UTC
Releases retrieved: 0.18.7
Upstream release that is considered latest: 0.18.7
Current version/release in rawhide: 0.18.6-3.fc42
URL: https://pypi.org/project/ruamel.yaml/0.16.6

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


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/python-ruamel-yaml

Comment 1 Upstream Release Monitoring 2024-12-30 18:30:27 UTC
Created attachment 2064303 [details]
Update to 0.18.7 (#2334967)

Comment 2 Upstream Release Monitoring 2024-12-30 18:35:59 UTC
the-new-hotness/release-monitoring.org's scratch build of python-ruamel-yaml-0.18.7-1.fc40.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=127412750

Comment 3 Sorin Sbarnea 2025-01-03 09:28:12 UTC
Do not update to 0.18.7 and 0.18.8 due to known regression https://sourceforge.net/p/ruamel-yaml/tickets/534/ -- we are just updating ansible-lint to avoid using these versions via https://github.com/ansible/ansible-lint/pull/4462

Comment 4 Upstream Release Monitoring 2025-01-05 10:03:00 UTC
Releases retrieved: 0.18.9
Upstream release that is considered latest: 0.18.9
Current version/release in rawhide: 0.18.6-3.fc42
URL: https://pypi.org/project/ruamel.yaml/0.16.6

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


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/python-ruamel-yaml

Comment 5 Upstream Release Monitoring 2025-01-05 10:03:09 UTC
Created attachment 2064727 [details]
Update to 0.18.9 (#2334967)

Comment 6 Upstream Release Monitoring 2025-01-05 10:07:32 UTC
the-new-hotness/release-monitoring.org's scratch build of python-ruamel-yaml-0.18.9-1.fc40.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=127572676

Comment 7 Upstream Release Monitoring 2025-01-06 15:00:28 UTC
Releases retrieved: 0.18.10
Upstream release that is considered latest: 0.18.10
Current version/release in rawhide: 0.18.6-3.fc42
URL: https://pypi.org/project/ruamel.yaml/0.16.6

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


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/python-ruamel-yaml

Comment 8 Upstream Release Monitoring 2025-01-06 15:00:32 UTC
Created attachment 2064898 [details]
Update to 0.18.10 (#2334967)

Comment 9 Upstream Release Monitoring 2025-01-06 15:07:44 UTC
the-new-hotness/release-monitoring.org's scratch build of python-ruamel-yaml-0.18.10-1.fc40.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=127605289

Comment 10 Fedora Update System 2025-01-06 15:12:45 UTC
FEDORA-2025-085f77607e (python-ruamel-yaml-0.18.10-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-085f77607e

Comment 11 Fedora Update System 2025-01-06 15:16:55 UTC
FEDORA-2025-085f77607e (python-ruamel-yaml-0.18.10-1.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.