mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.3.2 2025-01-07T16:01:41Z 2025-01-07T16:01:41Z Nick Mathewson nickm@torproject.org 2025-01-07T14:49:52Z urn:sha1:41c604be68b44eab3fecb9c5f54efbe09c0900c3 Done with ``` cargo set-version --bump patch -p arti ``` 2025-01-07T16:01:41Z Nick Mathewson nickm@torproject.org 2025-01-07T14:46:55Z urn:sha1:8f4297f5e2712213910b50ced205c7b5aa0619b5 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 ``` 2024-12-02T15:41:21Z Gabriela Moldovan gabi@torproject.org 2024-12-02T15:40:48Z urn:sha1:642b3c4e2de4f8baa453ad4078884366eed545b5 Done using: ``` cargo set-version --bump patch -p arti ``` 2024-12-02T15:41:21Z Gabriela Moldovan gabi@torproject.org 2024-12-02T15:39:29Z urn:sha1:e29e7a9aab4312af6a35818cb01676376d888e49 Done using: ``` for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do cargo set-version -p $crate 0.25.0 done ``` 2024-12-02T15:41:21Z Gabriela Moldovan gabi@torproject.org 2024-12-02T15:32:52Z urn:sha1:158ff2d2c0ef59ce6cdf5e8d6fe499b50e762002 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 ``` 2024-10-30T17:03:55Z Ian Jackson ijackson@chiark.greenend.org.uk 2024-10-30T17:03:55Z urn:sha1:5c3fa0a7aee925391c7acc26cd82ba367b2edbea I think we should bump the minor version because of the new features, particularly supporting .onion domains as a client by default, and the OOM DoS resistance features (#351). cargo set-version --offline --bump=minor -p arti 2024-10-30T16:55:19Z Ian Jackson ijackson@chiark.greenend.org.uk 2024-10-30T16:55:19Z urn:sha1:08ff96ea214b3f4841aac10db77815e5e52c35d0 cargo set-version -p tor-async-utils 0.24.0 cargo set-version -p tor-basic-utils 0.24.0 cargo set-version -p tor-bytes 0.24.0 cargo set-version -p tor-cell 0.24.0 cargo set-version -p tor-cert 0.24.0 cargo set-version -p tor-chanmgr 0.24.0 cargo set-version -p tor-checkable 0.24.0 cargo set-version -p tor-circmgr 0.24.0 cargo set-version -p tor-config 0.24.0 cargo set-version -p tor-config-path 0.24.0 cargo set-version -p tor-consdiff 0.24.0 cargo set-version -p tor-dirclient 0.24.0 cargo set-version -p tor-dirmgr 0.24.0 cargo set-version -p tor-error 0.24.0 cargo set-version -p tor-general-addr 0.24.0 cargo set-version -p tor-geoip 0.24.0 cargo set-version -p tor-guardmgr 0.24.0 cargo set-version -p tor-hsclient 0.24.0 cargo set-version -p tor-hscrypto 0.24.0 cargo set-version -p tor-hsrproxy 0.24.0 cargo set-version -p tor-hsservice 0.24.0 cargo set-version -p tor-key-forge 0.24.0 cargo set-version -p tor-keymgr 0.24.0 cargo set-version -p tor-linkspec 0.24.0 cargo set-version -p tor-llcrypto 0.24.0 cargo set-version -p tor-log-ratelim 0.24.0 cargo set-version -p tor-memquota 0.24.0 cargo set-version -p tor-netdir 0.24.0 cargo set-version -p tor-netdoc 0.24.0 cargo set-version -p tor-persist 0.24.0 cargo set-version -p tor-proto 0.24.0 cargo set-version -p tor-protover 0.24.0 cargo set-version -p tor-ptmgr 0.24.0 cargo set-version -p tor-relay-crypto 0.24.0 cargo set-version -p tor-relay-selection 0.24.0 cargo set-version -p tor-rpcbase 0.24.0 cargo set-version -p tor-rtcompat 0.24.0 cargo set-version -p tor-rtmock 0.24.0 cargo set-version -p tor-socksproto 0.24.0 cargo set-version -p tor-units 0.24.0 cargo set-version -p arti-client 0.24.0 cargo set-version -p arti-relay 0.24.0 cargo set-version -p arti-rpc-client-core 0.24.0 cargo set-version -p arti-rpcserver 0.24.0 2024-09-30T13:07:17Z Nick Mathewson nickm@torproject.org 2024-09-30T13:07:17Z urn:sha1:d477b87e5c78c01c37201abda22b08dbb89ebe85 Generated with ``` cargo set-version --bump patchlevel -p arti ``` 2024-09-30T13:04:32Z Nick Mathewson nickm@torproject.org 2024-09-30T13:04:32Z urn:sha1:d6890da4b1f87fd5e834aeb0cc9a7cd4b1d99e88 Per our policy, every one of these gets a minor bump. Generated with: ``` for crate in $(./maint/list_crates | grep '^\(tor\|arti\)-' ); do cargo set-version --bump minor -p $crate; done ``` (Note the use of `-` at the end end of the grep pattern to prevent matching the `arti` crate.) 2024-09-30T12:56:28Z Nick Mathewson nickm@torproject.org 2024-09-30T12:56:28Z urn:sha1:b29dd6d7f90cf077e8809a1ab317e23535e165c8 These crates are not in the tor/arti namespace, but we have given them MSRV bumps: ``` oneshot-fused-workaround slotmap-careful fslock-guard hashx equix caret fs-mistrust safelog test-temp-dir retry-error ``` We are counting this as a breaking change. Since all of these crates are at 0.x.x, we have indicated the breaking change with a minor version bump. This commit was generated with the following script: ``` BUMPS=" oneshot-fused-workaround slotmap-careful fslock-guard hashx equix caret fs-mistrust safelog test-temp-dir retry-error " for crate in $BUMPS; do cargo set-version --bump minor -p $crate; done ```