Bug 1955892

Summary: golang-github-aliyun-cli-3.0.74 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: golang-github-aliyun-cliAssignee: Brandon Perkins <bperkins>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: bperkins, go-sig
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: golang-github-aliyun-cli-3.0.74-2.s20210503git95a0900.fc35 golang-github-aliyun-cli-3.0.74-2.s20210503git95a0900.fc34 golang-github-aliyun-cli-3.0.74-2.s20210503git95a0900.fc33 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-03 16:32:31 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 2021-05-01 10:15:12 UTC
Latest upstream release: 3.0.74
Current version/release in rawhide: 3.0.73-1.s20210222git1e468f0.fc35
URL: https://github.com/aliyun/aliyun-cli

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

Comment 1 Fedora Update System 2021-05-03 16:32:31 UTC
FEDORA-2021-c452fb760e has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 2 Fedora Update System 2021-05-03 21:26:54 UTC
FEDORA-2021-1d4bcc5a04 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-1d4bcc5a04

Comment 3 Fedora Update System 2021-05-03 21:28:56 UTC
FEDORA-2021-7e05ce8f6f has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-7e05ce8f6f

Comment 4 Fedora Update System 2021-05-04 00:32:54 UTC
FEDORA-2021-1d4bcc5a04 has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-1d4bcc5a04`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-1d4bcc5a04

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

Comment 5 Fedora Update System 2021-05-04 01:09:36 UTC
FEDORA-2021-7e05ce8f6f 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-2021-7e05ce8f6f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-7e05ce8f6f

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

Comment 6 Fedora Update System 2021-05-12 05:42:28 UTC
FEDORA-2021-7e05ce8f6f has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2021-05-12 13:44:02 UTC
FEDORA-2021-1d4bcc5a04 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2021-05-12 16:12:36 UTC
FEDORA-2021-1d4bcc5a04 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.