Bug 2375297

Summary:	python-gitlab-6.1.0 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	python-gitlab	Assignee:	Steve Traylen <steve.traylen>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	steve.traylen
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-gitlab-6.1.0-1.fc43 python-gitlab-6.3.0-1.el10_1 python-gitlab-6.4.0-1.el10_2	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-06-30 07:32:01 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 2025-06-28 02:53:15 UTC

Releases retrieved: 6.1.0
Upstream release that is considered latest: 6.1.0
Current version/release in rawhide: 6.0.0-2.fc43
URL: https://github.com/python-gitlab/python-gitlab

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


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

Comment 1 Fedora Update System 2025-06-30 06:58:00 UTC

FEDORA-2025-5e9f3e4c0b (python-gitlab-6.1.0-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-5e9f3e4c0b

Comment 2 Fedora Update System 2025-06-30 07:32:01 UTC

FEDORA-2025-5e9f3e4c0b (python-gitlab-6.1.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.

Comment 3 Fedora Update System 2025-08-28 11:41:20 UTC

FEDORA-EPEL-2025-bb5dbe7097 (python-gitlab-6.3.0-1.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-bb5dbe7097

Comment 4 Fedora Update System 2025-08-29 02:10:44 UTC

FEDORA-EPEL-2025-bb5dbe7097 has been pushed to the Fedora EPEL 10.1 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-bb5dbe7097

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

Comment 5 Fedora Update System 2025-09-06 02:01:44 UTC

FEDORA-EPEL-2025-bb5dbe7097 (python-gitlab-6.3.0-1.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 Fedora Update System 2025-09-29 04:51:47 UTC

FEDORA-EPEL-2025-8c8212c570 (python-gitlab-6.4.0-1.el10_2) has been submitted as an update to Fedora EPEL 10.2.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-8c8212c570

Comment 7 Fedora Update System 2025-09-30 01:46:36 UTC

FEDORA-EPEL-2025-8c8212c570 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-2025-8c8212c570

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

Comment 8 Fedora Update System 2025-10-08 00:27:43 UTC

FEDORA-EPEL-2025-8c8212c570 (python-gitlab-6.4.0-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.