Fedora Account System
Red Hat Associate
Red Hat Customer
Releases retrieved: 3.37.0 Upstream release that is considered latest: 3.37.0 Current version/release in rawhide: 3.36.0-4.fc44 URL: https://github.com/slackapi/python-slackclient 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://docs.fedoraproject.org/en-US/package-maintainers/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/15587/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/python-slackclient
Created attachment 2108921 [details] Update to 3.37.0 (#2402038)
the-new-hotness/release-monitoring.org's scratch build of python-slackclient-3.37.0-1.fc40.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=137865758
FEDORA-2025-89f1ed2c0a (python-slackclient-3.37.0-1.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-89f1ed2c0a
FEDORA-2025-89f1ed2c0a has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-89f1ed2c0a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-89f1ed2c0a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-89f1ed2c0a (python-slackclient-3.37.0-1.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.