aboutsummaryrefslogtreecommitdiff
path: root/crates/tor-dirpublish/Cargo.toml
Commit message (Collapse)AuthorAgeFilesLines
* Bump versions for tor-* and arti-* cratesSteven Engler2026-08-031-7/+7
| | | | | | | ```bash readarray -t bump < <(maint/list-crates | grep -P '^tor-|^arti-') for crate in "${bump[@]}"; do cargo set-version --bump minor -p "${crate}"; done ```
* Version bumps for 2.5.0Nick Mathewson2026-06-301-9/+9
| | | | | | | | | | | | | Closes #2617. We've lucked out this time, and it turns out that every one of our published crates gets a minor bump. So this was generated with: ``` for cr in $(./maint/list-crates); do cargo set-version -p $cr --bump minor done ```
* Bump MSRV to 1.91Clara Engler2026-06-151-1/+1
| | | | | | | | | | | | | | | | | | | This commit bumps the MSRV to 1.91 which was released on 2025-10-30. The Cargo.toml files were updated as follows: ```sh git ls-files | \ grep ".*Cargo\.toml$" | \ xargs sed -i '' 's/^rust-version = "1\.89"$/rust-version = "1\.91"/g' ``` The following files were updated manually: ``` modified: .gitlab-ci.yml modified: README.md modified: flake.nix modified: maint/docker-android/Dockerfile ```
* Bump all the unstable tor- and arti- crates to 0.43.0Gabriela Moldovan2026-06-011-7/+7
| | | | | | | | | | Done using: ``` for crate in $(./maint/list-crates | rg '^(tor|arti-)'); do cargo set-version -p $crate 0.43.0 done ```
* dirpublish: Run maint/fixup-featuresGabriela Moldovan2026-06-011-1/+9
|
* Upgrade rand crates to 0.10.Wesley Aptekar-Cassels2026-05-121-1/+1
| | | | | | | | | | | When the circ-padding feature is enabled, we use maybenot, which does not yet support rand 0.10. In the meantime, enabling this feature pulls in rand 0.9. This is not ideal, but should be okay as a temporary situation. This also replaces the use of ReseedingRng (which was removed in 0.10) with the reseeding_rng crate. This is somewhat less performant, but it should be okay.
* New `tor-dirpublish` crate to handle uploading documents.Nick Mathewson2026-05-121-0/+39
This crate is a generalization of the logic for uploading we currently have in tor-hsservice to handle uploading a (possibly changing) document to a (possibly changing) list of targets. It supports different kinds of documents, different kinds of document targets, and different ways to upload. Currently only direct HTTP uploads are supported; we can add others in the future (and we'll have to, for bridges and onion services.) Closes #2499.