mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.2 2025-03-31T17:59:51Z 2025-03-31T17:59:51Z Gabriela Moldovan gabi@torproject.org 2025-03-31T17:34:50Z urn:sha1:1be579f99a7c0784bd7710f9ee6ee9a6b10c85df Done using: ``` for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do cargo set-version -p $crate 0.29.0 done ``` 2025-03-31T17:59:48Z Gabriela Moldovan gabi@torproject.org 2025-03-31T17:33:52Z urn:sha1:a0919b507bb2a5855e36b85a2e10e3eac5fa4e15 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. slotmap-careful: No change. fslock-guard: No change. caret: No change. retry-error: No change. ``` * crates that only have non-functional changes (bump the patch version): - test-temp-dir - equix - fs-mistrust - safelog * crates where APIs were broken (bump minor): - hashx (`RngCore` impl for `SipRand`) The bumps from this commit were created using this script: ``` PATCH=" test-temp-dir equix fs-mistrust safelog " for crate in $PATCH; do cargo set-version --bump patch -p $crate; done MINOR=" hashx " for crate in $MINOR; do cargo set-version --bump minor -p $crate; done ``` 2025-03-27T14:18:29Z Gabriela Moldovan gabi@torproject.org 2025-03-27T11:53:08Z urn:sha1:2253d7695e58565d8ddc6d0b014489726554fb1f In 0.27.0, strum's MSRV was bumped to 1.66.1, but that's okay because ours is 1.77. We aren't affected by any of its [breaking changes]. [breaking changes]: https://github.com/Peternator7/strum/blob/master/CHANGELOG.md#0270 2025-03-25T12:53:58Z Nick Mathewson nickm@torproject.org 2025-03-18T20:08:34Z urn:sha1:2e1e19f986fc2bded36e2c5328110bbe01263d9a 2025-03-18T16:09:44Z Nick Mathewson nickm@torproject.org 2025-03-17T17:56:27Z urn:sha1:e806f007efb84e40bf17ac1444b35ddab9abc83f (Per discussion at #1774, we think the changes are acceptable.) This commit won't compile on its own; subsequent commits will fix it. 2025-03-04T17:33:25Z Ian Jackson ijackson@chiark.greenend.org.uk 2025-02-26T17:19:40Z urn:sha1:37a1010070fa1cfd3d13adc4d5788def2c8ee115 This is going to become a hazard. Let's be explicit. This means using educe to derive the Default for Data. We also need to update our educe dependency to 0.4.22, since that's when Default(expression= "...") started working correctly. 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-12T11:33:27Z Ian Jackson ijackson@chiark.greenend.org.uk 2025-02-11T16:54:55Z urn:sha1:fd84e2ede87bb63d7312a2e9d4f46ed5c6bdad12 Right now this will give us `${Xmeta as ... default ...}`, which may improve things in the future. The Cargo.toml syntax is precisely that from https://docs.rs/derive-deftly/1.0.0/derive_deftly/doc_changelog/index.html#t:beta 2025-02-12T11:33:27Z Ian Jackson ijackson@chiark.greenend.org.uk 2025-02-11T16:51:36Z urn:sha1:b3f12ee37c823fb4bcf989b8f7ded5ac3afb02dc This is released now. Prepared with: cargo upgrade -i -p derive-deftly There is some new duplication now I think mostly because pwd-grp uses old derive-deftly.