Bug 2098476

Summary:	vala-language-server-0.48.5 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	vala-language-server	Assignee:	Christopher Crouse <mail>
Status:	CLOSED ERRATA	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	mail, petersen
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	vala-language-server-0.48.5-1.fc37 vala-language-server-0.48.5-1.fc36 vala-language-server-0.48.5-1.fc35	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-06-21 13:01:16 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 2022-06-19 21:39:50 UTC

Releases retrieved: 0.48.5
Upstream release that is considered latest: 0.48.5
Current version/release in rawhide: 0.48.4-4.fc37
URL: https://github.com/Prince781/vala-language-server

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://fedoraproject.org/wiki/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/242051/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/vala-language-server

Comment 1 Fedora Update System 2022-06-21 13:00:47 UTC

FEDORA-2022-3a4881bfa7 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-3a4881bfa7

Comment 2 Fedora Update System 2022-06-21 13:01:16 UTC

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

Comment 3 Fedora Update System 2022-06-21 13:20:01 UTC

FEDORA-2022-5002f3ae68 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-5002f3ae68

Comment 4 Fedora Update System 2022-06-21 13:30:27 UTC

FEDORA-2022-d995f66e71 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-d995f66e71

Comment 5 Fedora Update System 2022-06-22 02:01:22 UTC

FEDORA-2022-5002f3ae68 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 --advisory=FEDORA-2022-5002f3ae68`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-5002f3ae68

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

Comment 6 Fedora Update System 2022-06-22 02:20:50 UTC

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

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

Comment 7 Fedora Update System 2022-06-30 01:17:38 UTC

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

Comment 8 Fedora Update System 2022-06-30 02:17:36 UTC

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