Bug 2399769

Summary:	gnome-shell-extension-vertical-workspaces-49.0 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	gnome-shell-extension-vertical-workspaces	Assignee:	Carl George 🤠 <carl>
Status:	CLOSED ERRATA	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	carl
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---	Flags:	fedora-admin-xmlrpc: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	gnome-shell-extension-vertical-workspaces-49.0-1.fc44 gnome-shell-extension-vertical-workspaces-49.0-1.fc43 gnome-shell-extension-vertical-workspaces-49.11-1.fc44	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-09-26 17:26:26 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-09-26 16:20:27 UTC

Releases retrieved: 49.0
Upstream release that is considered latest: 49.0
Current version/release in rawhide: 48.8^1.65abb6b-1.fc44
URL: https://github.com/G-dH/vertical-workspaces

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


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/gnome-shell-extension-vertical-workspaces

Comment 1 Fedora Update System 2025-09-26 17:21:24 UTC

FEDORA-2025-8805384eb4 (gnome-shell-extension-vertical-workspaces-49.0-1.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-8805384eb4

Comment 2 Fedora Update System 2025-09-26 17:26:26 UTC

FEDORA-2025-8805384eb4 (gnome-shell-extension-vertical-workspaces-49.0-1.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 3 Fedora Update System 2025-09-26 21:33:30 UTC

FEDORA-2025-52ad41d6a3 (gnome-shell-extension-vertical-workspaces-49.0-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-52ad41d6a3

Comment 4 Fedora Update System 2025-09-27 00:50:26 UTC

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

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

Comment 5 Fedora Update System 2025-10-05 00:16:20 UTC

FEDORA-2025-52ad41d6a3 (gnome-shell-extension-vertical-workspaces-49.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 6 Fedora Update System 2025-12-30 18:30:38 UTC

FEDORA-2025-aefe40fbb0 (gnome-shell-extension-vertical-workspaces-49.11-1.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-aefe40fbb0

Comment 7 Fedora Update System 2025-12-30 18:35:24 UTC

FEDORA-2025-aefe40fbb0 (gnome-shell-extension-vertical-workspaces-49.11-1.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.