Releases retrieved: 1.50.0 Upstream release that is considered latest: 1.50.0 Current version/release in rawhide: 1.49.2-1.fc39 URL: https://github.com/gorhill/uBlock 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/16686/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/mozilla-ublock-origin
Created attachment 1969693 [details] Update to 1.50.0 (#2213457)
the-new-hotness/release-monitoring.org's scratch build of mozilla-ublock-origin-1.50.0-1.fc38.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=101930709
FEDORA-2023-08a1c9744a has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-08a1c9744a
FEDORA-2023-338f9563c6 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-08a1c9744a has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-08a1c9744a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-08a1c9744a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-08a1c9744a has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.