vincenzopalazzo
/
arti
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
arti/crates/tor-hsservice/Cargo.toml

31 lines
1000 B
TOML
Raw Normal View History

Sketch an API for onion services.
2023-01-12 19:38:40 +00:00
[package]
name = "tor-hsservice"
Patchlevel bumps for crates whose dependencies just changed. These crates had no changes until just a moment ago. But since we updated the versions on some of their dependents, they have now changed themselves. Thus they get patchlevel bumps. ``` tor-rtmock tor-protover tor-socksproto tor-consdiff tor-chanmgr tor-dirclient tor-hsservice ```
2023-03-31 13:30:14 +01:00
version = "0.1.2"
Sketch an API for onion services.
2023-01-12 19:38:40 +00:00
authors = ["The Tor Project, Inc.", "Nick Mathewson <nickm@torproject.org>"]
edition = "2021"
rust-version = "1.60"
license = "MIT OR Apache-2.0"
homepage = "https://gitlab.torproject.org/tpo/core/arti/-/wikis/home"
description = "Arti's implementation of an onion service provider"
keywords = ["tor", "arti", "cryptography"]
categories = ["cryptography"]
repository = "https://gitlab.torproject.org/tpo/core/arti.git/"
publish = false
[features]
default = []
[dependencies]
async-trait = "0.1.2"
rand_core = "0.6.2"
thiserror = "1"
Bump patchlevel on crates with non-breaking changes For these crates, the changes are nontrivial, so we _do_ bump the versions on which their dependent crates depend. Fortunately, since they are all pre-1.0, we don't need to distinguish semver-additions from other changes. (Except for arti, which _is_ post-1.0, but gets a patchlevel bump anyway.) These are unstable crates with breaking changes: ``` tor-hscrypto tor-hsclient ``` These have new or extended APIs: ``` safelog tor-bytes tor-cell tor-linkspec tor-llcrypto tor-proto tor-cert arti-client ``` These have new unstable APIs or features: ``` tor-netdoc tor-circmgr (also broke some unstable APIs) arti (is post-1.0) ``` These have bugfixes only: ``` caret tor-dirmgr ```
2023-03-31 13:24:39 +01:00
tor-circmgr = { version = "0.7.3", path = "../tor-circmgr", features = ["hs-service"] }
tor-hscrypto = { version = "0.1.2", path = "../tor-hscrypto" }
tor-llcrypto = { version = "0.4.3", path = "../tor-llcrypto" }
Bump minor versions for significant breaking changes. This includes tor-cell, tor-proto, and tor-netdir.
2023-02-28 12:05:15 +00:00
tor-netdir = { version = "0.8.0", path = "../tor-netdir" }
Bump patchlevel on crates with non-breaking changes For these crates, the changes are nontrivial, so we _do_ bump the versions on which their dependent crates depend. Fortunately, since they are all pre-1.0, we don't need to distinguish semver-additions from other changes. (Except for arti, which _is_ post-1.0, but gets a patchlevel bump anyway.) These are unstable crates with breaking changes: ``` tor-hscrypto tor-hsclient ``` These have new or extended APIs: ``` safelog tor-bytes tor-cell tor-linkspec tor-llcrypto tor-proto tor-cert arti-client ``` These have new unstable APIs or features: ``` tor-netdoc tor-circmgr (also broke some unstable APIs) arti (is post-1.0) ``` These have bugfixes only: ``` caret tor-dirmgr ```
2023-03-31 13:24:39 +01:00
tor-proto = { version = "0.9.1", path = "../tor-proto" }
Bump the patch-level version of crates with _minor_ changes. These changes influence behavior, but not effect compatibility. (If I messed up, and any crate except for `arti` has non-breaking API changes, that's still fine, since they are all version 0.x.)
2023-02-01 15:23:58 +00:00
tor-rtcompat = { version = "0.8.1", path = "../tor-rtcompat" }
Sketch an API for onion services.
2023-01-12 19:38:40 +00:00
[dev-dependencies]