mirrors/arti.git/crates/arti-client/Cargo.toml, branch arti-v1.3.2

Bump versions of internal arti crates for Arti 1.3.2

2025-01-07T16:01:41Z

The affected crates follow our regular versioning. They all get bumped to 0.26.0. Done with ``` for crate in $(./maint/list_crates |grep '^arti-\|tor-' ); do cargo set-version --bump minor -p $crate; done ```

Move base CfgPathResolver for arti-client back to tor-config-path.

2024-12-09T20:23:43Z

This time, we make explicit that it is a _base_ resolver, and that it is client-only.

Bump all the unstable tor- and arti- crates to 0.25.0.

2024-12-02T15:41:21Z

Done using: ``` for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do cargo set-version -p $crate 0.25.0 done ```

Bump the versions of the non-{arti-,tor-} crates.

2024-12-02T15:41:21Z

The non-{arti-,tor-} crates are: ``` ./maint/list_crates | rg -v '^(tor|arti)' oneshot-fused-workaround slotmap-careful test-temp-dir fslock-guard hashx equix caret fs-mistrust safelog retry-error ``` We split them in the following categories: * crates with no changes (no version bumps): ``` maint/changed_crates -v "arti-v$LAST_VERSION" 2>&1 >/dev/null | grep -i "no change" | grep -v '$tor\|arti$-' oneshot-fused-workaround: No change. test-temp-dir: No change. caret: No change. ``` * crates that only have non-functional changes (bump the patch version): - slotmap-careful - fslock-guard - hashx - equix - fs-mistrust - safelog - retry-error * crates where APIs were broken (bump minor): None The bumps from this commit were created using this script: ``` PATCH=" slotmap-careful fslock-guard hashx equix fs-mistrust safelog retry-error " for crate in $PATCH; do cargo set-version --bump patch -p $crate; done ```

Run fixup-features in preparation for release (fmt).

2024-12-02T10:21:22Z

Run fixup-features in preparation for release.

2024-12-02T10:18:10Z

PoW: Consolidate feature flags into a single flag.

2024-11-25T20:49:46Z

This replaces the hs-pow, hs-pow-full, hs-pow-v1, pow-v1, and pow-full features with a single hs-pow-full feature. It's possible that in the future we will want to split different schemes into different features, but we can do that when it comes up. For now, having this as a single flag makes it clearer what's going on, since the previous thing was not actually expressive enough to capture some things we care about (like "at least one pow scheme is enabled" that works in a future-compatible way). This change is not semver breaking since it's a experimental feature. Related: #1751

update `CfgPath::path` to use a `CfgPathResolver`

2024-11-18T15:01:56Z

This is a big change across multiple crates since there isn't a good way to break it up. This changes the signature of `CfgPath::path` to: ``` pub fn path(&self, path_resolver: &CfgPathResolver) -> Result { ``` Making this change means that our global `CfgPathResolver` needs to be stored in the 'arti-client' library instead of `tor-config-path`, and must be passed through to anything that calls `path` to expand the variables.

cargo: Update `thiserror` to `2`

2024-11-12T17:00:30Z

tor-config: removed re-export of `CfgPath`

2024-11-04T14:58:43Z

Also updated other packages to get `CfgPath` directly from `tor-config-path' instead of 'tor-config'.