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: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-06T23:09:41Z Steven Engler opara@torproject.org 2025-01-06T23:02:49Z urn:sha1:252a3a803b2db65792db5bd51dee8950d8557e0d Denies 'mod.rs' files for consistency. https://rust-lang.github.io/rust-clippy/master/index.html#mod_module_files 2025-01-06T13:10:39Z Nick Mathewson nickm@torproject.org 2025-01-06T13:10:39Z urn:sha1:a7f3cacea1eb5657ee1fee6d49594b1a58841519 2024-12-03T14:27:26Z Nick Mathewson nickm@torproject.org 2024-12-03T14:15:50Z urn:sha1:64cc3f2ed3eea0b7c5cc89ae07cbdadfdc1646fb In 1.83, this warning triggers on many of our crates. We're thinking of fixing them all, but for now, we're going to disable the warning. This is part of #1765. 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-12-02T10:21:22Z Gabriela Moldovan gabi@torproject.org 2024-12-02T10:21:22Z urn:sha1:79ebfca2db4b631404329c4d25a91296eccaf839 2024-12-02T10:18:10Z Gabriela Moldovan gabi@torproject.org 2024-12-02T10:18:10Z urn:sha1:33ee39924dbffdd3f8686b1cf0420782b9675112 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-25T18:20:11Z Wesley Aptekar-Cassels me@wesleyac.com 2024-11-21T20:33:11Z urn:sha1:5a2419925cad081eeb4094125d13b8ad7c0312ea