Bug 2104877
| Summary: | golang-github-google-cel-0.12.4 is available | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> |
| Component: | golang-github-google-cel | Assignee: | Robert-André Mauchin 🐧 <eclipseo> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | eclipseo, go-sig |
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | golang-github-google-cel-0.12.4-1.fc37 golang-github-google-cel-0.11.2-1.fc36 golang-github-google-cel-0.11.2-1.fc35 | Doc Type: | --- |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-08-07 13:57:54 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-07-07 11:49:19 UTC
Releases retrieved: 0.12.1 Upstream release that is considered latest: 0.12.1 Current version/release in rawhide: 0.11.4-3.fc37 URL: https://github.com/google/cel-go 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/205716/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/golang-github-google-cel Releases retrieved: 0.12.2, 0.12.3 Upstream release that is considered latest: 0.12.3 Current version/release in rawhide: 0.11.4-3.fc37 URL: https://github.com/google/cel-go 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/205716/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/golang-github-google-cel Releases retrieved: 0.12.4 Upstream release that is considered latest: 0.12.4 Current version/release in rawhide: 0.11.4-3.fc37 URL: https://github.com/google/cel-go 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/205716/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/golang-github-google-cel FEDORA-2022-2d49cf9323 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-2d49cf9323 FEDORA-2022-2d49cf9323 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-3c9381a377 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-3c9381a377 FEDORA-2022-e534fabd57 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-e534fabd57 FEDORA-2022-9960115b0a has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-9960115b0a FEDORA-2022-d436c7694b has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-d436c7694b FEDORA-2022-d436c7694b 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-2022-d436c7694b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-d436c7694b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-9960115b0a 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 --refresh --advisory=FEDORA-2022-9960115b0a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-9960115b0a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-d436c7694b has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-9960115b0a has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report. |