hasura/graphql-engine
1
0
Fork 0
mirror of https://github.com/hasura/graphql-engine.git synced 2024-12-15 17:31:56 +03:00
Code Issues Projects Releases Wiki Activity
fa9d91a1a5
graphql-engine/v3/Cargo.toml

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

137 lines
3.3 KiB
TOML
Raw Normal View History

v3: open-source hasura v3 engine Hasura V3 Engine v3.alpha.12-19-2023 V3-GitOrigin-RevId: 6605575a52b347b5e9a14ecd1cc736f113c663b3 PR-URL: https://github.com/hasura/graphql-engine-mono/pull/10567 Co-authored-by: Vishnu Bharathi <4211715+scriptnull@users.noreply.github.com> GitOrigin-RevId: 38c98a4b1971efe3ac724c2371c43ceb7d31f140
2023-12-19 12:04:02 +03:00
[workspace]
resolver = "2"
Set the crate properties once, to improve the Nix build. (#334) V3_GIT_ORIGIN_REV_ID: ec5f3d968306a64ad5c63df324ca5c524838c598
2024-03-06 20:14:24 +03:00
package.version = "0.1.0"
package.edition = "2021"
package.license = "Apache-2.0"
v3: open-source hasura v3 engine Hasura V3 Engine v3.alpha.12-19-2023 V3-GitOrigin-RevId: 6605575a52b347b5e9a14ecd1cc736f113c663b3 PR-URL: https://github.com/hasura/graphql-engine-mono/pull/10567 Co-authored-by: Vishnu Bharathi <4211715+scriptnull@users.noreply.github.com> GitOrigin-RevId: 38c98a4b1971efe3ac724c2371c43ceb7d31f140
2023-12-19 12:04:02 +03:00
members = [
create auth and utils subdirectories in crates, and move architecture information to a separate doc. (#534) ## Description 1. I've moved the architecture information we had in `CONTRIBUTING.md` to a separate document `docs/architecture.md` so we can evolve both separately in the future. 2. I've introduced a couple of sub directories: `utils` and `auth`, for supporting crates that are not the core functionality of the engine so it is easier to find the most relevant crates. New structure: ``` crates ├── auth │   ├── dev-auth-webhook │   ├── hasura-authn-core │   ├── hasura-authn-jwt │   └── hasura-authn-webhook ├── custom-connector ├── engine ├── lang-graphql ├── metadata-schema-generator ├── open-dds └── utils ├── opendds-derive ├── recursion_limit_macro └── tracing-util ``` V3_GIT_ORIGIN_REV_ID: e0e9394da2fcd911f329c48107a76f8492fa304c
2024-05-01 12:04:24 +03:00
"crates/auth/*",
"crates/custom-connector",
"crates/engine",
Split out `execute` crate (#588) <!-- Thank you for submitting this PR! :) --> ## Description Following `metadata-resolve` and `schema` crates, this splits out `execute`, the largest folder in `engine`. Undoubtedly this could be split further. Functional no-op. V3_GIT_ORIGIN_REV_ID: c272908153f78212d1f5dd58819707ac3cbcd439
2024-05-17 17:41:32 +03:00
"crates/execute",
Split out `IR` crate (#909) <!-- The PR description should answer 2 (maybe 3) important questions: --> ### What `execute` is now the biggest `crate` in engine and does a lot, let's split it into it's constituent steps. Functional no-op. <!-- What is this PR trying to accomplish (and why, if it's not obvious)? --> <!-- Consider: do we need to add a changelog entry? --> ### How Split out `ir` crate from the `execute` crate. Replace export of entire modules with that of specific types / functions. Therefore, consumers outside the crate talk about `ir::CommandInfo` rather than `ir::command::CommandInfo`. There is no need for other crates to know about the internal structure of this crate. <!-- How is it trying to accomplish it (what are the implementation steps)? --> V3_GIT_ORIGIN_REV_ID: 47553aec63e80af7f95e659a170a2685e9ac2ce3
2024-07-30 17:38:13 +03:00
"crates/ir",
create auth and utils subdirectories in crates, and move architecture information to a separate doc. (#534) ## Description 1. I've moved the architecture information we had in `CONTRIBUTING.md` to a separate document `docs/architecture.md` so we can evolve both separately in the future. 2. I've introduced a couple of sub directories: `utils` and `auth`, for supporting crates that are not the core functionality of the engine so it is easier to find the most relevant crates. New structure: ``` crates ├── auth │   ├── dev-auth-webhook │   ├── hasura-authn-core │   ├── hasura-authn-jwt │   └── hasura-authn-webhook ├── custom-connector ├── engine ├── lang-graphql ├── metadata-schema-generator ├── open-dds └── utils ├── opendds-derive ├── recursion_limit_macro └── tracing-util ``` V3_GIT_ORIGIN_REV_ID: e0e9394da2fcd911f329c48107a76f8492fa304c
2024-05-01 12:04:24 +03:00
"crates/lang-graphql",
Split `metadata-resolve` into own crate (#543) <!-- Thank you for submitting this PR! :) --> ## Description Now that metadata resolve has a clear interface with the rest of the engine, let's take it out into it's own crate. This will make it easier to maintain a strong boundary between things. To simplify imports etc, removed nested layers of modules, so now we import `use metadata_resolve::Qualified` instead of `use crate::metadata::resolved::Qualified`. The changes in `engine` crate are all just updating imports. Functional no-op. V3_GIT_ORIGIN_REV_ID: fb94304f7ed8883287c18bd6870045dfd69e3fe3
2024-05-02 15:28:27 +03:00
"crates/metadata-resolve",
create auth and utils subdirectories in crates, and move architecture information to a separate doc. (#534) ## Description 1. I've moved the architecture information we had in `CONTRIBUTING.md` to a separate document `docs/architecture.md` so we can evolve both separately in the future. 2. I've introduced a couple of sub directories: `utils` and `auth`, for supporting crates that are not the core functionality of the engine so it is easier to find the most relevant crates. New structure: ``` crates ├── auth │   ├── dev-auth-webhook │   ├── hasura-authn-core │   ├── hasura-authn-jwt │   └── hasura-authn-webhook ├── custom-connector ├── engine ├── lang-graphql ├── metadata-schema-generator ├── open-dds └── utils ├── opendds-derive ├── recursion_limit_macro └── tracing-util ``` V3_GIT_ORIGIN_REV_ID: e0e9394da2fcd911f329c48107a76f8492fa304c
2024-05-01 12:04:24 +03:00
"crates/metadata-schema-generator",
"crates/open-dds",
pre-execution plugin middleware (#771) The RFC: https://docs.google.com/document/d/1NB9fA6J8_dKtWknJkfTiqN5qWhPVDfYVOKFK25gYE7Y/edit The JIRA: https://hasurahq.atlassian.net/browse/V3ENGINE-234 <!-- The PR description should answer 2 (maybe 3) important questions: --> ### What <!-- What is this PR trying to accomplish (and why, if it's not obvious)? --> <!-- Consider: do we need to add a changelog entry? --> This PR adds a new middleware to the `/graphql` endpoint handler. This new middleware will be used to handle the pre-execution plugins. ### How <!-- How is it trying to accomplish it (what are the implementation steps)? --> We are doing something similar to https://github.com/tokio-rs/axum/blob/axum-v0.6.20/examples/consume-body-in-extractor-or-middleware/src/main.rs V3_GIT_ORIGIN_REV_ID: a7e0a7a252efd1f266b3e90df23a8307a9b35fc7
2024-07-03 15:57:38 +03:00
"crates/plugins/*",
data shape for query usage analytics (#606) ## Description The expectation is, that engine should emit usages of OpenDD objects (i.e. models, commands, relationships, permissions, fields of types etc.) from a GraphQL query. This PR adds the types required to gather query usage analytics, under a new crate `query-usage-analytics`. V3_GIT_ORIGIN_REV_ID: 49778c25a9019e0c8c9a2d13eaa8ba28638b8b55
2024-05-28 12:50:21 +03:00
"crates/query-usage-analytics",
Split `schema` into own crate (#556) <!-- Thank you for submitting this PR! :) --> ## Description This PR splits the GraphQL schema generation into the `schema` crate. Functional no-op. V3_GIT_ORIGIN_REV_ID: 4f1a91387305d88e9b5fbe4bc8df0575292cf878
2024-05-08 15:04:39 +03:00
"crates/schema",
Experimental SQL interface (#742) Adds a very experimental SQL interface to v3-engine for GenAI use cases. --------- Co-authored-by: Abhinav Gupta <127770473+abhinav-hasura@users.noreply.github.com> Co-authored-by: Gil Mizrahi <gil@gilmi.net> Co-authored-by: Anon Ray <ecthiender@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: 077779ec4e7843abdffdac1ed6aa655210649b93
2024-06-25 21:45:49 +03:00
"crates/sql",
create auth and utils subdirectories in crates, and move architecture information to a separate doc. (#534) ## Description 1. I've moved the architecture information we had in `CONTRIBUTING.md` to a separate document `docs/architecture.md` so we can evolve both separately in the future. 2. I've introduced a couple of sub directories: `utils` and `auth`, for supporting crates that are not the core functionality of the engine so it is easier to find the most relevant crates. New structure: ``` crates ├── auth │   ├── dev-auth-webhook │   ├── hasura-authn-core │   ├── hasura-authn-jwt │   └── hasura-authn-webhook ├── custom-connector ├── engine ├── lang-graphql ├── metadata-schema-generator ├── open-dds └── utils ├── opendds-derive ├── recursion_limit_macro └── tracing-util ``` V3_GIT_ORIGIN_REV_ID: e0e9394da2fcd911f329c48107a76f8492fa304c
2024-05-01 12:04:24 +03:00
"crates/utils/*",
v3: open-source hasura v3 engine Hasura V3 Engine v3.alpha.12-19-2023 V3-GitOrigin-RevId: 6605575a52b347b5e9a14ecd1cc736f113c663b3 PR-URL: https://github.com/hasura/graphql-engine-mono/pull/10567 Co-authored-by: Vishnu Bharathi <4211715+scriptnull@users.noreply.github.com> GitOrigin-RevId: 38c98a4b1971efe3ac724c2371c43ceb7d31f140
2023-12-19 12:04:02 +03:00
]
Reduce codegen units to 1 (#964) <!-- The PR description should answer 2 important questions: --> ### What By default, `rustc` splits crates up and builds in parallel. This is faster but misses some optimisations between these sections. Let's reduce it to increase runtime performance. ### How Add settings to `release` profile in `Cargo.toml`. <img width="776" alt="Screenshot 2024-08-13 at 12 59 46" src="https://github.com/user-attachments/assets/a03389dc-80ba-4723-8ca3-36af50846324"> V3_GIT_ORIGIN_REV_ID: 44fa511024140b680b30c9abfaa48034bf0845a9
2024-08-13 16:42:38 +03:00
# generally following guidance from https://nnethercote.github.io/perf-book/build-configuration.html
[profile.release]
codegen-units = 1 # reduce parallelisation to increase optimisations
use clippy settings in Cargo workspace (#441) <!-- Thank you for submitting this PR! :) --> ## Description Following the approach taken here: https://github.com/hasura/ndc-postgres/pull/402 This moves the `clippy` settings into the Cargo workspace file instead of passing them for each invocation. We enable all pedantic settings, run `cargo clippy --fix` to auto fix a few things, and then manually disable all other lints. Plenty of them are worth enabling and fixing in future IMO. --------- Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: aa0e6ccb8d72a7393e14b5c58b82077a67d9cb15
2024-04-08 13:13:26 +03:00
[workspace.lints.clippy]
all = { level = "warn", priority = -1 }
pedantic = { level = "warn", priority = -1 }
Ban `println!` in code with clippy (#711) <!-- Thank you for submitting this PR! :) --> ## Description A few debug lines slipped in recently, let's make `clippy` `warn` on those, so they are kicked out by CI. Functional no-op. V3_GIT_ORIGIN_REV_ID: 290f6de35f9315b68811eb5f15969fb0333e9d06
2024-06-24 14:46:07 +03:00
# ban printing to stdout and stderr
print_stdout = "warn"
print_stderr = "warn"
Remove redundant clones. (#752) I noticed a few extra calls to `.clone()` while working on an unrelated refactor. I want to remove them for brevity and simplicity; I don't expect a performance improvement. This turns on the Clippy warning `redundant_clone`, which detects unnecessary calls to `.clone()` (and `.to_string()`). It is an unstable warning and so might reports some false positives. If we find any, we can suppress the warning there. V3_GIT_ORIGIN_REV_ID: a713f29cf862d6f4cb40300105c6b9f96df00676
2024-06-24 17:08:11 +03:00
# unstable warnings; we might need to suppress them
redundant_clone = "warn"
Use Rust 1.79.0 (#751) <!-- Thank you for submitting this PR! :) --> ## Description Upgrade Rust, as a treat. Functional no-op. --------- Co-authored-by: Samir Talwar <samir@functional.computer> V3_GIT_ORIGIN_REV_ID: 1e0014049e89b8658326c8d8f652df800c415526
2024-06-28 01:21:04 +03:00
# disable this warning until
# https://github.com/rust-lang/rust-clippy/issues/12643 is fixed
manual_unwrap_or_default = "allow"
use clippy settings in Cargo workspace (#441) <!-- Thank you for submitting this PR! :) --> ## Description Following the approach taken here: https://github.com/hasura/ndc-postgres/pull/402 This moves the `clippy` settings into the Cargo workspace file instead of passing them for each invocation. We enable all pedantic settings, run `cargo clippy --fix` to auto fix a few things, and then manually disable all other lints. Plenty of them are worth enabling and fixing in future IMO. --------- Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: aa0e6ccb8d72a7393e14b5c58b82077a67d9cb15
2024-04-08 13:13:26 +03:00
# disable certain pedantic warnings
doc_markdown = "allow"
Semicolons, everywhere! (#700) If a function doesn't return a value, terminate with a semicolon. I also moved `implicit_hasher` and `return_self_not_must_use` to the "definitely keep disabling this" list, and installed [Bacon](https://dystroy.org/bacon/) in the Nix shell to make it easier to run Clippy. V3_GIT_ORIGIN_REV_ID: ffb17b42d982518aec433a1676dba0a0dd0ad95d
2024-06-11 18:32:43 +03:00
implicit_hasher = "allow"
use clippy settings in Cargo workspace (#441) <!-- Thank you for submitting this PR! :) --> ## Description Following the approach taken here: https://github.com/hasura/ndc-postgres/pull/402 This moves the `clippy` settings into the Cargo workspace file instead of passing them for each invocation. We enable all pedantic settings, run `cargo clippy --fix` to auto fix a few things, and then manually disable all other lints. Plenty of them are worth enabling and fixing in future IMO. --------- Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: aa0e6ccb8d72a7393e14b5c58b82077a67d9cb15
2024-04-08 13:13:26 +03:00
missing_errors_doc = "allow"
missing_panics_doc = "allow"
module_name_repetitions = "allow"
must_use_candidate = "allow"
Semicolons, everywhere! (#700) If a function doesn't return a value, terminate with a semicolon. I also moved `implicit_hasher` and `return_self_not_must_use` to the "definitely keep disabling this" list, and installed [Bacon](https://dystroy.org/bacon/) in the Nix shell to make it easier to run Clippy. V3_GIT_ORIGIN_REV_ID: ffb17b42d982518aec433a1676dba0a0dd0ad95d
2024-06-11 18:32:43 +03:00
return_self_not_must_use = "allow"
Apply a few lints to make it struct construction clearer. (#661) 1. Always name the struct when calling `default()`. 2. Sort construction according to the definitions. 3. Approve allowing `struct_field_names` because it doesn't seem to be helpful. 4. Enable `manual_string_new`; nothing seems to be triggering it now. V3_GIT_ORIGIN_REV_ID: 868742114b0bf27bc3ea03cdf1e63a0f710ebe33
2024-06-04 11:42:01 +03:00
struct_field_names = "allow"
use clippy settings in Cargo workspace (#441) <!-- Thank you for submitting this PR! :) --> ## Description Following the approach taken here: https://github.com/hasura/ndc-postgres/pull/402 This moves the `clippy` settings into the Cargo workspace file instead of passing them for each invocation. We enable all pedantic settings, run `cargo clippy --fix` to auto fix a few things, and then manually disable all other lints. Plenty of them are worth enabling and fixing in future IMO. --------- Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: aa0e6ccb8d72a7393e14b5c58b82077a67d9cb15
2024-04-08 13:13:26 +03:00
wildcard_imports = "allow"
# disable these for now, but we should probably fix them
result_large_err = "allow"
similar_names = "allow"
too_many_arguments = "allow"
too_many_lines = "allow"
unreadable_literal = "allow"
used_underscore_binding = "allow"
fix cargo doc warnings (#585) ## Description As advertised. Now you can run the following to browse our internal code ``` cargo doc --no-deps --document-private-items --open ``` V3_GIT_ORIGIN_REV_ID: 5b7091a00ed6148b8a91168807b07aa6a925cac9
2024-05-16 12:04:07 +03:00
[workspace.lints.rustdoc]
private_intra_doc_links = "allow"
Move all dependency versions into the workspace file. (#734) This keeps versions in one place so we can more easily ensure we upgrade crates together. V3_GIT_ORIGIN_REV_ID: 6a929bb6196c19a1f66a768585b669127035e9be
2024-06-20 15:25:06 +03:00
[workspace.dependencies]
Validate that the capabilities version matches the DataConnectorLink schema version (#880) This PR adds validation code to `metadata_resolve` that prevents someone from putting a schema/capabilities from the wrong NDC version into the DataConnectorLink while specifying a different schema version in the DataConnectorLink. For example: ``` kind: DataConnectorLink version: v1 definition: name: data_connector schema: version: v0.2 schema: {} capabilities: version: 0.1.5 # Not allowed for version v0.2! capabilities: {} ``` This PR has two commits. One is a refactor where we rearrange the DataConnectorError types so that the name of the data connector is captured centrally in `NamedDataConnectorError`, so that it doesn't have to be passed around and included in every error manually. The other is the validation changes to `metadata_resolve`. Completes APIPG-705 V3_GIT_ORIGIN_REV_ID: baed571f36f4cbed824ca546128f5df360d5b298
2024-07-25 17:30:31 +03:00
ndc-models = { git = "https://github.com/hasura/ndc-spec.git", tag = "v0.2.0-rc.0" } # When you update this tag, also update the schema references in crates/open-dds/src/data_connector.rs
Upgrade ndc_models to v0.2.0-rc0 (#835) This PR adds true support for ndc_models v0.2.0 to v3-engine. Note that v0.2.0 is not finalized yet, so we're pointing at v0.2.0-rc0. The support still comes via the migration methodology, where v0.2.x ndc models are downgraded to v0.1.x to support backwards compatibility. In the future we want to remove this and have the engine generate the different versioned ndc models separately instead of performing a migration. The ndc_models_v01 crate reference has been bumped to the official v0.1.5 version, which brings the newtypes to the v0.1.x version. The ndc_models crate reference is now on v0.2.0-rc0. The custom connector has been updated to support ndc-spec v0.2.0. All tests that talk to the custom connector have been updated with its latest v0.2.0 schema/capabilities. In `metadata_resolve` the v01->v02 schema/capabilities migration code has been updated to handle the new v0.2.0 types. This includes inferring v0.2.0 capabilities from what was possible in v0.1.x. In `execution`, the migration code has been updated to deal with the new v0.1.5 newtypes and v0.2.0 types. This means there are now cases where a downgrade is impossible and produces an error (see `NdcDowngradeError` in `execute::ndc::migration`). A bug has also been fixed where NDC expressions in arguments were not being serialized to the correct NDC version. V3_GIT_ORIGIN_REV_ID: 5b4afcde64c307b2bd7c985c588d6c74d9623a0f
2024-07-16 04:52:56 +03:00
ndc-models-v01 = { package = "ndc-models", git = "https://github.com/hasura/ndc-spec.git", tag = "v0.1.5" }
Move all dependency versions into the workspace file. (#734) This keeps versions in one place so we can more easily ensure we upgrade crates together. V3_GIT_ORIGIN_REV_ID: 6a929bb6196c19a1f66a768585b669127035e9be
2024-06-20 15:25:06 +03:00
anyhow = "1"
apollo-parser = "0.7"
async-graphql-parser = "7"
async-recursion = "1"
axum = "0.6"
base64 = "0.22"
bincode = "1"
bson = "2"
build-data = "0.2"
bytes = "1"
clap = "4"
convert_case = "0.6"
cookie = "0.18"
criterion = "0.5"
darling = "0.20"
derive_more = "0.99"
diffy = "0.4"
env_logger = "0.11"
expect-test = "1"
futures-util = "0.3"
goldenfile = "1"
graphql-parser = "0.4"
http = "0.2"
human_bytes = "0.4"
indexmap = "2"
insta = "1"
json_value_merge = "2"
jsonptr = "0.4"
jsonwebkey = "0.3"
jsonwebtoken = "8"
lexical-core = "0.8"
Use mimalloc (#961) <!-- The PR description should answer 2 important questions: --> ### What We started using `mimalloc` allocator in MBS a while ago with good results, let's use it here too. Once `v3-engine-multitenant` is merged we should use it there too. ### How Import crate, switch it on in engine binary and in benchmarks. <img width="845" alt="Screenshot 2024-08-13 at 10 10 49" src="https://github.com/user-attachments/assets/dc872668-1633-468a-86d3-51fca5be68bf"> V3_GIT_ORIGIN_REV_ID: ebad91bb57964477d0f227e341c7bd12d54f0f68
2024-08-13 12:54:08 +03:00
mimalloc = "0.1"
CI: Fix the Rust cache. (#942) ### What Try not to pollute the CI cache with the wrong thing. ### How 1. Remove the package selector as we don't care about production builds here any more. 2. Tell the test build to not save the cache so there is no write contention. 3. Downgrade `mockito` to v1.4 reduce the size of the cache, because `v1.5` depends on `http` v1. V3_GIT_ORIGIN_REV_ID: 2109c8c7db5d80e3b2c29d2949423e8faebd10b2
2024-08-07 18:02:33 +03:00
mockito = { version = "~1.4", default-features = false } # v1.5+ depends on http v1
Move all dependency versions into the workspace file. (#734) This keeps versions in one place so we can more easily ensure we upgrade crates together. V3_GIT_ORIGIN_REV_ID: 6a929bb6196c19a1f66a768585b669127035e9be
2024-06-20 15:25:06 +03:00
nonempty = "0.10"
openssl = "0.10"
opentelemetry = "0.22"
opentelemetry-contrib = "0.14"
opentelemetry-http = "0.11"
opentelemetry-otlp = "0.15"
opentelemetry-semantic-conventions = "0.14"
Stdout otel exporter (#776) ### What Output all traces to stdout. --------- Co-authored-by: Daniel Harvey <danieljamesharvey@gmail.com> V3_GIT_ORIGIN_REV_ID: 06330076ca305a331996530ddcd4d4c13d46bd95
2024-06-27 17:44:09 +03:00
opentelemetry-stdout = { version = "0.3", default-features = false }
Move all dependency versions into the workspace file. (#734) This keeps versions in one place so we can more easily ensure we upgrade crates together. V3_GIT_ORIGIN_REV_ID: 6a929bb6196c19a1f66a768585b669127035e9be
2024-06-20 15:25:06 +03:00
opentelemetry-zipkin = "0.20"
opentelemetry_sdk = "0.22"
postcard = "1"
pretty_assertions = "1"
proc-macro2 = "1"
quote = "1"
rand = "0.8"
ref-cast = "1"
regex = "1"
reqwest = "0.11"
rmp-serde = "1"
Validate that the capabilities version matches the DataConnectorLink schema version (#880) This PR adds validation code to `metadata_resolve` that prevents someone from putting a schema/capabilities from the wrong NDC version into the DataConnectorLink while specifying a different schema version in the DataConnectorLink. For example: ``` kind: DataConnectorLink version: v1 definition: name: data_connector schema: version: v0.2 schema: {} capabilities: version: 0.1.5 # Not allowed for version v0.2! capabilities: {} ``` This PR has two commits. One is a refactor where we rearrange the DataConnectorError types so that the name of the data connector is captured centrally in `NamedDataConnectorError`, so that it doesn't have to be passed around and included in every error manually. The other is the validation changes to `metadata_resolve`. Completes APIPG-705 V3_GIT_ORIGIN_REV_ID: baed571f36f4cbed824ca546128f5df360d5b298
2024-07-25 17:30:31 +03:00
semver = "1.0"
Move all dependency versions into the workspace file. (#734) This keeps versions in one place so we can more easily ensure we upgrade crates together. V3_GIT_ORIGIN_REV_ID: 6a929bb6196c19a1f66a768585b669127035e9be
2024-06-20 15:25:06 +03:00
schemars = "0.8"
serde = "1"
serde_json = "1"
serde_path_to_error = "0.1"
serde_with = "3"
sha2 = "0.10"
smol_str = "0.1"
strum = "0.26"
strum_macros = "0.26"
syn = "2"
thiserror = "1"
tokio = "1"
tokio-test = "0.4"
tower = "0.4"
tower-http = "0.4"
tracing = "0.1"
tracing-subscriber = "0.3"
transitive = "0.5"
url = "2"
Reference in New Issue Copy Permalink