Bug 2440120

Summary:	catch-3.13.0 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	catch	Assignee:	Ben Beasley <code>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	code, epel-packagers-sig, igor.raits, orion, tom
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	catch-3.13.0-1.fc45 catch-3.13.0-1.fc44	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2026-02-16 20:30:44 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-02-16 02:16:01 UTC

Releases retrieved: 3.13.0
Upstream release that is considered latest: 3.13.0
Current version/release in rawhide: 3.10.0-3.fc44
URL: https://github.com/catchorg/Catch2

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


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

Comment 1 Ben Beasley 2026-02-16 07:16:36 UTC

I have a PR open for this as co-maintainer, https://src.fedoraproject.org/rpms/catch/pull-request/6. I’m currently impact-checking it.

Tom, feel free to look over my shoulder and tell me if you don’t like something. :-)

Comment 2 Tom Hughes 2026-02-16 08:23:09 UTC

Well you know this was only opned a few hours ago and I'd have looked at it once I got up... To be honest I didn't realise anybody else had maintainer on it.

As to the PR well there's so much in it that it's hard to comment quickly so it will probably have to wait until this evening now for me to review it anyway given all the other stuff.

Comment 3 Ben Beasley 2026-02-16 08:32:01 UTC

That’s fine. I’m in no hurry. It just happened to “catch” my eye. Please don’t feel pressured.

Comment 4 Fedora Update System 2026-02-16 20:25:51 UTC

FEDORA-2026-efaade4bd9 (catch-3.13.0-1.fc45) has been submitted as an update to Fedora 45.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-efaade4bd9

Comment 5 Fedora Update System 2026-02-16 20:30:44 UTC

FEDORA-2026-efaade4bd9 (catch-3.13.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 6 Fedora Update System 2026-02-17 22:42:22 UTC

FEDORA-2026-fa91074961 (catch-3.13.0-1.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-fa91074961

Comment 7 Fedora Update System 2026-02-18 05:07:55 UTC

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

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

Comment 8 Fedora Update System 2026-03-07 00:19:07 UTC

FEDORA-2026-fa91074961 (catch-3.13.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.