Releases retrieved: 1.19.0 Upstream release that is considered latest: 1.19.0 Current version/release in rawhide: 1.18.0-2.fc39 URL: https://pypi.org/project/hatchling/0.0.10 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/185085/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/python-hatchling
I am tracking this, but not updating right away. First, I want to see what happens with two upstream bug reports indicating possible regressions: - https://github.com/pypa/hatch/issues/1114 hatchling 1.19.0 - AttributeError: module 'hatchling.build' has no attribute 'prepare_metadata_for_build_editable' - https://github.com/pypa/hatch/issues/1113 "ValueError: At least one file selection option must be defined" error with hatchling-v1.19.0 Second, I want to note that python-hatchling and hatch are maintained in a single upstream repository, but released separately with different version numbers. Furthermore, the hatchling tests that make sense to run offline are lumped in with the hatch tests, in tests/backend, and (while this isn’t ideal) it’s actually in the dependent “hatch” package that we run them. When hatchling releases get ahead of hatch, I sometimes need to patch in some test-suite changes to the hatch package to keep up with python-hatchling. This is usually OK. In this case, there has been a lot of churn, and patching would be more awkward. I hope that by delaying a little while, I can build python-hatchling ≥ 1.19.0 along with a new hatch release. According to https://github.com/pypa/hatch/issues/984, this is perhaps a bit behind schedule but nevertheless planned soon.
Releases retrieved: 1.19.1 Upstream release that is considered latest: 1.19.1 Current version/release in rawhide: 1.18.0-2.fc39 URL: https://pypi.org/project/hatchling/0.0.10 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/185085/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/python-hatchling
Releases retrieved: 1.20.0 Upstream release that is considered latest: 1.20.0 Current version/release in rawhide: 1.18.0-2.fc39 URL: https://pypi.org/project/hatchling/0.0.10 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/185085/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/python-hatchling
This probably won’t make it to EPEL9. There are two obstacles: - The version of python-click is too old; it must be at least 8.0.6, which means at least 8.1.0 in practice. I haven’t completed a full impact check, but it is probably possible to update it. The current package from Rawhide builds in EPEL9, there are no version constraints that would prevent the update, and the release notes don’t call out any obvious breaking changes. - I can’t figure out how to ensure the hatch/_version.py file is generated correctly with python3-setuptools_scm 6.0.1. Current Fedora branches have at least 7.x. This is not something in which I want to invest a lot of time.
Both of the mentioned obstacles are in Hatch, but updating python-hatchling far past the packaged Hatch version is troublesome and at minimum requires patching tests.
FEDORA-2023-08fb67dfef has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2023-08fb67dfef
FEDORA-2023-08fb67dfef has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-3c3699fe47 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-3c3699fe47
FEDORA-2023-1d669864d2 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-1d669864d2
FEDORA-2023-1d669864d2 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-1d669864d2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-1d669864d2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-3c3699fe47 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-3c3699fe47` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-3c3699fe47 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-1d669864d2 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-3c3699fe47 has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.