martinvonz/jj
1
1
Fork 0
mirror of https://github.com/martinvonz/jj.git synced 2024-11-11 02:30:57 +03:00
Code Issues Packages Projects Releases Wiki Activity
c52e83e54d
jj/lib/Cargo.toml

51 lines
1.3 KiB
TOML
Raw Normal View History

import commit 0f15be02bf4012c116636913562691a0aaa7aed2 from my hg repo
2020-12-12 11:00:42 +03:00
[package]
project: rename project from Jujube to Jujutsu "Jujutsu" is probably much more familiar and relatable to most people. Also, I'm still not sure how "jujube" is supposed to be pronounced :P
2021-05-15 19:16:31 +03:00
name = "jujutsu-lib"
release: release version 0.4.0 This release is mostly about the fix for #177, which looks pretty bad even though I think it is actually harmless. It also has `jj log -p` contributed by @yuja!
2022-04-03 08:56:59 +03:00
version = "0.4.0"
import commit 0f15be02bf4012c116636913562691a0aaa7aed2 from my hg repo
2020-12-12 11:00:42 +03:00
authors = ["Martin von Zweigbergk <martinvonz@google.com>"]
cargo: upgrade to Rust 2021 (just to stay up to date)
2021-12-14 08:38:10 +03:00
edition = "2021"
cargo: upgrade protobuf crates to 3.0.1 The biggest difference in the API is that fields are now public. The exception from that is `oneof` fields, which still require setters and getters. I couldn't measure any difference in performance. I didn't expect any difference either, but it's good that it didn't seem to regress. I timed `jj debug operation <some hash prefix>`, which will read the whole operation log (to check that the prefix is unambiguous).
2022-05-02 18:53:50 +03:00
rust-version = "1.60"
cargo: fill in crates.io metadata
2021-01-03 19:45:07 +03:00
license = "Apache-2.0"
project: rename project from Jujube to Jujutsu "Jujutsu" is probably much more familiar and relatable to most people. Also, I'm still not sure how "jujube" is supposed to be pronounced :P
2021-05-15 19:16:31 +03:00
description = "Library for Jujutsu (an experimental VCS)"
cargo: fill in crates.io metadata
2021-01-03 19:45:07 +03:00
homepage = "https://github.com/martinvonz/jj"
repository = "https://github.com/martinvonz/jj"
project: rename project from Jujube to Jujutsu "Jujutsu" is probably much more familiar and relatable to most people. Also, I'm still not sure how "jujube" is supposed to be pronounced :P
2021-05-15 19:16:31 +03:00
documentation = "https://docs.rs/jujutsu"
cargo: fill in crates.io metadata
2021-01-03 19:45:07 +03:00
readme = "../README.md"
import commit 0f15be02bf4012c116636913562691a0aaa7aed2 from my hg repo
2020-12-12 11:00:42 +03:00
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
protobuf: generate code at build-time I had tried to generate the protobuf code at build time many months ago, but decided against it because it slowed down the build too much. I didn't realize there was the "cargo:rerun-if-changed=<filename>" feature that time. Given that that exists, it seems like an obvious win to generate the source code at build time. I put the generated sources in `$OUT_DIR` (where [1] says they should be), then include them in the `protos` module by using the `include!` macro. The biggest problem with that is that I couldn't get IntelliJ to understand it, even after enabling the experimental features described in [2]. [1] https://doc.rust-lang.org/cargo/reference/build-script-examples.html#code-generation [2] https://github.com/intellij-rust/intellij-rust/issues/1908#issuecomment-592773865
2020-12-24 10:12:18 +03:00
[build-dependencies]
cargo: upgrade protobuf crates to 3.0.1 The biggest difference in the API is that fields are now public. The exception from that is `oneof` fields, which still require setters and getters. I couldn't measure any difference in performance. I didn't expect any difference either, but it's good that it didn't seem to regress. I timed `jj debug operation <some hash prefix>`, which will read the whole operation log (to check that the prefix is unambiguous).
2022-05-02 18:53:50 +03:00
protobuf-codegen = "3.0.1"
build: conditionally use `map_first_last` feature if available
2022-02-21 09:14:13 +03:00
version_check = "0.9.4"
import commit 0f15be02bf4012c116636913562691a0aaa7aed2 from my hg repo
2020-12-12 11:00:42 +03:00
[dependencies]
cargo: upgrade backoff
2022-02-10 09:15:38 +03:00
backoff = "0.4.0"
cargo: bump blake2 from 0.10.2 to 0.10.4 Bumps [blake2](https://github.com/RustCrypto/hashes) from 0.10.2 to 0.10.4. - [Release notes](https://github.com/RustCrypto/hashes/releases) - [Commits](https://github.com/RustCrypto/hashes/commits) --- updated-dependencies: - dependency-name: blake2 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-03-17 07:10:14 +03:00
blake2 = "0.10.4"
cargo: bump bytes from 1.2.0 to 1.2.1 Bumps [bytes](https://github.com/tokio-rs/bytes) from 1.2.0 to 1.2.1. - [Release notes](https://github.com/tokio-rs/bytes/releases) - [Changelog](https://github.com/tokio-rs/bytes/blob/master/CHANGELOG.md) - [Commits](https://github.com/tokio-rs/bytes/commits) --- updated-dependencies: - dependency-name: bytes dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-08-01 18:46:23 +03:00
bytes = "1.2.1"
cargo: run `cargo upgrade` For no particular reason other than to stay up to date.
2021-11-30 20:14:21 +03:00
byteorder = "1.4.3"
chrono: update to latest version and disable `oldtime` feature `oldtime` brings in an old version of the `time` crate, which we don't need and has some issues reported in RustSec.
2022-08-22 21:28:34 +03:00
chrono = { version = "0.4.20", default-features = false, features = ["std", "clock"] }
cargo: bump config from 0.13.1 to 0.13.2 Bumps [config](https://github.com/mehcode/config-rs) from 0.13.1 to 0.13.2. - [Release notes](https://github.com/mehcode/config-rs/releases) - [Changelog](https://github.com/mehcode/config-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/mehcode/config-rs/compare/0.13.1...0.13.2) --- updated-dependencies: - dependency-name: config dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-08-02 18:35:49 +03:00
config = { version = "0.13.2", features = ["toml"] }
cargo: bump git2 from 0.14.4 to 0.15.0 Bumps [git2](https://github.com/rust-lang/git2-rs) from 0.14.4 to 0.15.0. - [Release notes](https://github.com/rust-lang/git2-rs/releases) - [Commits](https://github.com/rust-lang/git2-rs/compare/0.14.4...git2-curl-0.15.0) --- updated-dependencies: - dependency-name: git2 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-07-29 18:34:12 +03:00
git2 = "0.15.0"
cargo: run `cargo upgrade` For no particular reason other than to stay up to date.
2021-11-30 20:14:21 +03:00
hex = "0.4.3"
cargo: upgrade dependencies
2022-02-10 09:19:16 +03:00
itertools = "0.10.3"
tests: start using the maplit crate
2020-12-23 20:39:09 +03:00
maplit = "1.0.2"
cargo: bump pest from 2.2.0 to 2.2.1 Bumps [pest](https://github.com/pest-parser/pest) from 2.2.0 to 2.2.1. - [Release notes](https://github.com/pest-parser/pest/releases) - [Commits](https://github.com/pest-parser/pest/compare/v2.2.0...v2.2.1) --- updated-dependencies: - dependency-name: pest dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-08-01 18:46:27 +03:00
pest = "2.2.1"
cargo: bump pest_derive from 2.1.0 to 2.2.1 Bumps [pest_derive](https://github.com/pest-parser/pest) from 2.1.0 to 2.2.1. - [Release notes](https://github.com/pest-parser/pest/releases) - [Commits](https://github.com/pest-parser/pest/compare/v2.1.0...v2.2.1) --- updated-dependencies: - dependency-name: pest_derive dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-08-09 18:34:25 +03:00
pest_derive = "2.2.1"
cargo: upgrade protobuf crates to 3.0.1 The biggest difference in the API is that fields are now public. The exception from that is `oneof` fields, which still require setters and getters. I couldn't measure any difference in performance. I didn't expect any difference either, but it's good that it didn't seem to regress. I timed `jj debug operation <some hash prefix>`, which will read the whole operation log (to check that the prefix is unambiguous).
2022-05-02 18:53:50 +03:00
protobuf = { version = "3.0.1", features = ["with-bytes"] }
cargo: bump rand from 0.8.4 to 0.8.5 Bumps [rand](https://github.com/rust-random/rand) from 0.8.4 to 0.8.5. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.8.4...0.8.5) --- updated-dependencies: - dependency-name: rand dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-03-17 07:53:28 +03:00
rand = "0.8.5"
cargo: bump regex from 1.5.6 to 1.6.0 Bumps [regex](https://github.com/rust-lang/regex) from 1.5.6 to 1.6.0. - [Release notes](https://github.com/rust-lang/regex/releases) - [Changelog](https://github.com/rust-lang/regex/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/regex/compare/1.5.6...1.6.0) --- updated-dependencies: - dependency-name: regex dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-07-06 18:33:53 +03:00
regex = "1.6.0"
cargo: bump serde_json from 1.0.82 to 1.0.83 Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.82 to 1.0.83. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.82...v1.0.83) --- updated-dependencies: - dependency-name: serde_json dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-08-03 18:41:34 +03:00
serde_json = "1.0.83"
cargo: upgrade dependencies
2022-02-10 09:19:16 +03:00
tempfile = "3.3.0"
cargo: bump thiserror from 1.0.31 to 1.0.32 Bumps [thiserror](https://github.com/dtolnay/thiserror) from 1.0.31 to 1.0.32. - [Release notes](https://github.com/dtolnay/thiserror/releases) - [Commits](https://github.com/dtolnay/thiserror/compare/1.0.31...1.0.32) --- updated-dependencies: - dependency-name: thiserror dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-08-09 00:23:52 +03:00
thiserror = "1.0.32"
cargo: bump uuid from 1.1.1 to 1.1.2 Bumps [uuid](https://github.com/uuid-rs/uuid) from 1.1.1 to 1.1.2. - [Release notes](https://github.com/uuid-rs/uuid/releases) - [Commits](https://github.com/uuid-rs/uuid/compare/1.1.1...1.1.2) --- updated-dependencies: - dependency-name: uuid dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-06-13 18:58:47 +03:00
uuid = { version = "1.1.2", features = ["v4"] }
cargo: run `cargo upgrade` For no particular reason other than to stay up to date.
2021-11-30 20:14:21 +03:00
whoami = "1.2.1"
cargo: bump zstd from 0.11.1+zstd.1.5.2 to 0.11.2+zstd.1.5.2 Bumps [zstd](https://github.com/gyscos/zstd-rs) from 0.11.1+zstd.1.5.2 to 0.11.2+zstd.1.5.2. - [Release notes](https://github.com/gyscos/zstd-rs/releases) - [Commits](https://github.com/gyscos/zstd-rs/commits/v0.11.2) --- updated-dependencies: - dependency-name: zstd dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-05-13 18:27:28 +03:00
zstd = "0.11.2"
import commit 0f15be02bf4012c116636913562691a0aaa7aed2 from my hg repo
2020-12-12 11:00:42 +03:00
[dev-dependencies]
build: use `assert_matches` crate The `assert_matches` feature is nightly-only, so use this crate as a shim.
2022-02-21 08:45:09 +03:00
assert_matches = "1.5.0"
cargo: bump insta from 1.18.2 to 1.19.0 Bumps [insta](https://github.com/mitsuhiko/insta) from 1.18.2 to 1.19.0. - [Release notes](https://github.com/mitsuhiko/insta/releases) - [Changelog](https://github.com/mitsuhiko/insta/blob/master/CHANGELOG.md) - [Commits](https://github.com/mitsuhiko/insta/compare/1.18.2...1.19.0) --- updated-dependencies: - dependency-name: insta dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-08-22 18:35:21 +03:00
insta = "1.19.0"
cargo: upgrade dependencies
2022-02-10 09:19:16 +03:00
num_cpus = "1.13.1"
cargo: bump test-case from 2.1.0 to 2.2.1 Bumps [test-case](https://github.com/frondeus/test-case) from 2.1.0 to 2.2.1. - [Release notes](https://github.com/frondeus/test-case/releases) - [Changelog](https://github.com/frondeus/test-case/blob/master/CHANGELOG.md) - [Commits](https://github.com/frondeus/test-case/compare/v2.1.0...v2.2.1) --- updated-dependencies: - dependency-name: test-case dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-07-22 18:32:39 +03:00
test-case = "2.2.1"
cargo: use libgit2 with vendored OpenSSL (#73) I was able to build a working musl binary with this change, by running this command: ``` cargo build --release --target x86_64-unknown-linux-musl ``` Thanks to @arxanas for the tip.
2022-03-13 10:03:44 +03:00
[features]
vendored-openssl = ["git2/vendored-openssl"]
Reference in New Issue Copy Permalink