Latest upstream release: 0.3.19 Current version/release in rawhide: 0.3.18-2.fc35 URL: https://pypi.org/project/libcst/0.2.0 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/24003/
Latest upstream release: 0.3.20 Current version/release in rawhide: 0.3.18-5.fc35 URL: https://pypi.org/project/libcst/0.2.0 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/24003/
Latest upstream release: 0.3.21 Current version/release in rawhide: 0.3.18-5.fc35 URL: https://pypi.org/project/libcst/0.2.0 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/24003/
FEDORA-2021-897037408d has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2021-897037408d
FEDORA-2021-e905bc99eb has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-e905bc99eb
FEDORA-2021-8114e33f99 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-8114e33f99
FEDORA-2021-897037408d has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2021-e905bc99eb 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-2021-e905bc99eb` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-e905bc99eb See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-8114e33f99 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-8114e33f99` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-8114e33f99 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-8114e33f99 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2021-e905bc99eb has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.