mirrors/arti.git/.gitlab-ci.yml, branch arti-v2.2.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.2.02026-03-18T15:14:28Zarti-extra: don't include flowctl-cc or counter-galois-onion2026-03-18T15:14:28ZJim Newsomejnewsome@torproject.org2026-03-10T20:21:11Zurn:sha1:0c2fc7a9646977a15b3c1f2906ba0aaf838d9cab
Including these would introduce flakiness, until arti#2400 is resolved.
This also adds a general mechanism for omitting specific features in the
arti-extra build.
arti-extra build: enable everything in full and experimental2026-03-18T15:14:28ZJim Newsomejnewsome@torproject.org2026-03-09T17:44:40Zurn:sha1:3fa4f98371b59684acd6173f7156acf02abfae68
Previously we enabled features piecemeal to avoid enabling `rpc`, which
resulted in breakage when running under shadow. Experimentally, this
appears to no longer be the case.
Enabling everything in `full` and `experimental` gives us at least a
little bit of testing of those features (that they don't break the build
or other usage), even if we don't specifically exercise them (yet) in
the CI tests.
chutney test: include arti-extra bin2026-03-11T19:33:42ZJim Newsomejnewsome@torproject.org2026-03-11T15:05:51Zurn:sha1:83f1d188a229b74ea7fc79b24afeaf38b225aa54
Test the arti-extra bin, which includes most of `full` and
`experimental` features, too.
python lints: install chutney2026-03-04T21:41:19ZJim Newsomejnewsome@torproject.org2026-03-04T21:08:47Zurn:sha1:ace1742f83a4642fddea4c21784a9b69ad157131
mypy needs it to correctly type-check the chutney test scripts, which
now import chutney as a module
chutney test: bump CHUTNEY commit and update to test all endpoints2026-03-04T21:41:19ZJim Newsomejnewsome@torproject.org2026-03-04T20:51:33Zurn:sha1:f8d2878046f6016207e6e10cae281baf42610c27
chutney replaced Node.socksport (a single optional port) with
Node.socksport_endpoints (a sequence of bound addresses and ports).
Update for compatibility, and test all of the exposed endpoints where
relevant.
chutney test: drop jq dependency2026-03-04T21:09:30ZJim Newsomejnewsome@torproject.org2026-03-04T19:45:44Zurn:sha1:0b78243cfddd3007ef60b2885dc697abdb3bd329Add compare_to check for cargo-audit changes rules check.2026-02-19T15:56:31ZAlexander Hansen Færøyahf@torproject.org2026-02-19T15:56:31Zurn:sha1:92b222c2442e060cc46ddc0da7e25df36fdf2313
See: arti#2367
See: arti!3703
See: arti!3690
Allow cargo-audit CI job to fail for MR's with no changes to **/Cargo.lock.2026-02-18T17:27:44ZAlexander Hansen Færøyahf@torproject.org2026-02-11T21:04:32Zurn:sha1:31390c82bdd65285fe796c89008103227755c9a9
This patch changes the behaviour of our `cargo-audit` CI job:
- All non-merge requests (pushes, manual jobs, scheduled jobs, tags, etc.) will
continue to run with allow_failure set to false.
- When a push is made, where there are changes to `**/Cargo.lock`, we
continue to NOT allow failures.
- When a push is made, where there are NO changes to `**/Cargo.lock`, we
now allow failures.
Specify workflows for Arti in our GitLab CI configuration:
- We currently run our jobs on pushes, and upon tags.
This was discussed in the Network Team meeting on 2026-02-10.
Bump MSRV from 1.86 to 1.892026-02-16T15:22:24ZGabriela Moldovangabi@torproject.org2026-02-09T11:29:39Zurn:sha1:c48a2ba6771016e7c57f02cfb99d62c3e5b34bc4
As agreed at our last team meeting.
See
https://gitlab.torproject.org/tpo/core/arti/#minimum-supported-rust-version
ci: Check crates configure features published to docs.rs2026-02-09T01:34:03ZNiel Duysterscontact@ndvibes.com2026-02-09T01:21:37Zurn:sha1:d4d7f9f1c6aa542f24f8abe8fe44f8f74a3ed9e1
All (publishable) crates should explicitly configure what features to (not) document in docs.rs.
This to avoid our documentation containing references to public API specifications which yield "given resource not found"
due to them being behind a feature flag not being published to docs.rs by default.