Bug 2058998
| Summary: | golang-github-niklasfasching-org-1.6.2 is available | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> |
| Component: | golang-github-niklasfasching-org | Assignee: | Elliott Sales de Andrade <quantum.analyst> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | go-sig, quantum.analyst |
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | golang-github-niklasfasching-org-1.6.2-1.fc34 golang-github-niklasfasching-org-1.6.2-1.fc35 golang-github-niklasfasching-org-1.6.2-1.fc36 | Doc Type: | --- |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-03-14 22:25:37 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-02-27 17:09:19 UTC
Latest upstream release: 1.6.2 Current version/release in rawhide: 1.6.0-3.fc37 URL: https://github.com/niklasfasching/go-org 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/21910/ FEDORA-2022-5fc2d0eec1 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-5fc2d0eec1 FEDORA-2022-07b0d97117 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-07b0d97117 FEDORA-2022-e0662f9a86 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-e0662f9a86` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-e0662f9a86 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-5fc2d0eec1 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-5fc2d0eec1` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-5fc2d0eec1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-07b0d97117 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-07b0d97117` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-07b0d97117 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-07b0d97117 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-5fc2d0eec1 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-e0662f9a86 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. |