Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 2158071

Summary:	mozilla-noscript-11.4.14 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	mozilla-noscript	Assignee:	Dominik 'Rathann' Mierzejewski <dominik>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	dominik
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	mozilla-noscript-11.4.14-1.fc36 mozilla-noscript-11.4.14-1.fc37	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-01-13 01:20:27 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 2023-01-04 06:27:25 UTC

Releases retrieved: 11.4.14
Upstream release that is considered latest: 11.4.14
Current version/release in rawhide: 11.4.13-1.fc38
URL: https://noscript.net/

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


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

Comment 1 Fedora Update System 2023-01-04 11:18:24 UTC

FEDORA-2023-a167966a5a has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2023-a167966a5a

Comment 2 Fedora Update System 2023-01-04 11:18:24 UTC

FEDORA-2023-1f354b6380 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-1f354b6380

Comment 3 Fedora Update System 2023-01-05 01:25:58 UTC

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

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

Comment 4 Fedora Update System 2023-01-05 02:10:22 UTC

FEDORA-2023-a167966a5a has been pushed to the Fedora 36 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-a167966a5a`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-a167966a5a

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

Comment 5 Fedora Update System 2023-01-13 01:20:27 UTC

FEDORA-2023-a167966a5a has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 Fedora Update System 2023-01-13 01:30:59 UTC

FEDORA-2023-1f354b6380 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.