summaryrefslogtreecommitdiff
path: root/maint
Commit message (Collapse)AuthorAgeFilesLines
* Add a missing "-".Nick Mathewson2024-07-311-1/+1
|
* Add a script to run cbindgen and check its outputs.Nick Mathewson2024-07-312-3/+179
| | | | | | | | | | This is a bit complicated since: - Using cbindgen with macro expansion requires a nightly rust: so, we have to look for one. - There are some cbindgen warnings which I cannot find any way to suppress, so instead of giving all warnings, it seems better to give a diff from the old list of warnings to the new list.
* Bump our CI Rust build cache tokenIan Jackson2024-07-291-1/+1
| | | | | | This invalidates the cache. This may not be strictly necessary, but it will make sure that the new pinned image is used in the CI run *for this MR*.
* maint/rust-maint-common/forbid-absolute-shebang: Fix error messageIan Jackson2024-07-171-1/+1
|
* maint/common/update-shell-includes: Tolerate includes with a `$`Ian Jackson2024-07-161-1/+1
| | | | | | | | | | | | | | | These are not hardcoded, whatever they are, so they're not the principal thing we're trying to prevent. Previously, this would trip on this in arti.git:maint/cargo-publish: maint="$(dirname "$0")" ... # shellcheck source=maint/crates-io-utils.sh source "$maint/crates-io-utils.sh" Ideally we'd teach this script to be able to check and maintain includes for scripts that aren't in common/, but I think that's a task for another day.
* Switch to maint/common/forbid-script-extensionsIan Jackson2024-07-161-38/+0
|
* Switch to maint/common/forbid-absolute-shebangsIan Jackson2024-07-161-10/+0
|
* maint/common/forbid-absolute-shebansg: Fix error handlingIan Jackson2024-07-161-4/+15
| | | | | | | | set -o pipefail is defused by the if. And we should properly check the expected statuses from git. If git isn't found, this script would otherwise spuriously think everything is fine.
* maint scripts: Fix some absolute shebangsIan Jackson2024-07-162-2/+2
|
* maint/common/apt-install: Don't repeat apt-get updateIan Jackson2024-07-161-1/+9
|
* maint/common/apt-install: Use `apt-get install`Ian Jackson2024-07-161-1/+1
| | | | | This changes from `apt install` (which is not supposed to be used in scripts) to `apt-get install`.
* Switch to maint/common/via-cargo-install-in-ciIan Jackson2024-07-161-20/+0
| | | | And delete our old version of the script.
* Aet maint/via-cargo-install-in-ci.cache-idIan Jackson2024-07-161-0/+1
| | | | | | | See docs in maint/common/via-cargo-install-in-ci This is not the same id as in our maint/via-cargo-install-in-ci, which is deliberate. Let's flush this cache, just in case.
* Replace maint/shellcheck_all with maint/common/shellcheck-allIan Jackson2024-07-162-10/+3
| | | | | | | | * Change all in-tree reference * Delete our copy of script, which now lives in the rust-maint-common subtree. * Leave a symlink behind, so that old git hooks that people (IMO possibly unwisely) installed, still work.
* Add symlink to rust-maint-commonIan Jackson2024-07-161-0/+1
| | | | As recommended by the README there
* Add 'maint/rust-maint-common/' from commit ↵Ian Jackson2024-07-1616-0/+698
|\ | | | | | | | | | | | | | | 'be8ec72c0b0ced653c618af564387079d9ea8e5f' git-subtree-dir: maint/rust-maint-common git-subtree-mainline: c05af7edf8f715b31d90d128ba6078a8094f440c git-subtree-split: be8ec72c0b0ced653c618af564387079d9ea8e5f
| * via-cargo-install-in-ci: run in CIIan Jackson2024-07-111-0/+1
| | | | We must make a symlink so things can find the scripts in maint/.
* with_coverage: Exclude maint/ and examples/ in coverage reports.Nick Mathewson2024-07-151-0/+2
| | | | | These are not parts of arti per se, and we don't especially want to track their test coverage.
* Merge branch 'categories' into 'main'Nick Mathewson2024-07-153-6/+134
|\ | | | | | | | | | | | | Check cargo categories against crates.io Closes #1481 See merge request tpo/core/arti!2256
| * maint/: crates_io_api_call: Add a TODO about unifying themIan Jackson2024-07-111-0/+2
| |
| * maint/cargo-check-publishable: Check categoriesIan Jackson2024-07-102-0/+121
| | | | | | | | What a palaver.
| * maint/list_crates: Include `Crate.raw_metadata`Ian Jackson2024-07-101-2/+3
| |
| * maint/list_crates: Add a type annotationIan Jackson2024-07-101-1/+1
| |
| * maint/list_crates: Resolve `Crate.publish`Ian Jackson2024-07-101-1/+3
| | | | | | | | | | If this is unset, set it to True. Otherwise it's super confusing (and every call site needs to do this special comparison.)
| * shell crates.io API: set User-Agent and add a sleepIan Jackson2024-07-101-1/+3
| | | | | | | | See https://crates.io/data-access
| * shell crates.io: Fix a doc typoIan Jackson2024-07-101-1/+1
| |
* | maint/cargo-crate-owners: Add comment about empty filesIan Jackson2024-07-101-1/+4
| | | | | | | | | | Prompted by: https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2255#note_3046801
* | maint/cargo-crate-owners: Fix and comment sedderyIan Jackson2024-07-101-4/+6
| | | | | | | | | | | | | | Prompted by: https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2255#note_3046739 There is an improvement to comment semantics.
* | maint/cargo-crate-owners: Comment read_owners_overrideIan Jackson2024-07-101-0/+3
| | | | | | | | | | Prompted by: https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2255#note_3046737
* | maint/cargo-crate-owners: Implement override facilityIan Jackson2024-07-101-1/+53
| |
* | maint/cargo-crate-owners: Plan for override facilityIan Jackson2024-07-101-0/+42
|/
* Remove an obsolete RUSTSEC allowIan Jackson2024-07-091-18/+0
| | | | | We don't use the affected crates any more, now that arti-hyper is gone.
* Merge branch 'post-release' into 'main'Nick Mathewson2024-06-272-0/+72
|\ | | | | | | | | Release process improvements See merge request tpo/core/arti!2240
| * maint/tag-arti-releaes: New scriptIan Jackson2024-06-271-0/+36
| |
| * maint/changelog-syntax-fiddle: New scriptIan Jackson2024-06-271-0/+36
| |
* | maint/check-cli-help: Don't attempt to parse wrapped help lines.Gabriela Moldovan2024-06-271-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Skip parsing the next line unless it starts with two spaces followed by a non-whitespace character. This ensures we don't accidentally try to parse a wrapped help line as a command. This enables it to parse commands with wrapping descriptions, such as ``` Usage: arti hsc [OPTIONS] <COMMAND> Commands: prepare-service-discovery-key Prepare a service discovery key for connecting to a service running in restricted discovery mode help Print this message or the help of the given subcommand(s) ```
* | arti: Add an arti hsc subcommand.Gabriela Moldovan2024-06-271-1/+1
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds an experimental `arti hsc` subcommand for managing client state and keys. Currently, it only supports the `prepare-service-discovery-keys` operation described in #1281 and `doc/dev/notes/client-auth.md`. A note on terminology: I am referring to services that encrypt the second layer of their descriptor as running in "restricted discovery" mode (because they can only be discovered, i.e. have their IPT points found out, by a set of authorized clients). The corresponding client "auth" keys, being the keys that enable the client to find out the list of intro points, pow-params etc. of the service, are referred to as service "discovery keys". Alternative names I considered: * extra descriptor encryption: accurate, but overly technical. IMO, the CLI should be accessible to users who aren't familiar with the nitty-gritty of the protocol * shielded mode: good, but slightly misleading. Calling it "shielded mode" makes it sound like a universally desirable "extra protection" that should almost always be enabled (which is not the case). Seeing `shielded_mode = off` in the config might be worry operators that don't fully understand what "extra descriptor encryption" or "shielded mode" means * restricted mode: slightly inaccurate. It implies this mechanism is a good substitute for conventional service-side authentication, which it isn't (because client authorization isn't instantaneous) Closes #1281
* Explain in a comment why x32 is disabledIan Jackson2024-06-271-0/+1
|
* Disable x86_64-unknown-linux-gnux32 test caseIan Jackson2024-06-271-1/+1
| | | | | | | This only runs in scheduled jobs. And it doesn't work right now. It hasn't passed for at least a month, but it's not clear how much of that time it was being run because the osx failure would mask it.
* Remove arti-hyperIan Jackson2024-06-251-1/+0
| | | | | | This has been obsolete for a very long time. We have already published a version with a "won't be updated" warning.
* Update to base32 0.5Ian Jackson2024-06-251-1/+1
| | | | | | | No code changes needed. Precisely nailing-cargo -Eu upgrade --incompatible -p base32
* Update to itertools 0.13.0Ian Jackson2024-06-251-1/+1
| | | | | | | No code changes needed. Precisely nailing-cargo -Eu upgrade --incompatible -p itertools
* maint/crates-io-utils.sh: Try to deconfuse shellcheckIan Jackson2024-06-241-0/+6
|
* Remove check-crate-owners scriptIan Jackson2024-06-241-35/+0
| | | | | | | | This is superseded now. (I wish I had noticed it; perhaps I could have souped it up rather than writing a whole new thing, but I think the result would have been much the same.)
* maint/cargo-crate-owners: More sophisticated ownership check scriptIan Jackson2024-06-241-0/+90
| | | | | | | | | | | | | | | | | Compared to check-crate-owners: 1. Checks for uniformity, rather than having an embedded list of intended maintainers. 2. Uses curl | jq, rather than `cargo owner`. This is necessary for: 3. Ignores crates which have never been published. This is necessary to be able to run this in CI, since there may be new crates in the workspace. 4. Prints the ownership information rather differently - just the usernames. This is a consequence of using curl | jq.
* maint/crates-io-utils.sh: Add preserving tmp featureIan Jackson2024-06-241-2/+8
| | | | This is useful for debugging.
* maint/crates-io-utils.sh: Add exit status control featureIan Jackson2024-06-241-1/+5
|
* maint/crates-io-utils.sh: Break out from cargo-publishIan Jackson2024-06-242-30/+62
|
* shellcheck: check *.sh files tooIan Jackson2024-06-241-1/+4
| | | | | We (will) use `*.sh` for shell include files. We're about to make one of these.
* maint: Fix check-cli-help to pass shellcheckDavid Goulet2024-06-111-4/+3
| | | | Signed-off-by: David Goulet <[email protected]>
generated by cgit v1.2.3 (git 2.46.0) at 2026-08-26 23:20:23 +0000