Bug 2279198

Summary:	dillo-3.1.0 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	dillo	Assignee:	Artem <ego.cordatus>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	ego.cordatus, itsme_410, walter.pete
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	dillo-3.1.0-2.fc41 dillo-3.1.0-3.el9 dillo-3.1.0-2.fc40	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-05-06 15:05:54 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 2024-05-05 22:59:28 UTC

Releases retrieved: 3.1.0
Upstream release that is considered latest: 3.1.0
Current version/release in rawhide: 3.0.5-31.fc40
URL: https://dillo-browser.github.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/438/


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

Comment 1 Fedora Update System 2024-05-06 15:01:36 UTC

FEDORA-2024-74d3ca457a (dillo-3.1.0-2.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-74d3ca457a

Comment 2 Fedora Update System 2024-05-06 15:05:54 UTC

FEDORA-2024-74d3ca457a (dillo-3.1.0-2.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 3 Fedora Update System 2024-05-06 17:28:01 UTC

FEDORA-2024-473832f5d5 (dillo-3.1.0-2.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-473832f5d5

Comment 4 Fedora Update System 2024-05-06 17:28:11 UTC

FEDORA-EPEL-2024-7c234f02b1 (dillo-3.1.0-3.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-7c234f02b1

Comment 5 Fedora Update System 2024-05-07 03:35:51 UTC

FEDORA-EPEL-2024-7c234f02b1 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-2024-7c234f02b1

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

Comment 6 Fedora Update System 2024-05-07 04:56:09 UTC

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

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

Comment 7 Fedora Update System 2024-05-15 15:41:57 UTC

FEDORA-EPEL-2024-7c234f02b1 (dillo-3.1.0-3.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 8 Fedora Update System 2024-05-15 18:56:31 UTC

FEDORA-2024-473832f5d5 (dillo-3.1.0-2.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.