Bug 1861514

Summary: pytest-6.0.0 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: pytestAssignee: Thomas Moschny <thomas.moschny>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: dradez, mhroncok, mrunge, thomas.moschny
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-28 20:22:10 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
[patch] Update to 6.0.0 (#1861514) none

Description Upstream Release Monitoring 2020-07-28 20:00:31 UTC 
Latest upstream release: 6.0.0
Current version/release in rawhide: 5.4.3-1.fc33
URL: https://pypi.python.org/pypi/pytest

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/3765/
Comment 1 Upstream Release Monitoring 2020-07-28 20:00:35 UTC 
Created attachment 1702725 [details]
[patch] Update to 6.0.0 (#1861514)
Comment 2 Miro Hrončok 2020-07-28 20:22:10 UTC 

*** This bug has been marked as a duplicate of bug 1855480 ***