Bug 2012278

Summary:	json-3.10.3 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	json	Assignee:	Vitaly <vitaly>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	ebaron, knoepfel, vitaly, xjakub
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	json-3.10.3-1.fc34	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-10-16 20:44: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 2021-10-08 17:58:41 UTC

Latest upstream release: 3.10.3
Current version/release in rawhide: 3.10.2-1.fc36
URL: https://github.com/nlohmann/json

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://fedoraproject.org/wiki/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/11152/

Comment 1 Fedora Update System 2021-10-09 10:14:16 UTC

FEDORA-2021-6c6ac5c8af has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-6c6ac5c8af

Comment 2 Fedora Update System 2021-10-16 20:44:01 UTC

FEDORA-2021-6c6ac5c8af has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.