Bug 2350493 - caddy-2.10.0 is available
Summary: caddy-2.10.0 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: caddy
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Carl George 🤠
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-03-06 22:23 UTC by Upstream Release Monitoring
Modified: 2025-04-29 01:12 UTC (History)
3 users (show)

Fixed In Version: caddy-2.10.0-1.fc42
Clone Of:
Environment:
Last Closed: 2025-04-29 01:12:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Upstream Release Monitoring 2025-03-06 22:23:00 UTC
Releases retrieved: 2.10.0-beta.1
Upstream release that is considered latest: 2.10.0-beta.1
Current version/release in rawhide: 2.9.1-3.fc42
URL: https://caddyserver.com

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


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/caddy

Comment 1 Upstream Release Monitoring 2025-04-18 21:13:21 UTC
Releases retrieved: 2.10.0
Upstream release that is considered latest: 2.10.0
Current version/release in rawhide: 2.9.1-3.fc42
URL: https://caddyserver.com

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


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/caddy

Comment 2 Fedora Update System 2025-04-19 05:03:06 UTC
FEDORA-2025-89401f2116 (caddy-2.10.0-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-89401f2116

Comment 3 Fedora Update System 2025-04-19 05:06:57 UTC
FEDORA-2025-89401f2116 (caddy-2.10.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.

Comment 4 Fedora Update System 2025-04-19 20:46:33 UTC
FEDORA-2025-4518c12e2f (caddy-2.10.0-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-4518c12e2f

Comment 5 Fedora Update System 2025-04-21 02:50:44 UTC
FEDORA-2025-4518c12e2f 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-4518c12e2f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-4518c12e2f

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

Comment 6 Fedora Update System 2025-04-29 01:12:02 UTC
FEDORA-2025-4518c12e2f (caddy-2.10.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.


Note You need to log in before you can comment on or make changes to this bug.