curl release candidates
Release candidates are pre-releases that include all features targeted for the pending curl release.
Please try release candidates in your use cases and products and verify that everything works as intended.
Test the new features and options and verify that they work the way they are documented, and maybe also the way you think they should. Features that have not shipped in a release yet can still be marginally tweaked if deemed desirable.
Do not use release candidates in production. They are work in progress. Use them for testing and verification only. Use actual releases in production.
Releases candidates are ephemeral. They are provided only for a few weeks until they are automatically removed. The coming release is scheduled to happen on 2025-04-02.
Release candidates
| file | date | size | signature |
|---|---|---|---|
| curl-8.13.0-rc1.tar.xz | 2025-03-08 | 2.7 MB | GPG |
| curl-8.13.0-rc1.zip | 2025-03-08 | 6.4 MB | GPG |
| curl-8.13.0-rc1.tar.bz2 | 2025-03-08 | 3.1 MB | GPG |
| curl-8.13.0-rc1.tar.gz | 2025-03-08 | 4.0 MB | GPG |
Contents
Each release candidate is provided in four different file formats. They all have the exact same content.
docs/RELEASE-TOOLS.md in the tarball shows the tooling needed to reproduce it.
docs/tarball-commit.txt in the tarball shows the exact commit hash that was the HEAD at the time the tarball was made. There are no git tags set for release candidates.
Release cycle
The idea is to provide three release candidates before every release, distributed as displayed in the image below.
- rc1 comes the day the feature release starts, 25 days before release
- rc2 comes nine days after rc1, 16 days before release
- rc3 comes nine days after rc2, 7 days before release
Updated: 2025-03-08 09:26 UTC