Bug 2413726

Summary:	fish-4.2.0 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	fish	Assignee:	Neal Gompa <ngompa13>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	dan.cermak, igor.raits, luto, michel, ngompa13, svashisht
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	fish-4.2.0-1.fc43 fish-4.2.0-1.el10_2 fish-4.2.0-1.fc42	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-11-11 00:50:05 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 2025-11-10 07:58:51 UTC

Releases retrieved: 4.2.0
Upstream release that is considered latest: 4.2.0
Current version/release in rawhide: 4.1.2-5.fc44
URL: https://fishshell.com

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


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

Comment 1 Fedora Update System 2025-11-10 15:10:54 UTC

FEDORA-2025-8af0b3a063 (fish-4.2.0-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-8af0b3a063

Comment 2 Fedora Update System 2025-11-10 15:11:14 UTC

FEDORA-2025-81f0854f75 (fish-4.2.0-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-81f0854f75

Comment 3 Fedora Update System 2025-11-10 15:11:50 UTC

FEDORA-EPEL-2025-9542b4ed95 (fish-4.2.0-1.el10_2) has been submitted as an update to Fedora EPEL 10.2.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-9542b4ed95

Comment 4 Fedora Update System 2025-11-11 00:50:05 UTC

FEDORA-2025-8af0b3a063 (fish-4.2.0-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 5 Fedora Update System 2025-11-11 15:17:21 UTC

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

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

Comment 6 Fedora Update System 2025-11-11 18:27:49 UTC

FEDORA-EPEL-2025-9542b4ed95 has been pushed to the Fedora EPEL 10.2 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-9542b4ed95

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

Comment 7 Fedora Update System 2025-11-19 02:13:00 UTC

FEDORA-EPEL-2025-9542b4ed95 (fish-4.2.0-1.el10_2) has been pushed to the Fedora EPEL 10.2 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2025-11-19 02:30:20 UTC

FEDORA-2025-81f0854f75 (fish-4.2.0-1.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.