mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.1 2025-03-03T13:18:27Z 2025-03-03T13:18:27Z Nick Mathewson nickm@torproject.org 2025-03-03T13:18:27Z urn:sha1:fd4dfef12d55dea0b4c07e290b5fef8cc925cd4d 2025-02-26T18:06:37Z Nick Mathewson nickm@torproject.org 2025-02-26T17:50:42Z urn:sha1:d4dfbd6e1af1935af8cc4b83831891165da6af51 This took a little refactoring, since derive_more::Foo no longer re-exports std::ops::Foo. 2025-02-06T18:17:34Z Ian Jackson ijackson@chiark.greenend.org.uk 2025-02-06T18:13:25Z urn:sha1:e590ba4d522b44ffc7adc0eea463309df2de12f3 See Release.md. maint/list_crates | grep -P '^tor-|^arti-' | xargs -n1 nailing-cargo -Eu set-version --bump minor -p This completes the version bumps. The report of changed crates, before I started the release work, is: $ maint/changed_crates -v "arti-v$LAST_VERSION" oneshot-fused-workaround: No change. slotmap-careful: No change. test-temp-dir: No change. fslock-guard: No change. hashx: No change. equix: No change. tor-basic-utils: No change. caret: No change. fs-mistrust safelog: No change. retry-error: No change. tor-error tor-general-addr: No change. tor-geoip: No change. tor-rtcompat tor-rtmock tor-async-utils tor-config tor-config-path tor-rpc-connect tor-log-ratelim: No change. tor-rpcbase tor-memquota: No change. tor-units tor-llcrypto: No change. tor-protover: No change. tor-bytes tor-checkable: No change. tor-cert tor-key-forge tor-hscrypto: No change. tor-socksproto: No change. tor-linkspec: No change. tor-cell: No change. tor-proto tor-netdoc: No change. tor-consdiff: No change. tor-netdir tor-relay-selection: No change. tor-persist tor-chanmgr tor-ptmgr: No change. tor-guardmgr: No change. tor-circmgr tor-dirclient: No change. tor-dirmgr: No change. tor-keymgr tor-hsclient tor-hsservice tor-hsrproxy: No change. tor-relay-crypto arti-client arti-relay arti-rpcserver arti arti-rpc-client-core $ 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 ``` 2025-01-06T13:10:39Z Nick Mathewson nickm@torproject.org 2025-01-06T13:10:39Z urn:sha1:a7f3cacea1eb5657ee1fee6d49594b1a58841519 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-11-28T14:44:00Z Gabriela Moldovan gabi@torproject.org 2024-11-28T14:27:39Z urn:sha1:a579e00e8ecd9883bb081bc4fe0a4e07831a0853 According to the changelog, moving from 0.7.6 to 0.8.0 we get some new constructors and breaking changes to various "general" APIs. 2024-11-25T20:49:46Z Wesley Aptekar-Cassels me@wesleyac.com 2024-11-25T20:45:58Z urn:sha1:7846ed242bf39d9b366f47393de28056d70abec0 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 2024-11-12T17:00:30Z Clara Engler cve@cve.cx 2024-11-12T10:04:54Z urn:sha1:2f00918ad55881fb8fb37ad51eb644c8aaa16a23 2024-10-30T18:21:11Z Ian Jackson iwj@torproject.org 2024-10-30T18:21:11Z urn:sha1:6f24257bdf1a075cf09b41787d834bcc1a37f3a3 Version bumps for release of 1.3.0 See merge request tpo/core/arti!2599