Bug 2384195

Summary:	python-colcon-core-0.20.1 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	python-colcon-core	Assignee:	Scott K Logan <logans>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	logans
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-colcon-core-0.20.1-1.fc44 python-colcon-core-0.20.1-1.el8 python-colcon-core-0.20.1-1.el9 python-colcon-core-0.20.1-1.fc42 python-colcon-core-0.20.1-1.el10_2 python-colcon-core-0.20.1-1.el10_1 python-colcon-core-0.20.1-1.fc41	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-10-06 20:12:42 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-07-29 04:08:21 UTC

Releases retrieved: 0.20.0
Upstream release that is considered latest: 0.20.0
Current version/release in rawhide: 0.19.0-3.fc43
URL: https://colcon.readthedocs.io

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


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

Comment 1 Fedora Update System 2025-10-06 19:46:16 UTC

FEDORA-2025-014fdd06e3 (python-colcon-core-0.20.1-1.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-014fdd06e3

Comment 2 Fedora Update System 2025-10-06 20:12:42 UTC

FEDORA-2025-014fdd06e3 (python-colcon-core-0.20.1-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 3 Fedora Update System 2025-10-06 21:26:15 UTC

FEDORA-EPEL-2025-de5972edac (python-colcon-core-0.20.1-1.el8) has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-de5972edac

Comment 4 Fedora Update System 2025-10-06 21:26:16 UTC

FEDORA-EPEL-2025-be252462f7 (python-colcon-core-0.20.1-1.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-be252462f7

Comment 5 Fedora Update System 2025-10-06 21:26:16 UTC

FEDORA-EPEL-2025-39f4e1074c (python-colcon-core-0.20.1-1.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-39f4e1074c

Comment 6 Fedora Update System 2025-10-06 21:26:17 UTC

FEDORA-2025-c4c14d158e (python-colcon-core-0.20.1-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-c4c14d158e

Comment 7 Fedora Update System 2025-10-07 01:13:22 UTC

FEDORA-2025-492bf27d48 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-2025-492bf27d48`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-492bf27d48

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

Comment 8 Fedora Update System 2025-10-07 01:19:02 UTC

FEDORA-EPEL-2025-be252462f7 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-2025-be252462f7

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

Comment 9 Fedora Update System 2025-10-07 01:24:51 UTC

FEDORA-EPEL-2025-de5972edac has been pushed to the Fedora EPEL 8 testing repository.

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

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

Comment 10 Fedora Update System 2025-10-07 01:37:59 UTC

FEDORA-2025-ad52f28cf6 has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-ad52f28cf6`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-ad52f28cf6

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

Comment 11 Fedora Update System 2025-10-07 02:02:34 UTC

FEDORA-2025-c4c14d158e has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-c4c14d158e`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-c4c14d158e

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

Comment 12 Fedora Update System 2025-10-07 02:16:33 UTC

FEDORA-EPEL-2025-0e54a2b102 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-0e54a2b102

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

Comment 13 Fedora Update System 2025-10-07 02:17:10 UTC

FEDORA-EPEL-2025-39f4e1074c 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-39f4e1074c

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

Comment 14 Fedora Update System 2025-10-15 00:26:38 UTC

FEDORA-EPEL-2025-de5972edac (python-colcon-core-0.20.1-1.el8) has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 15 Fedora Update System 2025-10-15 00:30:13 UTC

FEDORA-EPEL-2025-be252462f7 (python-colcon-core-0.20.1-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 16 Fedora Update System 2025-10-15 01:00:43 UTC

FEDORA-2025-ad52f28cf6 (python-colcon-core-0.20.1-1.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 17 Fedora Update System 2025-10-15 01:48:42 UTC

FEDORA-EPEL-2025-0e54a2b102 (python-colcon-core-0.20.1-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 18 Fedora Update System 2025-10-15 01:57:02 UTC

FEDORA-EPEL-2025-39f4e1074c (python-colcon-core-0.20.1-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 19 Fedora Update System 2025-10-15 02:30:38 UTC

FEDORA-2025-c4c14d158e (python-colcon-core-0.20.1-1.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 20 Fedora Update System 2025-10-25 21:02:24 UTC

FEDORA-2025-492bf27d48 (python-colcon-core-0.20.1-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.