Releases retrieved: 0.4.0 Upstream release that is considered latest: 0.4.0 Current version/release in rawhide: 0.3.2-3.fc43 URL: https://pypi.org/project/hatch-nodejs-version/0.1.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://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/256088/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/python-hatch-nodejs-version
FEDORA-2025-d1b541a294 (python-hatch-nodejs-version-0.4.0-1.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2025-d1b541a294
FEDORA-EPEL-2025-09422e0ef1 (python-hatch-nodejs-version-0.4.0-1.el10_2) has been submitted as an update to Fedora EPEL 10.2. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-09422e0ef1
FEDORA-2025-4680d9d5fc (python-hatch-nodejs-version-0.4.0-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-4680d9d5fc
FEDORA-2025-9d595c6b8d (python-hatch-nodejs-version-0.4.0-1.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-9d595c6b8d
FEDORA-2025-d1b541a294 (python-hatch-nodejs-version-0.4.0-1.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2025-09422e0ef1 has been pushed to the Fedora EPEL 10.2 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-09422e0ef1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-9d595c6b8d has been pushed to the Fedora 42 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-9d595c6b8d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-9d595c6b8d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-eb58f3dda2 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-eb58f3dda2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-eb58f3dda2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-4680d9d5fc has been pushed to the Fedora 41 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-4680d9d5fc` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-4680d9d5fc See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-09422e0ef1 (python-hatch-nodejs-version-0.4.0-1.el10_2) has been pushed to the Fedora EPEL 10.2 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-eb58f3dda2 (python-hatch-nodejs-version-0.4.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.
FEDORA-2025-9d595c6b8d (python-hatch-nodejs-version-0.4.0-1.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.