hasura/graphql-engine
1
0
Fork 0
mirror of https://github.com/hasura/graphql-engine.git synced 2025-01-08 08:44:24 +03:00
Code Issues Projects Releases Wiki Activity
af9f058d88
graphql-engine/v3/Cargo.lock

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

5590 lines
129 KiB
Plaintext
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
# This file is automatically @generated by Cargo.
# It is not intended for manual editing.
version = 3
[[package]]
name = "addr2line"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.22.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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "6e4503c46a5c0c7844e948c9a4d6acd9f50cccb4de1c48eb9e291ea17470c678"
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
dependencies = [
"gimli",
]
[[package]]
name = "adler"
version = "1.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f26201604c87b1e01bd3d98f8d5d9a8fcbb815e8cedb41ffccbeb4bf593a35fe"
Update to Rust v1.80.1. (#1002) ### What Upgrade to the latest version of Rust. ### How I modified `rust-toolchain.toml` and ran `cargo update`. V3_GIT_ORIGIN_REV_ID: 5fe675ee5dc568cd24de542c826ffd2d355f90ff
2024-08-22 11:08:47 +03:00
[[package]]
name = "adler2"
version = "2.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "512761e0bb2578dd7380c6baaa0f4ce03e84f95e960231d1dec8bf4d7d6e2627"
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
[[package]]
name = "ahash"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.8.11"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "e89da841a80418a9b391ebaea17f5c112ffaaa96f621d2c285b5174da76b9011"
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
dependencies = [
"cfg-if",
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
"const-random",
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
"getrandom",
"once_cell",
"version_check",
"zerocopy",
]
[[package]]
name = "aho-corasick"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "1.1.3"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "8e60d3430d3a69478ad0993f19238d2df97c507009a52b3c10addcd7f6bcb916"
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
dependencies = [
"memchr",
]
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
[[package]]
name = "alloc-no-stdlib"
version = "2.0.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "cc7bb162ec39d46ab1ca8c77bf72e890535becd1751bb45f64c597edb4c8c6b3"
[[package]]
name = "alloc-stdlib"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "94fb8275041c72129eb51b7d0322c29b8387a0386127718b096429201a5d6ece"
dependencies = [
"alloc-no-stdlib",
]
[[package]]
name = "allocator-api2"
version = "0.2.18"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5c6cb57a04249c6480766f7f7cef5467412af1490f8d1e243141daddada3264f"
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
[[package]]
name = "android-tzdata"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e999941b234f3131b00bc13c22d06e8c5ff726d1b6318ac7eb276997bbb4fef0"
[[package]]
name = "android_system_properties"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "819e7219dbd41043ac279b19830f2efc897156490d7fd6ea916720117ee66311"
dependencies = [
"libc",
]
[[package]]
name = "anes"
version = "0.1.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4b46cbb362ab8752921c97e041f5e366ee6297bd428a31275b9fcf1e380f7299"
[[package]]
name = "anstream"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.6.15"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "64e15c1ab1f89faffbf04a634d5e1962e9074f2741eef6d97f3c4e322426d526"
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
dependencies = [
"anstyle",
"anstyle-parse",
"anstyle-query",
"anstyle-wincon",
"colorchoice",
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
"is_terminal_polyfill",
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
"utf8parse",
]
[[package]]
name = "anstyle"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "1.0.8"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "1bec1de6f59aedf83baf9ff929c98f2ad654b97c9510f4e70cf6f661d49fd5b1"
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
[[package]]
name = "anstyle-parse"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.2.5"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "eb47de1e80c2b463c735db5b217a0ddc39d612e7ac9e2e96a5aed1f57616c1cb"
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
dependencies = [
"utf8parse",
]
[[package]]
name = "anstyle-query"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "1.1.1"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "6d36fc52c7f6c869915e99412912f22093507da8d9e942ceaf66fe4b7c14422a"
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
dependencies = [
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
"windows-sys 0.52.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
]
[[package]]
name = "anstyle-wincon"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "3.0.4"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "5bf74e1b6e971609db8ca7a9ce79fd5768ab6ae46441c572e46cf596f59e57f8"
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
dependencies = [
"anstyle",
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
"windows-sys 0.52.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
]
[[package]]
name = "anyhow"
Bump anyhow from 1.0.82 to 1.0.86 (#617) V3_GIT_ORIGIN_REV_ID: b5611a05dd14177ed1391edffa84dc8c82a355c6
2024-05-27 10:54:03 +03:00
version = "1.0.86"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump anyhow from 1.0.82 to 1.0.86 (#617) V3_GIT_ORIGIN_REV_ID: b5611a05dd14177ed1391edffa84dc8c82a355c6
2024-05-27 10:54:03 +03:00
checksum = "b3d1d046238990b9cf5bcde22a3fb3584ee5cf65fb2765f454ed428c7a0063da"
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
[[package]]
name = "apollo-parser"
Bump apollo-parser from 0.4.1 to 0.7.7 (#517) V3_GIT_ORIGIN_REV_ID: 13f05ec1a9a909c3b713b99df08a6d169a1b3a3a
2024-04-29 11:47:11 +03:00
version = "0.7.7"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump apollo-parser from 0.4.1 to 0.7.7 (#517) V3_GIT_ORIGIN_REV_ID: 13f05ec1a9a909c3b713b99df08a6d169a1b3a3a
2024-04-29 11:47:11 +03:00
checksum = "6bb7c8a9776825e5524b5ab3a7f478bf091a054180f244dff85814452cb87d90"
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
dependencies = [
Bump apollo-parser from 0.4.1 to 0.7.7 (#517) V3_GIT_ORIGIN_REV_ID: 13f05ec1a9a909c3b713b99df08a6d169a1b3a3a
2024-04-29 11:47:11 +03:00
"memchr",
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
"rowan",
"thiserror",
]
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
[[package]]
name = "arrayref"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.3.8"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "9d151e35f61089500b617991b791fc8bfd237ae50cd5950803758a179b41e67a"
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
[[package]]
name = "arrayvec"
Update to Rust v1.80.1. (#1002) ### What Upgrade to the latest version of Rust. ### How I modified `rust-toolchain.toml` and ran `cargo update`. V3_GIT_ORIGIN_REV_ID: 5fe675ee5dc568cd24de542c826ffd2d355f90ff
2024-08-22 11:08:47 +03:00
version = "0.7.6"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update to Rust v1.80.1. (#1002) ### What Upgrade to the latest version of Rust. ### How I modified `rust-toolchain.toml` and ran `cargo update`. V3_GIT_ORIGIN_REV_ID: 5fe675ee5dc568cd24de542c826ffd2d355f90ff
2024-08-22 11:08:47 +03:00
checksum = "7c02d123df017efcdfbd739ef81735b36c5ba83ec3c59c80a9d7ecc718f92e50"
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
[[package]]
name = "arrow"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
version = "52.2.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
checksum = "05048a8932648b63f21c37d88b552ccc8a65afb6dfe9fc9f30ce79174c2e7a85"
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
dependencies = [
"arrow-arith",
"arrow-array",
"arrow-buffer",
"arrow-cast",
"arrow-csv",
"arrow-data",
"arrow-ipc",
"arrow-json",
"arrow-ord",
"arrow-row",
"arrow-schema",
"arrow-select",
"arrow-string",
]
[[package]]
name = "arrow-arith"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
version = "52.2.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
checksum = "1d8a57966e43bfe9a3277984a14c24ec617ad874e4c0e1d2a1b083a39cfbf22c"
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
dependencies = [
"arrow-array",
"arrow-buffer",
"arrow-data",
"arrow-schema",
"chrono",
"half",
"num",
]
[[package]]
name = "arrow-array"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
version = "52.2.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
checksum = "16f4a9468c882dc66862cef4e1fd8423d47e67972377d85d80e022786427768c"
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
dependencies = [
"ahash",
"arrow-buffer",
"arrow-data",
"arrow-schema",
"chrono",
"chrono-tz",
"half",
"hashbrown 0.14.5",
"num",
]
[[package]]
name = "arrow-buffer"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
version = "52.2.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
checksum = "c975484888fc95ec4a632cdc98be39c085b1bb518531b0c80c5d462063e5daa1"
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
dependencies = [
"bytes",
"half",
"num",
]
[[package]]
name = "arrow-cast"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
version = "52.2.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
checksum = "da26719e76b81d8bc3faad1d4dbdc1bcc10d14704e63dc17fc9f3e7e1e567c8e"
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
dependencies = [
"arrow-array",
"arrow-buffer",
"arrow-data",
"arrow-schema",
"arrow-select",
"atoi",
"base64 0.22.1",
"chrono",
"comfy-table",
"half",
"lexical-core",
"num",
"ryu",
]
[[package]]
name = "arrow-csv"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
version = "52.2.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
checksum = "c13c36dc5ddf8c128df19bab27898eea64bf9da2b555ec1cd17a8ff57fba9ec2"
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
dependencies = [
"arrow-array",
"arrow-buffer",
"arrow-cast",
"arrow-data",
"arrow-schema",
"chrono",
"csv",
"csv-core",
"lazy_static",
"lexical-core",
"regex",
]
[[package]]
name = "arrow-data"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
version = "52.2.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
checksum = "dd9d6f18c65ef7a2573ab498c374d8ae364b4a4edf67105357491c031f716ca5"
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
dependencies = [
"arrow-buffer",
"arrow-schema",
"half",
"num",
]
[[package]]
name = "arrow-ipc"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
version = "52.2.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
checksum = "e786e1cdd952205d9a8afc69397b317cfbb6e0095e445c69cda7e8da5c1eeb0f"
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
dependencies = [
"arrow-array",
"arrow-buffer",
"arrow-cast",
"arrow-data",
"arrow-schema",
"flatbuffers",
"lz4_flex",
]
[[package]]
name = "arrow-json"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
version = "52.2.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
checksum = "fb22284c5a2a01d73cebfd88a33511a3234ab45d66086b2ca2d1228c3498e445"
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
dependencies = [
"arrow-array",
"arrow-buffer",
"arrow-cast",
"arrow-data",
"arrow-schema",
"chrono",
"half",
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"indexmap 2.4.0",
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
"lexical-core",
"num",
"serde",
"serde_json",
]
[[package]]
name = "arrow-ord"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
version = "52.2.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
checksum = "42745f86b1ab99ef96d1c0bcf49180848a64fe2c7a7a0d945bc64fa2b21ba9bc"
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
dependencies = [
"arrow-array",
"arrow-buffer",
"arrow-data",
"arrow-schema",
"arrow-select",
"half",
"num",
]
[[package]]
name = "arrow-row"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
version = "52.2.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
checksum = "4cd09a518c602a55bd406bcc291a967b284cfa7a63edfbf8b897ea4748aad23c"
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
dependencies = [
"ahash",
"arrow-array",
"arrow-buffer",
"arrow-data",
"arrow-schema",
"half",
]
[[package]]
name = "arrow-schema"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
version = "52.2.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
checksum = "9e972cd1ff4a4ccd22f86d3e53e835c2ed92e0eea6a3e8eadb72b4f1ac802cf8"
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
dependencies = [
"serde",
]
[[package]]
name = "arrow-select"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
version = "52.2.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
checksum = "600bae05d43483d216fb3494f8c32fdbefd8aa4e1de237e790dbb3d9f44690a3"
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
dependencies = [
"ahash",
"arrow-array",
"arrow-buffer",
"arrow-data",
"arrow-schema",
"num",
]
[[package]]
name = "arrow-string"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
version = "52.2.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
checksum = "f0dc1985b67cb45f6606a248ac2b4a288849f196bab8c657ea5589f47cdd55e6"
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
dependencies = [
"arrow-array",
"arrow-buffer",
"arrow-data",
"arrow-schema",
"arrow-select",
"memchr",
"num",
"regex",
"regex-syntax",
]
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
[[package]]
name = "ascii"
version = "0.9.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "eab1c04a571841102f5345a8fc0f6bb3d31c315dec879b5c6e42e40ce7ffa34e"
[[package]]
name = "assert-json-diff"
version = "2.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "47e4f2b81832e72834d7518d8487a0396a28cc408186a2e8854c0f98011faf12"
dependencies = [
"serde",
"serde_json",
]
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
[[package]]
name = "async-compression"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.4.12"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "fec134f64e2bc57411226dfc4e52dec859ddfc7e711fc5e07b612584f000e4aa"
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
dependencies = [
"bzip2",
"flate2",
"futures-core",
"futures-io",
"memchr",
"pin-project-lite",
"tokio",
"xz2",
"zstd",
"zstd-safe",
]
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
[[package]]
name = "async-graphql-parser"
Bump async-graphql-parser from 7.0.6 to 7.0.7 (#865) Bumps [async-graphql-parser](https://github.com/async-graphql/async-graphql) from 7.0.6 to 7.0.7. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/async-graphql/async-graphql/blob/master/CHANGELOG.md">async-graphql-parser's changelog</a>.</em></p> <blockquote> <h1>[7.0.7] 2024-07-14</h1> <ul> <li>Support raw values from serde_json <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1554">#1554</a></li> <li>The custom directive <code>ARGUMENT_DEFINITION</code> is not being output at the appropriate location in SDL <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1559">#1559</a></li> <li>Support for JSON extended representations of BSON ObjectId and Uuid <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1542">#1542</a></li> <li>feat: get directives from SelectionField <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1548">#1548</a></li> <li>Support Directives on Subscriptions <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1500">#1500</a></li> <li>fix subscription err typo <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1556">#1556</a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/async-graphql/async-graphql/commits">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=async-graphql-parser&package-manager=cargo&previous-version=7.0.6&new-version=7.0.7)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: 8c0d1a222a57c86cedf2f0870f6cccb0a861a3e6
2024-07-26 13:44:01 +03:00
version = "7.0.7"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump async-graphql-parser from 7.0.6 to 7.0.7 (#865) Bumps [async-graphql-parser](https://github.com/async-graphql/async-graphql) from 7.0.6 to 7.0.7. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/async-graphql/async-graphql/blob/master/CHANGELOG.md">async-graphql-parser's changelog</a>.</em></p> <blockquote> <h1>[7.0.7] 2024-07-14</h1> <ul> <li>Support raw values from serde_json <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1554">#1554</a></li> <li>The custom directive <code>ARGUMENT_DEFINITION</code> is not being output at the appropriate location in SDL <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1559">#1559</a></li> <li>Support for JSON extended representations of BSON ObjectId and Uuid <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1542">#1542</a></li> <li>feat: get directives from SelectionField <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1548">#1548</a></li> <li>Support Directives on Subscriptions <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1500">#1500</a></li> <li>fix subscription err typo <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1556">#1556</a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/async-graphql/async-graphql/commits">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=async-graphql-parser&package-manager=cargo&previous-version=7.0.6&new-version=7.0.7)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: 8c0d1a222a57c86cedf2f0870f6cccb0a861a3e6
2024-07-26 13:44:01 +03:00
checksum = "f801451484b4977d6fe67b29030f81353cabdcbb754e5a064f39493582dac0cf"
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
dependencies = [
"async-graphql-value",
"pest",
"serde",
"serde_json",
]
[[package]]
name = "async-graphql-value"
Bump async-graphql-parser from 7.0.6 to 7.0.7 (#865) Bumps [async-graphql-parser](https://github.com/async-graphql/async-graphql) from 7.0.6 to 7.0.7. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/async-graphql/async-graphql/blob/master/CHANGELOG.md">async-graphql-parser's changelog</a>.</em></p> <blockquote> <h1>[7.0.7] 2024-07-14</h1> <ul> <li>Support raw values from serde_json <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1554">#1554</a></li> <li>The custom directive <code>ARGUMENT_DEFINITION</code> is not being output at the appropriate location in SDL <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1559">#1559</a></li> <li>Support for JSON extended representations of BSON ObjectId and Uuid <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1542">#1542</a></li> <li>feat: get directives from SelectionField <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1548">#1548</a></li> <li>Support Directives on Subscriptions <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1500">#1500</a></li> <li>fix subscription err typo <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1556">#1556</a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/async-graphql/async-graphql/commits">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=async-graphql-parser&package-manager=cargo&previous-version=7.0.6&new-version=7.0.7)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: 8c0d1a222a57c86cedf2f0870f6cccb0a861a3e6
2024-07-26 13:44:01 +03:00
version = "7.0.7"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump async-graphql-parser from 7.0.6 to 7.0.7 (#865) Bumps [async-graphql-parser](https://github.com/async-graphql/async-graphql) from 7.0.6 to 7.0.7. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/async-graphql/async-graphql/blob/master/CHANGELOG.md">async-graphql-parser's changelog</a>.</em></p> <blockquote> <h1>[7.0.7] 2024-07-14</h1> <ul> <li>Support raw values from serde_json <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1554">#1554</a></li> <li>The custom directive <code>ARGUMENT_DEFINITION</code> is not being output at the appropriate location in SDL <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1559">#1559</a></li> <li>Support for JSON extended representations of BSON ObjectId and Uuid <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1542">#1542</a></li> <li>feat: get directives from SelectionField <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1548">#1548</a></li> <li>Support Directives on Subscriptions <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1500">#1500</a></li> <li>fix subscription err typo <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1556">#1556</a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/async-graphql/async-graphql/commits">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=async-graphql-parser&package-manager=cargo&previous-version=7.0.6&new-version=7.0.7)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: 8c0d1a222a57c86cedf2f0870f6cccb0a861a3e6
2024-07-26 13:44:01 +03:00
checksum = "69117c43c01d81a69890a9f5dd6235f2f027ca8d1ec62d6d3c5e01ca0edb4f2b"
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
dependencies = [
"bytes",
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"indexmap 2.4.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
"serde",
"serde_json",
]
[[package]]
name = "async-recursion"
Bump async-recursion from 1.1.0 to 1.1.1 (#550) V3_GIT_ORIGIN_REV_ID: cc078462ec7713139875b0991e86f670d81b7ae6
2024-05-07 11:04:45 +03:00
version = "1.1.1"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump async-recursion from 1.1.0 to 1.1.1 (#550) V3_GIT_ORIGIN_REV_ID: cc078462ec7713139875b0991e86f670d81b7ae6
2024-05-07 11:04:45 +03:00
checksum = "3b43422f69d8ff38f95f1b2bb76517c91589a924d1559a0e935d7c8ce0274c11"
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
dependencies = [
"proc-macro2",
"quote",
Bump syn from 2.0.75 to 2.0.76 (#1017) Bumps [syn](https://github.com/dtolnay/syn) from 2.0.75 to 2.0.76. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/syn/releases">syn's releases</a>.</em></p> <blockquote> <h2>2.0.76</h2> <ul> <li>Enforce that tail call <code>become</code> keyword is followed by an expression (<a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/syn/commit/ef3e9c6dde79be7590fc90278772663ca31c1a73"><code>ef3e9c6</code></a> Release 2.0.76</li> <li><a href="https://github.com/dtolnay/syn/commit/8f7365ff9685c8ca9527c2de409204179a3efcdf"><code>8f7365f</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a> from dtolnay/tailcall</li> <li><a href="https://github.com/dtolnay/syn/commit/6cddd9ea714fe034466b4f02d3f7abb484c65ea0"><code>6cddd9e</code></a> Make tail call expr mandatory</li> <li>See full diff in <a href="https://github.com/dtolnay/syn/compare/2.0.75...2.0.76">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=syn&package-manager=cargo&previous-version=2.0.75&new-version=2.0.76)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d261ad30ffeb10034a80f9044504cb9d6c7c1ff7
2024-08-26 14:39:45 +03:00
"syn 2.0.76",
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
]
[[package]]
name = "async-stream"
version = "0.3.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "cd56dd203fef61ac097dd65721a419ddccb106b2d2b70ba60a6b529f03961a51"
dependencies = [
"async-stream-impl",
"futures-core",
"pin-project-lite",
]
[[package]]
name = "async-stream-impl"
version = "0.3.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "16e62a023e7c117e27523144c5d2459f4397fcc3cab0085af8e2224f643a0193"
dependencies = [
"proc-macro2",
"quote",
Bump syn from 2.0.75 to 2.0.76 (#1017) Bumps [syn](https://github.com/dtolnay/syn) from 2.0.75 to 2.0.76. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/syn/releases">syn's releases</a>.</em></p> <blockquote> <h2>2.0.76</h2> <ul> <li>Enforce that tail call <code>become</code> keyword is followed by an expression (<a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/syn/commit/ef3e9c6dde79be7590fc90278772663ca31c1a73"><code>ef3e9c6</code></a> Release 2.0.76</li> <li><a href="https://github.com/dtolnay/syn/commit/8f7365ff9685c8ca9527c2de409204179a3efcdf"><code>8f7365f</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a> from dtolnay/tailcall</li> <li><a href="https://github.com/dtolnay/syn/commit/6cddd9ea714fe034466b4f02d3f7abb484c65ea0"><code>6cddd9e</code></a> Make tail call expr mandatory</li> <li>See full diff in <a href="https://github.com/dtolnay/syn/compare/2.0.75...2.0.76">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=syn&package-manager=cargo&previous-version=2.0.75&new-version=2.0.76)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d261ad30ffeb10034a80f9044504cb9d6c7c1ff7
2024-08-26 14:39:45 +03:00
"syn 2.0.76",
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
]
[[package]]
name = "async-trait"
Bump async-trait from 0.1.80 to 0.1.81 (#804) Bumps [async-trait](https://github.com/dtolnay/async-trait) from 0.1.80 to 0.1.81. V3_GIT_ORIGIN_REV_ID: 1e9a6a6a40b6b0f732774df1e7a52b8a182f70c1
2024-07-08 11:31:17 +03:00
version = "0.1.81"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump async-trait from 0.1.80 to 0.1.81 (#804) Bumps [async-trait](https://github.com/dtolnay/async-trait) from 0.1.80 to 0.1.81. V3_GIT_ORIGIN_REV_ID: 1e9a6a6a40b6b0f732774df1e7a52b8a182f70c1
2024-07-08 11:31:17 +03:00
checksum = "6e0c28dcc82d7c8ead5cb13beb15405b57b8546e93215673ff8ca0349a028107"
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
dependencies = [
"proc-macro2",
"quote",
Bump syn from 2.0.75 to 2.0.76 (#1017) Bumps [syn](https://github.com/dtolnay/syn) from 2.0.75 to 2.0.76. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/syn/releases">syn's releases</a>.</em></p> <blockquote> <h2>2.0.76</h2> <ul> <li>Enforce that tail call <code>become</code> keyword is followed by an expression (<a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/syn/commit/ef3e9c6dde79be7590fc90278772663ca31c1a73"><code>ef3e9c6</code></a> Release 2.0.76</li> <li><a href="https://github.com/dtolnay/syn/commit/8f7365ff9685c8ca9527c2de409204179a3efcdf"><code>8f7365f</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a> from dtolnay/tailcall</li> <li><a href="https://github.com/dtolnay/syn/commit/6cddd9ea714fe034466b4f02d3f7abb484c65ea0"><code>6cddd9e</code></a> Make tail call expr mandatory</li> <li>See full diff in <a href="https://github.com/dtolnay/syn/compare/2.0.75...2.0.76">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=syn&package-manager=cargo&previous-version=2.0.75&new-version=2.0.76)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d261ad30ffeb10034a80f9044504cb9d6c7c1ff7
2024-08-26 14:39:45 +03:00
"syn 2.0.76",
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
]
[[package]]
name = "atoi"
version = "2.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f28d99ec8bfea296261ca1af174f24225171fea9664ba9003cbebee704810528"
dependencies = [
"num-traits",
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
]
[[package]]
name = "atomic-polyfill"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "1.0.3"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "8cf2bce30dfe09ef0bfaef228b9d414faaf7e563035494d7fe092dba54b300f4"
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
dependencies = [
"critical-section",
]
[[package]]
name = "autocfg"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "1.3.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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "0c4b4d0bd25bd0b74681c0ad21497610ce1b7c91b1022cd21c80c6fbdd9476b0"
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
[[package]]
name = "axum"
version = "0.6.20"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3b829e4e32b91e643de6eafe82b1d90675f5874230191a4ffbc1b336dec4d6bf"
dependencies = [
"async-trait",
"axum-core",
"bitflags 1.3.2",
"bytes",
"futures-util",
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
"http",
"http-body",
"hyper",
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
"itoa",
"matchit",
"memchr",
"mime",
Remove unused dependencies using `cargo machete`. (#413) `cargo machete` is a very useful tool that figures out when you aren't using a dependency. I have run this locally to remove unused dependencies. I've also added a CI job to make sure we catch these in the future. Sometimes it reports false positives, e.g. when a dependency isn't used directly but in macro-generated code (e.g. with `strum`). I have added `"ignored"` clauses to the `Cargo.toml` files where appropriate. V3_GIT_ORIGIN_REV_ID: ed015089b695cec8eeb03ce455d6dd3cd312a016
2024-03-28 12:16:54 +03:00
"percent-encoding",
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
"pin-project-lite",
"rustversion",
"serde",
"serde_json",
"serde_path_to_error",
"serde_urlencoded",
"sync_wrapper",
"tokio",
"tower",
"tower-layer",
"tower-service",
]
[[package]]
name = "axum-core"
version = "0.3.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "759fa577a247914fd3f7f76d62972792636412fbfd634cd452f6a385a74d2d2c"
dependencies = [
"async-trait",
"bytes",
"futures-util",
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
"http",
"http-body",
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
"mime",
"rustversion",
"tower-layer",
"tower-service",
]
Add graceful shutdown to all cloud servers (#1023) <!-- The PR description should answer 2 important questions: --> ### What Put graceful shutdown code in a new crate. ### How <!-- How is it trying to accomplish it (what are the implementation steps)? --> V3_GIT_ORIGIN_REV_ID: 262cd85064f0420d2170a3bf710ab72853b5764d
2024-08-28 13:23:08 +03:00
[[package]]
name = "axum-ext"
version = "3.0.0"
dependencies = [
"tokio",
]
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
[[package]]
name = "backtrace"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.3.73"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "5cc23269a4f8976d0a4d2e7109211a419fe30e8d88d677cd60b6bc79c5732e0a"
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
dependencies = [
"addr2line",
"cc",
"cfg-if",
"libc",
Update to Rust v1.80.1. (#1002) ### What Upgrade to the latest version of Rust. ### How I modified `rust-toolchain.toml` and ran `cargo update`. V3_GIT_ORIGIN_REV_ID: 5fe675ee5dc568cd24de542c826ffd2d355f90ff
2024-08-22 11:08:47 +03:00
"miniz_oxide 0.7.4",
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
"object",
"rustc-demangle",
]
[[package]]
name = "base64"
version = "0.13.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9e1b586273c5702936fe7b7d6896644d8be71e6314cfe09d3167c95f712589e8"
[[package]]
name = "base64"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.21.7"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "9d297deb1925b89f2ccc13d7635fa0714f12c87adce1c75356b39ca9b7178567"
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
Bump base64 from 0.21.7 to 0.22.0 (#488) V3_GIT_ORIGIN_REV_ID: b5706296b08d72e4dceeb475c48d94399746f49d
2024-04-22 12:18:14 +03:00
[[package]]
name = "base64"
Bump base64 from 0.22.0 to 0.22.1 (#551) V3_GIT_ORIGIN_REV_ID: 5cebb181c8edd4dc539ce7166156cc9a2d6c47a4
2024-05-07 11:21:15 +03:00
version = "0.22.1"
Bump base64 from 0.21.7 to 0.22.0 (#488) V3_GIT_ORIGIN_REV_ID: b5706296b08d72e4dceeb475c48d94399746f49d
2024-04-22 12:18:14 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump base64 from 0.22.0 to 0.22.1 (#551) V3_GIT_ORIGIN_REV_ID: 5cebb181c8edd4dc539ce7166156cc9a2d6c47a4
2024-05-07 11:21:15 +03:00
checksum = "72b3254f16251a8381aa12e40e3c4d2f0199f8c6508fbecb9d91f575e0fbb8c6"
Bump base64 from 0.21.7 to 0.22.0 (#488) V3_GIT_ORIGIN_REV_ID: b5706296b08d72e4dceeb475c48d94399746f49d
2024-04-22 12:18:14 +03:00
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
[[package]]
name = "bincode"
version = "1.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b1f45e9417d87227c7a56d22e471c6206462cba514c7590c09aff4cf6d1ddcad"
dependencies = [
"serde",
]
[[package]]
name = "bitflags"
version = "1.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bef38d45163c2f1dde094a7dfd33ccf595c92905c8f8f4fdc18d06fb1037718a"
[[package]]
name = "bitflags"
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
version = "2.6.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
source = "registry+https://github.com/rust-lang/crates.io-index"
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
checksum = "b048fb63fd8b5923fc5aa7b340d8e156aec7ec02f0c78fa8a6ddc2613f6f71de"
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
[[package]]
name = "bitvec"
version = "1.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1bc2832c24239b0141d5674bb9174f9d68a8b5b3f2753311927c172ca46f7e9c"
dependencies = [
"funty",
"radium",
"tap",
"wyz",
]
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
[[package]]
name = "blake2"
version = "0.10.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "46502ad458c9a52b69d4d4d32775c788b7a1b85e8bc9d482d92250fc0e3f8efe"
dependencies = [
"digest 0.10.7",
]
[[package]]
name = "blake3"
Update to Rust v1.80.1. (#1002) ### What Upgrade to the latest version of Rust. ### How I modified `rust-toolchain.toml` and ran `cargo update`. V3_GIT_ORIGIN_REV_ID: 5fe675ee5dc568cd24de542c826ffd2d355f90ff
2024-08-22 11:08:47 +03:00
version = "1.5.4"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update to Rust v1.80.1. (#1002) ### What Upgrade to the latest version of Rust. ### How I modified `rust-toolchain.toml` and ran `cargo update`. V3_GIT_ORIGIN_REV_ID: 5fe675ee5dc568cd24de542c826ffd2d355f90ff
2024-08-22 11:08:47 +03:00
checksum = "d82033247fd8e890df8f740e407ad4d038debb9eb1f40533fffb32e7d17dc6f7"
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
dependencies = [
"arrayref",
"arrayvec",
"cc",
"cfg-if",
"constant_time_eq",
]
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
[[package]]
name = "block-buffer"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4152116fd6e9dadb291ae18fc1ec3575ed6d84c29642d97890f4b4a3417297e4"
dependencies = [
"generic-array",
]
add field arguments in schema and execution (#695) ### TODO - [x] Validate the presence of arguments in the data connector schema - [x] Add test for IR - [x] Add test using custom connector ## Description JIRA: https://hasurahq.atlassian.net/browse/V3ENGINE-148 This is part 2 of the field arguments. This will add the field arguments to the graphql schema and also handles the execution part. ![image](https://github.com/hasura/v3-engine/assets/85472423/c8f55d70-6539-42ef-ab5a-91b74e5699e2) ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> Add support for field arguments <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> --------- Co-authored-by: Anon Ray <ecthiender@users.noreply.github.com> Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: ea06b896feaca30419f81cd070fd4cfd608ef35b
2024-06-19 11:14:24 +03:00
[[package]]
name = "block-buffer"
version = "0.10.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3078c7629b62d3f0439517fa394996acacc5cbc91c5a20d8c658e77abd503a71"
dependencies = [
"generic-array",
]
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
[[package]]
name = "brotli"
version = "6.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "74f7971dbd9326d58187408ab83117d8ac1bb9c17b085fdacd1cf2f598719b6b"
dependencies = [
"alloc-no-stdlib",
"alloc-stdlib",
"brotli-decompressor",
]
[[package]]
name = "brotli-decompressor"
version = "4.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9a45bd2e4095a8b518033b128020dd4a55aab1c0a381ba4404a472630f4bc362"
dependencies = [
"alloc-no-stdlib",
"alloc-stdlib",
]
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
[[package]]
name = "bson"
Bump bson from 2.10.0 to 2.11.0 (#689) Bumps [bson](https://github.com/mongodb/bson-rust) from 2.10.0 to 2.11.0. V3_GIT_ORIGIN_REV_ID: e89e67fbaf4be2c98aabb5b1d504dc4684460763
2024-06-10 08:17:26 +03:00
version = "2.11.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
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump bson from 2.10.0 to 2.11.0 (#689) Bumps [bson](https://github.com/mongodb/bson-rust) from 2.10.0 to 2.11.0. V3_GIT_ORIGIN_REV_ID: e89e67fbaf4be2c98aabb5b1d504dc4684460763
2024-06-10 08:17:26 +03:00
checksum = "d8a88e82b9106923b5c4d6edfca9e7db958d4e98a478ec115022e81b9b38e2c8"
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
dependencies = [
"ahash",
"base64 0.13.1",
"bitvec",
"hex",
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"indexmap 2.4.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
"js-sys",
"once_cell",
"rand",
"serde",
"serde_bytes",
"serde_json",
"time",
"uuid",
]
[[package]]
name = "bstr"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "1.10.0"
Take snapshots of passing and failing metadata resolution. (#763) ### What In order to more easily monitor and review changes to metadata resolution, this introduces snapshot testing for both successful and failing calls to `resolve`. I used [Insta](https://insta.rs/) for this. ### How For tests of the failure case, we already had a text file with the expected error, so I have turned those files into snapshot files. I wrote a small script to move the files rather than deleting and recreating them so I could guarantee that the contents have not changed. (Unfortunately, Git's diff doesn't always recognise the move as a move because Insta has added a header.) For tests of the successful case, I added a line to snapshot the metadata rather than discarding it. I also rewrote the tests to use `insta::glob` so we could get rid of `test_each`. V3_GIT_ORIGIN_REV_ID: 41bef4cf77bddb8d20d7c101df52ae149e8b0476
2024-06-26 11:14:34 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "40723b8fb387abc38f4f4a37c09073622e41dd12327033091ef8950659e6dc0c"
Take snapshots of passing and failing metadata resolution. (#763) ### What In order to more easily monitor and review changes to metadata resolution, this introduces snapshot testing for both successful and failing calls to `resolve`. I used [Insta](https://insta.rs/) for this. ### How For tests of the failure case, we already had a text file with the expected error, so I have turned those files into snapshot files. I wrote a small script to move the files rather than deleting and recreating them so I could guarantee that the contents have not changed. (Unfortunately, Git's diff doesn't always recognise the move as a move because Insta has added a header.) For tests of the successful case, I added a line to snapshot the metadata rather than discarding it. I also rewrote the tests to use `insta::glob` so we could get rid of `test_each`. V3_GIT_ORIGIN_REV_ID: 41bef4cf77bddb8d20d7c101df52ae149e8b0476
2024-06-26 11:14:34 +03:00
dependencies = [
"memchr",
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"regex-automata",
Take snapshots of passing and failing metadata resolution. (#763) ### What In order to more easily monitor and review changes to metadata resolution, this introduces snapshot testing for both successful and failing calls to `resolve`. I used [Insta](https://insta.rs/) for this. ### How For tests of the failure case, we already had a text file with the expected error, so I have turned those files into snapshot files. I wrote a small script to move the files rather than deleting and recreating them so I could guarantee that the contents have not changed. (Unfortunately, Git's diff doesn't always recognise the move as a move because Insta has added a header.) For tests of the successful case, I added a line to snapshot the metadata rather than discarding it. I also rewrote the tests to use `insta::glob` so we could get rid of `test_each`. V3_GIT_ORIGIN_REV_ID: 41bef4cf77bddb8d20d7c101df52ae149e8b0476
2024-06-26 11:14:34 +03:00
"serde",
]
use short commit SHA as version and mark non-release builds as dev (#295) V3_GIT_ORIGIN_REV_ID: 78475725003cd57790361caa8659c7a7146eacf2
2024-01-25 11:53:24 +03:00
[[package]]
name = "build-data"
Bump build-data from 0.1.5 to 0.2.1 (#688) Bumps [build-data](https://gitlab.com/leonhard-llc/ops) from 0.1.5 to 0.2.1. V3_GIT_ORIGIN_REV_ID: 5e2b922820ecb44706f6a628d5dcb60c8ad5df76
2024-06-10 09:01:09 +03:00
version = "0.2.1"
use short commit SHA as version and mark non-release builds as dev (#295) V3_GIT_ORIGIN_REV_ID: 78475725003cd57790361caa8659c7a7146eacf2
2024-01-25 11:53:24 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump build-data from 0.1.5 to 0.2.1 (#688) Bumps [build-data](https://gitlab.com/leonhard-llc/ops) from 0.1.5 to 0.2.1. V3_GIT_ORIGIN_REV_ID: 5e2b922820ecb44706f6a628d5dcb60c8ad5df76
2024-06-10 09:01:09 +03:00
checksum = "eda20fcece9c23f3c3f4c2751a8a5ca9491c05fa7a69920af65953c3b39b7ce4"
use short commit SHA as version and mark non-release builds as dev (#295) V3_GIT_ORIGIN_REV_ID: 78475725003cd57790361caa8659c7a7146eacf2
2024-01-25 11:53:24 +03:00
dependencies = [
"chrono",
"safe-regex",
]
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
[[package]]
name = "bumpalo"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "3.16.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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "79296716171880943b8470b5f8d03aa55eb2e645a4874bdbb28adb49162e012c"
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
[[package]]
name = "byteorder"
version = "1.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1fd0f2584146f6f2ef48085050886acf353beff7305ebd1ae69500e27c67f64b"
[[package]]
name = "bytes"
Bump bytes from 1.6.1 to 1.7.1 (#927) Bumps [bytes](https://github.com/tokio-rs/bytes) from 1.6.1 to 1.7.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/tokio-rs/bytes/releases">bytes's releases</a>.</em></p> <blockquote> <h2>Bytes 1.7.1</h2> <h1>1.7.1 (August 1, 2024)</h1> <p>This release reverts the following change due to a regression:</p> <ul> <li>Reuse capacity when possible in <code>&lt;BytesMut as Buf&gt;::advance</code> impl (<a href="https://redirect.github.com/tokio-rs/bytes/issues/698">#698</a>)</li> </ul> <p>The revert can be found at <a href="https://redirect.github.com/tokio-rs/bytes/issues/726">#726</a>.</p> <h2>Bytes 1.7.0</h2> <h1>1.7.0 (July 31, 2024)</h1> <h3>Added</h3> <ul> <li>Add conversion from <code>Bytes</code> to <code>BytesMut</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/695">#695</a>, <a href="https://redirect.github.com/tokio-rs/bytes/issues/710">#710</a>)</li> <li>Add reclaim method without additional allocation (<a href="https://redirect.github.com/tokio-rs/bytes/issues/686">#686</a>)</li> </ul> <h3>Documented</h3> <ul> <li>Clarify how <code>BytesMut::zeroed</code> works (<a href="https://redirect.github.com/tokio-rs/bytes/issues/714">#714</a>)</li> <li>Clarify the behavior of <code>Buf::chunk</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/717">#717</a>)</li> </ul> <h3>Changed</h3> <ul> <li>Change length condition of <code>BytesMut::truncate</code></li> <li>Reuse capacity when possible in <code>&lt;BytesMut as Buf&gt;::advance</code> impl (<a href="https://redirect.github.com/tokio-rs/bytes/issues/698">#698</a>)</li> <li>Improve <code>must_use</code> suggestion of <code>BytesMut::split</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/699">#699</a>)</li> </ul> <h3>Internal changes</h3> <ul> <li>Use <code>ManuallyDrop</code> instead of <code>mem::forget</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/678">#678</a>)</li> <li>Don't set <code>len</code> in <code>BytesMut::reserve</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/682">#682</a>)</li> <li>Optimize <code>Bytes::copy_to_bytes</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/688">#688</a>)</li> <li>Refactor <code>BytesMut::truncate</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/694">#694</a>)</li> <li>Refactor <code>BytesMut::resize</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/696">#696</a>)</li> <li>Reorder assertion in <code>Bytes::split_to</code>, <code>Bytes::split_off</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/689">#689</a>, <a href="https://redirect.github.com/tokio-rs/bytes/issues/693">#693</a>)</li> <li>Use <code>offset_from</code> in more places (<a href="https://redirect.github.com/tokio-rs/bytes/issues/705">#705</a>)</li> <li>Correct the wrong usage of <code>IntoIter</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/707">#707</a>)</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/tokio-rs/bytes/blob/master/CHANGELOG.md">bytes's changelog</a>.</em></p> <blockquote> <h1>1.7.1 (August 1, 2024)</h1> <p>This release reverts the following change due to a regression:</p> <ul> <li>Reuse capacity when possible in <code>&lt;BytesMut as Buf&gt;::advance</code> impl (<a href="https://redirect.github.com/tokio-rs/bytes/issues/698">#698</a>)</li> </ul> <p>The revert can be found at <a href="https://redirect.github.com/tokio-rs/bytes/issues/726">#726</a>.</p> <h1>1.7.0 (July 31, 2024)</h1> <h3>Added</h3> <ul> <li>Add conversion from <code>Bytes</code> to <code>BytesMut</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/695">#695</a>, <a href="https://redirect.github.com/tokio-rs/bytes/issues/710">#710</a>)</li> <li>Add reclaim method without additional allocation (<a href="https://redirect.github.com/tokio-rs/bytes/issues/686">#686</a>)</li> </ul> <h3>Documented</h3> <ul> <li>Clarify how <code>BytesMut::zeroed</code> works (<a href="https://redirect.github.com/tokio-rs/bytes/issues/714">#714</a>)</li> <li>Clarify the behavior of <code>Buf::chunk</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/717">#717</a>)</li> </ul> <h3>Changed</h3> <ul> <li>Change length condition of <code>BytesMut::truncate</code></li> <li>Reuse capacity when possible in <code>&lt;BytesMut as Buf&gt;::advance</code> impl (<a href="https://redirect.github.com/tokio-rs/bytes/issues/698">#698</a>)</li> <li>Improve <code>must_use</code> suggestion of <code>BytesMut::split</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/699">#699</a>)</li> </ul> <h3>Internal changes</h3> <ul> <li>Use <code>ManuallyDrop</code> instead of <code>mem::forget</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/678">#678</a>)</li> <li>Don't set <code>len</code> in <code>BytesMut::reserve</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/682">#682</a>)</li> <li>Optimize <code>Bytes::copy_to_bytes</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/688">#688</a>)</li> <li>Refactor <code>BytesMut::truncate</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/694">#694</a>)</li> <li>Refactor <code>BytesMut::resize</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/696">#696</a>)</li> <li>Reorder assertion in <code>Bytes::split_to</code>, <code>Bytes::split_off</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/689">#689</a>, <a href="https://redirect.github.com/tokio-rs/bytes/issues/693">#693</a>)</li> <li>Use <code>offset_from</code> in more places (<a href="https://redirect.github.com/tokio-rs/bytes/issues/705">#705</a>)</li> <li>Correct the wrong usage of <code>IntoIter</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/707">#707</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/tokio-rs/bytes/commit/dc4fb3e8f45650500187f8cdbad5ac8ffdb7df0a"><code>dc4fb3e</code></a> chore: prepare bytes v1.7.1 (<a href="https://redirect.github.com/tokio-rs/bytes/issues/727">#727</a>)</li> <li><a href="https://github.com/tokio-rs/bytes/commit/f488be48d07d899dc428c5cd7f5c11a95bf7716c"><code>f488be4</code></a> Revert &quot;Reuse capacity when possible in &lt;BytesMut as Buf&gt;::advance impl&quot; (<a href="https://redirect.github.com/tokio-rs/bytes/issues/726">#726</a>)</li> <li><a href="https://github.com/tokio-rs/bytes/commit/03fdde9dcfe69caf681ecaa1d97f8105a9c9a6c1"><code>03fdde9</code></a> chore: prepare v1.7.0 (<a href="https://redirect.github.com/tokio-rs/bytes/issues/724">#724</a>)</li> <li><a href="https://github.com/tokio-rs/bytes/commit/f8c7b574c0ef0c3cb097d29a08e53b15b4e4a522"><code>f8c7b57</code></a> Merge 'v1.6.1' into 'master' (<a href="https://redirect.github.com/tokio-rs/bytes/issues/721">#721</a>)</li> <li><a href="https://github.com/tokio-rs/bytes/commit/9965a04b5684079bb614addd750340ffc165a9f5"><code>9965a04</code></a> Remove unnecessary file (<a href="https://redirect.github.com/tokio-rs/bytes/issues/719">#719</a>)</li> <li><a href="https://github.com/tokio-rs/bytes/commit/3443ca5a0be21cdb2424bd20d49746bd622ed195"><code>3443ca5</code></a> docs: clarify the behavior of <code>Buf::chunk</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/717">#717</a>)</li> <li><a href="https://github.com/tokio-rs/bytes/commit/8cc940779fd6a489a2d7ca53fbbc44f84210083e"><code>8cc9407</code></a> Allow reclaiming the current allocation (<a href="https://redirect.github.com/tokio-rs/bytes/issues/686">#686</a>)</li> <li><a href="https://github.com/tokio-rs/bytes/commit/7a5154ba8b54970b7bb07c4902bc8a7981f4e57c"><code>7a5154b</code></a> Clarify how <code>BytesMut::zeroed</code> works and advantages to manual impl (<a href="https://redirect.github.com/tokio-rs/bytes/issues/714">#714</a>)</li> <li><a href="https://github.com/tokio-rs/bytes/commit/fa1daac3ae1dcb07dffe3a41a041dffd6edf177b"><code>fa1daac</code></a> Change Bytes::make_mut to impl From&lt;Bytes&gt; for BytesMut (closes <a href="https://redirect.github.com/tokio-rs/bytes/issues/709">#709</a>) (<a href="https://redirect.github.com/tokio-rs/bytes/issues/710">#710</a>)</li> <li><a href="https://github.com/tokio-rs/bytes/commit/caf520ac7f2c466d26bd88eca33ddc53c408e17e"><code>caf520a</code></a> Fix iter tests to use the actual bytes IntoIter instead of std (<a href="https://redirect.github.com/tokio-rs/bytes/issues/707">#707</a>)</li> <li>Additional commits viewable in <a href="https://github.com/tokio-rs/bytes/compare/v1.6.1...v1.7.1">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=bytes&package-manager=cargo&previous-version=1.6.1&new-version=1.7.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: f62b65cc14db0002cdd17da8b5c992c2d1b43ac2
2024-08-05 08:25:39 +03:00
version = "1.7.1"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump bytes from 1.6.1 to 1.7.1 (#927) Bumps [bytes](https://github.com/tokio-rs/bytes) from 1.6.1 to 1.7.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/tokio-rs/bytes/releases">bytes's releases</a>.</em></p> <blockquote> <h2>Bytes 1.7.1</h2> <h1>1.7.1 (August 1, 2024)</h1> <p>This release reverts the following change due to a regression:</p> <ul> <li>Reuse capacity when possible in <code>&lt;BytesMut as Buf&gt;::advance</code> impl (<a href="https://redirect.github.com/tokio-rs/bytes/issues/698">#698</a>)</li> </ul> <p>The revert can be found at <a href="https://redirect.github.com/tokio-rs/bytes/issues/726">#726</a>.</p> <h2>Bytes 1.7.0</h2> <h1>1.7.0 (July 31, 2024)</h1> <h3>Added</h3> <ul> <li>Add conversion from <code>Bytes</code> to <code>BytesMut</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/695">#695</a>, <a href="https://redirect.github.com/tokio-rs/bytes/issues/710">#710</a>)</li> <li>Add reclaim method without additional allocation (<a href="https://redirect.github.com/tokio-rs/bytes/issues/686">#686</a>)</li> </ul> <h3>Documented</h3> <ul> <li>Clarify how <code>BytesMut::zeroed</code> works (<a href="https://redirect.github.com/tokio-rs/bytes/issues/714">#714</a>)</li> <li>Clarify the behavior of <code>Buf::chunk</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/717">#717</a>)</li> </ul> <h3>Changed</h3> <ul> <li>Change length condition of <code>BytesMut::truncate</code></li> <li>Reuse capacity when possible in <code>&lt;BytesMut as Buf&gt;::advance</code> impl (<a href="https://redirect.github.com/tokio-rs/bytes/issues/698">#698</a>)</li> <li>Improve <code>must_use</code> suggestion of <code>BytesMut::split</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/699">#699</a>)</li> </ul> <h3>Internal changes</h3> <ul> <li>Use <code>ManuallyDrop</code> instead of <code>mem::forget</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/678">#678</a>)</li> <li>Don't set <code>len</code> in <code>BytesMut::reserve</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/682">#682</a>)</li> <li>Optimize <code>Bytes::copy_to_bytes</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/688">#688</a>)</li> <li>Refactor <code>BytesMut::truncate</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/694">#694</a>)</li> <li>Refactor <code>BytesMut::resize</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/696">#696</a>)</li> <li>Reorder assertion in <code>Bytes::split_to</code>, <code>Bytes::split_off</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/689">#689</a>, <a href="https://redirect.github.com/tokio-rs/bytes/issues/693">#693</a>)</li> <li>Use <code>offset_from</code> in more places (<a href="https://redirect.github.com/tokio-rs/bytes/issues/705">#705</a>)</li> <li>Correct the wrong usage of <code>IntoIter</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/707">#707</a>)</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/tokio-rs/bytes/blob/master/CHANGELOG.md">bytes's changelog</a>.</em></p> <blockquote> <h1>1.7.1 (August 1, 2024)</h1> <p>This release reverts the following change due to a regression:</p> <ul> <li>Reuse capacity when possible in <code>&lt;BytesMut as Buf&gt;::advance</code> impl (<a href="https://redirect.github.com/tokio-rs/bytes/issues/698">#698</a>)</li> </ul> <p>The revert can be found at <a href="https://redirect.github.com/tokio-rs/bytes/issues/726">#726</a>.</p> <h1>1.7.0 (July 31, 2024)</h1> <h3>Added</h3> <ul> <li>Add conversion from <code>Bytes</code> to <code>BytesMut</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/695">#695</a>, <a href="https://redirect.github.com/tokio-rs/bytes/issues/710">#710</a>)</li> <li>Add reclaim method without additional allocation (<a href="https://redirect.github.com/tokio-rs/bytes/issues/686">#686</a>)</li> </ul> <h3>Documented</h3> <ul> <li>Clarify how <code>BytesMut::zeroed</code> works (<a href="https://redirect.github.com/tokio-rs/bytes/issues/714">#714</a>)</li> <li>Clarify the behavior of <code>Buf::chunk</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/717">#717</a>)</li> </ul> <h3>Changed</h3> <ul> <li>Change length condition of <code>BytesMut::truncate</code></li> <li>Reuse capacity when possible in <code>&lt;BytesMut as Buf&gt;::advance</code> impl (<a href="https://redirect.github.com/tokio-rs/bytes/issues/698">#698</a>)</li> <li>Improve <code>must_use</code> suggestion of <code>BytesMut::split</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/699">#699</a>)</li> </ul> <h3>Internal changes</h3> <ul> <li>Use <code>ManuallyDrop</code> instead of <code>mem::forget</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/678">#678</a>)</li> <li>Don't set <code>len</code> in <code>BytesMut::reserve</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/682">#682</a>)</li> <li>Optimize <code>Bytes::copy_to_bytes</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/688">#688</a>)</li> <li>Refactor <code>BytesMut::truncate</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/694">#694</a>)</li> <li>Refactor <code>BytesMut::resize</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/696">#696</a>)</li> <li>Reorder assertion in <code>Bytes::split_to</code>, <code>Bytes::split_off</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/689">#689</a>, <a href="https://redirect.github.com/tokio-rs/bytes/issues/693">#693</a>)</li> <li>Use <code>offset_from</code> in more places (<a href="https://redirect.github.com/tokio-rs/bytes/issues/705">#705</a>)</li> <li>Correct the wrong usage of <code>IntoIter</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/707">#707</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/tokio-rs/bytes/commit/dc4fb3e8f45650500187f8cdbad5ac8ffdb7df0a"><code>dc4fb3e</code></a> chore: prepare bytes v1.7.1 (<a href="https://redirect.github.com/tokio-rs/bytes/issues/727">#727</a>)</li> <li><a href="https://github.com/tokio-rs/bytes/commit/f488be48d07d899dc428c5cd7f5c11a95bf7716c"><code>f488be4</code></a> Revert &quot;Reuse capacity when possible in &lt;BytesMut as Buf&gt;::advance impl&quot; (<a href="https://redirect.github.com/tokio-rs/bytes/issues/726">#726</a>)</li> <li><a href="https://github.com/tokio-rs/bytes/commit/03fdde9dcfe69caf681ecaa1d97f8105a9c9a6c1"><code>03fdde9</code></a> chore: prepare v1.7.0 (<a href="https://redirect.github.com/tokio-rs/bytes/issues/724">#724</a>)</li> <li><a href="https://github.com/tokio-rs/bytes/commit/f8c7b574c0ef0c3cb097d29a08e53b15b4e4a522"><code>f8c7b57</code></a> Merge 'v1.6.1' into 'master' (<a href="https://redirect.github.com/tokio-rs/bytes/issues/721">#721</a>)</li> <li><a href="https://github.com/tokio-rs/bytes/commit/9965a04b5684079bb614addd750340ffc165a9f5"><code>9965a04</code></a> Remove unnecessary file (<a href="https://redirect.github.com/tokio-rs/bytes/issues/719">#719</a>)</li> <li><a href="https://github.com/tokio-rs/bytes/commit/3443ca5a0be21cdb2424bd20d49746bd622ed195"><code>3443ca5</code></a> docs: clarify the behavior of <code>Buf::chunk</code> (<a href="https://redirect.github.com/tokio-rs/bytes/issues/717">#717</a>)</li> <li><a href="https://github.com/tokio-rs/bytes/commit/8cc940779fd6a489a2d7ca53fbbc44f84210083e"><code>8cc9407</code></a> Allow reclaiming the current allocation (<a href="https://redirect.github.com/tokio-rs/bytes/issues/686">#686</a>)</li> <li><a href="https://github.com/tokio-rs/bytes/commit/7a5154ba8b54970b7bb07c4902bc8a7981f4e57c"><code>7a5154b</code></a> Clarify how <code>BytesMut::zeroed</code> works and advantages to manual impl (<a href="https://redirect.github.com/tokio-rs/bytes/issues/714">#714</a>)</li> <li><a href="https://github.com/tokio-rs/bytes/commit/fa1daac3ae1dcb07dffe3a41a041dffd6edf177b"><code>fa1daac</code></a> Change Bytes::make_mut to impl From&lt;Bytes&gt; for BytesMut (closes <a href="https://redirect.github.com/tokio-rs/bytes/issues/709">#709</a>) (<a href="https://redirect.github.com/tokio-rs/bytes/issues/710">#710</a>)</li> <li><a href="https://github.com/tokio-rs/bytes/commit/caf520ac7f2c466d26bd88eca33ddc53c408e17e"><code>caf520a</code></a> Fix iter tests to use the actual bytes IntoIter instead of std (<a href="https://redirect.github.com/tokio-rs/bytes/issues/707">#707</a>)</li> <li>Additional commits viewable in <a href="https://github.com/tokio-rs/bytes/compare/v1.6.1...v1.7.1">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=bytes&package-manager=cargo&previous-version=1.6.1&new-version=1.7.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: f62b65cc14db0002cdd17da8b5c992c2d1b43ac2
2024-08-05 08:25:39 +03:00
checksum = "8318a53db07bb3f8dca91a600466bdb3f2eaadeedfdbcf02e1accbad9271ba50"
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
dependencies = [
"serde",
]
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
[[package]]
name = "bzip2"
version = "0.4.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bdb116a6ef3f6c3698828873ad02c3014b3c85cadb88496095628e3ef1e347f8"
dependencies = [
"bzip2-sys",
"libc",
]
[[package]]
name = "bzip2-sys"
version = "0.1.11+1.0.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "736a955f3fa7875102d57c82b8cac37ec45224a07fd32d58f9f7a186b6cd4cdc"
dependencies = [
"cc",
"libc",
"pkg-config",
]
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
[[package]]
name = "cast"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "37b2a672a2cb129a2e41c10b1224bb368f9f37a2b16b612598138befd7b37eb5"
[[package]]
name = "cc"
Update to Rust v1.80.1. (#1002) ### What Upgrade to the latest version of Rust. ### How I modified `rust-toolchain.toml` and ran `cargo update`. V3_GIT_ORIGIN_REV_ID: 5fe675ee5dc568cd24de542c826ffd2d355f90ff
2024-08-22 11:08:47 +03:00
version = "1.1.13"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update to Rust v1.80.1. (#1002) ### What Upgrade to the latest version of Rust. ### How I modified `rust-toolchain.toml` and ran `cargo update`. V3_GIT_ORIGIN_REV_ID: 5fe675ee5dc568cd24de542c826ffd2d355f90ff
2024-08-22 11:08:47 +03:00
checksum = "72db2f7947ecee9b03b510377e8bb9077afa27176fdbff55c51027e976fdcc48"
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
dependencies = [
"jobserver",
"libc",
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"shlex",
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
]
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
[[package]]
name = "cfg-if"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "baf1de4339761588bc0619e3cbc0120ee582ebb74b53b4efbf79117bd2da40fd"
[[package]]
name = "chrono"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.4.38"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "a21f936df1771bf62b77f047b726c4625ff2e8aa607c01ec06e5a05bd8463401"
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
dependencies = [
"android-tzdata",
"iana-time-zone",
Use v3.0.0 as the version number. (#999) ### What Updates the version number to `3.0.0`, now we're officially at GA. ### How I updated the version number, and also updated some dependencies. The `Cargo.lock` file was not up to date. V3_GIT_ORIGIN_REV_ID: 3e9b784c8ad856556193e56aee9fa607fa8ce19e
2024-08-21 17:02:43 +03:00
"js-sys",
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
"num-traits",
"serde",
Use v3.0.0 as the version number. (#999) ### What Updates the version number to `3.0.0`, now we're officially at GA. ### How I updated the version number, and also updated some dependencies. The `Cargo.lock` file was not up to date. V3_GIT_ORIGIN_REV_ID: 3e9b784c8ad856556193e56aee9fa607fa8ce19e
2024-08-21 17:02:43 +03:00
"wasm-bindgen",
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"windows-targets 0.52.6",
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
]
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
[[package]]
name = "chrono-tz"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "93698b29de5e97ad0ae26447b344c482a7284c737d9ddc5f9e52b74a336671bb"
dependencies = [
"chrono",
"chrono-tz-build",
"phf",
]
[[package]]
name = "chrono-tz-build"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0c088aee841df9c3041febbb73934cfc39708749bf96dc827e3359cd39ef11b1"
dependencies = [
"parse-zoneinfo",
"phf",
"phf_codegen",
]
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
[[package]]
name = "ciborium"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.2.2"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "42e69ffd6f0917f5c029256a24d0161db17cea3997d185db0d35926308770f0e"
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
dependencies = [
"ciborium-io",
"ciborium-ll",
"serde",
]
[[package]]
name = "ciborium-io"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.2.2"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "05afea1e0a06c9be33d539b876f1ce3692f4afea2cb41f740e7743225ed1c757"
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
[[package]]
name = "ciborium-ll"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.2.2"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "57663b653d948a338bfb3eeba9bb2fd5fcfaecb9e199e87e1eda4d9e8b240fd9"
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
dependencies = [
"ciborium-io",
"half",
]
[[package]]
name = "clap"
Use v3.0.0 as the version number. (#999) ### What Updates the version number to `3.0.0`, now we're officially at GA. ### How I updated the version number, and also updated some dependencies. The `Cargo.lock` file was not up to date. V3_GIT_ORIGIN_REV_ID: 3e9b784c8ad856556193e56aee9fa607fa8ce19e
2024-08-21 17:02:43 +03:00
version = "4.5.16"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Use v3.0.0 as the version number. (#999) ### What Updates the version number to `3.0.0`, now we're officially at GA. ### How I updated the version number, and also updated some dependencies. The `Cargo.lock` file was not up to date. V3_GIT_ORIGIN_REV_ID: 3e9b784c8ad856556193e56aee9fa607fa8ce19e
2024-08-21 17:02:43 +03:00
checksum = "ed6719fffa43d0d87e5fd8caeab59be1554fb028cd30edc88fc4369b17971019"
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
dependencies = [
"clap_builder",
"clap_derive",
]
[[package]]
name = "clap_builder"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "4.5.15"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "216aec2b177652e3846684cbfe25c9964d18ec45234f0f5da5157b207ed1aab6"
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
dependencies = [
"anstream",
"anstyle",
Bump Criterion lib (#504) <!-- Thank you for submitting this PR! :) --> ## Description Benchmarks are running pretty slowly in Github, let's check it's not an old library version problem. --------- Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: db1a70c5465cf475fa66d2afc981fd496eccacaa
2024-04-24 18:52:47 +03:00
"clap_lex",
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
"strsim",
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
]
[[package]]
name = "clap_derive"
Bump clap from 4.5.11 to 4.5.13 (#928) Bumps [clap](https://github.com/clap-rs/clap) from 4.5.11 to 4.5.13. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/clap-rs/clap/releases">clap's releases</a>.</em></p> <blockquote> <h2>v4.5.13</h2> <h2>[4.5.13] - 2024-07-31</h2> <h3>Fixes</h3> <ul> <li><em>(derive)</em> Improve error message when <code>#[flatten]</code>ing an optional <code>#[group(skip)]</code></li> <li><em>(help)</em> Properly wrap long subcommand descriptions in help</li> </ul> <h2>v4.5.12</h2> <h2>[4.5.12] - 2024-07-31</h2> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/clap-rs/clap/blob/master/CHANGELOG.md">clap's changelog</a>.</em></p> <blockquote> <h2>[4.5.13] - 2024-07-31</h2> <h3>Fixes</h3> <ul> <li><em>(derive)</em> Improve error message when <code>#[flatten]</code>ing an optional <code>#[group(skip)]</code></li> <li><em>(help)</em> Properly wrap long subcommand descriptions in help</li> </ul> <h2>[4.5.12] - 2024-07-31</h2> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/clap-rs/clap/commit/66b5a122ecd53234e02c15d57ccc2744b9f7a5ca"><code>66b5a12</code></a> chore: Release</li> <li><a href="https://github.com/clap-rs/clap/commit/a83b724fc12cbd733f580cec39b03df6a3e2a17f"><code>a83b724</code></a> docs: Update changelog</li> <li><a href="https://github.com/clap-rs/clap/commit/e19469f0e2dc0df0877bfbe00b11f64d97bdfefd"><code>e19469f</code></a> Merge pull request <a href="https://redirect.github.com/clap-rs/clap/issues/5615">#5615</a> from epage/wrap</li> <li><a href="https://github.com/clap-rs/clap/commit/360bb3bc11bf7a0a18ba269642704492383eb028"><code>360bb3b</code></a> fix(help): Properly wrap subcommand about</li> <li><a href="https://github.com/clap-rs/clap/commit/58b5bd89ea1dc324769f4b6185ca840d775bb66e"><code>58b5bd8</code></a> test(help): Show bad subcommand wrapping</li> <li><a href="https://github.com/clap-rs/clap/commit/e1f63207307200bb4a51094a1311f34aabe795e8"><code>e1f6320</code></a> Merge pull request <a href="https://redirect.github.com/clap-rs/clap/issues/5614">#5614</a> from epage/snap</li> <li><a href="https://github.com/clap-rs/clap/commit/7b5b61b0218d2c19ed424155e7ae55d21b0e2240"><code>7b5b61b</code></a> test(help): Switch to snapbox</li> <li><a href="https://github.com/clap-rs/clap/commit/1490e2434aaf4071dc0dc36fe0046238401a3679"><code>1490e24</code></a> chore: Update snapbox</li> <li><a href="https://github.com/clap-rs/clap/commit/6671d9350027a9fb5cfca44304603d0d32f5e30a"><code>6671d93</code></a> Merge pull request <a href="https://redirect.github.com/clap-rs/clap/issues/5613">#5613</a> from epage/flatten</li> <li><a href="https://github.com/clap-rs/clap/commit/13dfdb38709ded67d2bedafdea56306f04749bd9"><code>13dfdb3</code></a> fix(derive): Improve flattening-skipped-group assert</li> <li>Additional commits viewable in <a href="https://github.com/clap-rs/clap/compare/clap_complete-v4.5.11...v4.5.13">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=clap&package-manager=cargo&previous-version=4.5.11&new-version=4.5.13)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: 898ddf94dc4357f35e50b1599dedef672c18cd8a
2024-08-05 08:26:11 +03:00
version = "4.5.13"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump clap from 4.5.11 to 4.5.13 (#928) Bumps [clap](https://github.com/clap-rs/clap) from 4.5.11 to 4.5.13. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/clap-rs/clap/releases">clap's releases</a>.</em></p> <blockquote> <h2>v4.5.13</h2> <h2>[4.5.13] - 2024-07-31</h2> <h3>Fixes</h3> <ul> <li><em>(derive)</em> Improve error message when <code>#[flatten]</code>ing an optional <code>#[group(skip)]</code></li> <li><em>(help)</em> Properly wrap long subcommand descriptions in help</li> </ul> <h2>v4.5.12</h2> <h2>[4.5.12] - 2024-07-31</h2> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/clap-rs/clap/blob/master/CHANGELOG.md">clap's changelog</a>.</em></p> <blockquote> <h2>[4.5.13] - 2024-07-31</h2> <h3>Fixes</h3> <ul> <li><em>(derive)</em> Improve error message when <code>#[flatten]</code>ing an optional <code>#[group(skip)]</code></li> <li><em>(help)</em> Properly wrap long subcommand descriptions in help</li> </ul> <h2>[4.5.12] - 2024-07-31</h2> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/clap-rs/clap/commit/66b5a122ecd53234e02c15d57ccc2744b9f7a5ca"><code>66b5a12</code></a> chore: Release</li> <li><a href="https://github.com/clap-rs/clap/commit/a83b724fc12cbd733f580cec39b03df6a3e2a17f"><code>a83b724</code></a> docs: Update changelog</li> <li><a href="https://github.com/clap-rs/clap/commit/e19469f0e2dc0df0877bfbe00b11f64d97bdfefd"><code>e19469f</code></a> Merge pull request <a href="https://redirect.github.com/clap-rs/clap/issues/5615">#5615</a> from epage/wrap</li> <li><a href="https://github.com/clap-rs/clap/commit/360bb3bc11bf7a0a18ba269642704492383eb028"><code>360bb3b</code></a> fix(help): Properly wrap subcommand about</li> <li><a href="https://github.com/clap-rs/clap/commit/58b5bd89ea1dc324769f4b6185ca840d775bb66e"><code>58b5bd8</code></a> test(help): Show bad subcommand wrapping</li> <li><a href="https://github.com/clap-rs/clap/commit/e1f63207307200bb4a51094a1311f34aabe795e8"><code>e1f6320</code></a> Merge pull request <a href="https://redirect.github.com/clap-rs/clap/issues/5614">#5614</a> from epage/snap</li> <li><a href="https://github.com/clap-rs/clap/commit/7b5b61b0218d2c19ed424155e7ae55d21b0e2240"><code>7b5b61b</code></a> test(help): Switch to snapbox</li> <li><a href="https://github.com/clap-rs/clap/commit/1490e2434aaf4071dc0dc36fe0046238401a3679"><code>1490e24</code></a> chore: Update snapbox</li> <li><a href="https://github.com/clap-rs/clap/commit/6671d9350027a9fb5cfca44304603d0d32f5e30a"><code>6671d93</code></a> Merge pull request <a href="https://redirect.github.com/clap-rs/clap/issues/5613">#5613</a> from epage/flatten</li> <li><a href="https://github.com/clap-rs/clap/commit/13dfdb38709ded67d2bedafdea56306f04749bd9"><code>13dfdb3</code></a> fix(derive): Improve flattening-skipped-group assert</li> <li>Additional commits viewable in <a href="https://github.com/clap-rs/clap/compare/clap_complete-v4.5.11...v4.5.13">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=clap&package-manager=cargo&previous-version=4.5.11&new-version=4.5.13)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: 898ddf94dc4357f35e50b1599dedef672c18cd8a
2024-08-05 08:26:11 +03:00
checksum = "501d359d5f3dcaf6ecdeee48833ae73ec6e42723a1e52419c79abf9507eec0a0"
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
dependencies = [
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
"heck 0.5.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
"proc-macro2",
"quote",
Bump syn from 2.0.75 to 2.0.76 (#1017) Bumps [syn](https://github.com/dtolnay/syn) from 2.0.75 to 2.0.76. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/syn/releases">syn's releases</a>.</em></p> <blockquote> <h2>2.0.76</h2> <ul> <li>Enforce that tail call <code>become</code> keyword is followed by an expression (<a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/syn/commit/ef3e9c6dde79be7590fc90278772663ca31c1a73"><code>ef3e9c6</code></a> Release 2.0.76</li> <li><a href="https://github.com/dtolnay/syn/commit/8f7365ff9685c8ca9527c2de409204179a3efcdf"><code>8f7365f</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a> from dtolnay/tailcall</li> <li><a href="https://github.com/dtolnay/syn/commit/6cddd9ea714fe034466b4f02d3f7abb484c65ea0"><code>6cddd9e</code></a> Make tail call expr mandatory</li> <li>See full diff in <a href="https://github.com/dtolnay/syn/compare/2.0.75...2.0.76">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=syn&package-manager=cargo&previous-version=2.0.75&new-version=2.0.76)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d261ad30ffeb10034a80f9044504cb9d6c7c1ff7
2024-08-26 14:39:45 +03:00
"syn 2.0.76",
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
]
[[package]]
name = "clap_lex"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.7.2"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "1462739cb27611015575c0c11df5df7601141071f07518d56fcc1be504cbec97"
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
[[package]]
name = "cobs"
version = "0.2.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "67ba02a97a2bd10f4b59b25c7973101c79642302776489e030cd13cdab09ed15"
[[package]]
name = "colorchoice"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "1.0.2"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "d3fd119d74b830634cea2a0f58bbd0d54540518a14397557951e79340abc28c0"
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
[[package]]
name = "combine"
version = "3.8.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "da3da6baa321ec19e1cc41d31bf599f00c783d0517095cdaf0332e3fe8d20680"
dependencies = [
"ascii",
"byteorder",
"either",
"memchr",
"unreachable",
]
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
[[package]]
name = "comfy-table"
version = "7.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b34115915337defe99b2aff5c2ce6771e5fbc4079f4b506301f5cf394c8452f7"
dependencies = [
"strum",
"strum_macros",
"unicode-width",
]
Use v3.0.0 as the version number. (#999) ### What Updates the version number to `3.0.0`, now we're officially at GA. ### How I updated the version number, and also updated some dependencies. The `Cargo.lock` file was not up to date. V3_GIT_ORIGIN_REV_ID: 3e9b784c8ad856556193e56aee9fa607fa8ce19e
2024-08-21 17:02:43 +03:00
[[package]]
name = "compatibility"
version = "3.0.0"
dependencies = [
"chrono",
"open-dds",
"opendds-derive",
"schemars",
"serde",
"serde_json",
"serde_path_to_error",
"thiserror",
]
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
[[package]]
name = "console"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.15.8"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "0e1f83fc076bd6dd27517eacdf25fef6c4dfe5f1d7448bafaaf3a26f13b5e4eb"
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
dependencies = [
"encode_unicode",
"lazy_static",
"libc",
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
"windows-sys 0.52.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
]
[[package]]
name = "const-oid"
version = "0.6.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9d6f2aa4d0537bcc1c74df8755072bd31c1ef1a3a1b85a68e8404a8c353b7b8b"
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
[[package]]
name = "const-random"
version = "0.1.18"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "87e00182fe74b066627d63b85fd550ac2998d4b0bd86bfed477a0ae4c7c71359"
dependencies = [
"const-random-macro",
]
[[package]]
name = "const-random-macro"
version = "0.1.16"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f9d839f2a20b0aee515dc581a6172f2321f96cab76c1a38a4c584a194955390e"
dependencies = [
"getrandom",
"once_cell",
"tiny-keccak",
]
[[package]]
name = "constant_time_eq"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f7144d30dcf0fafbce74250a3963025d8d52177934239851c917d29f1df280c2"
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
[[package]]
name = "convert_case"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6245d59a3e82a7fc217c5828a6692dbc6dfb63a0c8c90495621f7b9d79704a0e"
Custom deserializer for OpenDd objects (#313) V3_GIT_ORIGIN_REV_ID: 4c7a9380e517ac8e7ac1bd44dbe879918bd0d9a2
2024-03-11 15:16:53 +03:00
[[package]]
name = "convert_case"
version = "0.6.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ec182b0ca2f35d8fc196cf3404988fd8b8c739a4d270ff118a398feb0cbec1ca"
dependencies = [
"unicode-segmentation",
]
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
[[package]]
name = "cookie"
Bump cookie from 0.17.0 to 0.18.1 (#515) V3_GIT_ORIGIN_REV_ID: 40af3675b9c3a230d7e70148797ce28e5b1e85cc
2024-04-29 11:14:07 +03:00
version = "0.18.1"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump cookie from 0.17.0 to 0.18.1 (#515) V3_GIT_ORIGIN_REV_ID: 40af3675b9c3a230d7e70148797ce28e5b1e85cc
2024-04-29 11:14:07 +03:00
checksum = "4ddef33a339a91ea89fb53151bd0a4689cfce27055c291dfa69945475d22c747"
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
dependencies = [
"time",
"version_check",
]
[[package]]
name = "core-foundation"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.9.4"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "91e195e091a93c46f7102ec7818a2aa394e1e1771c3ab4825963fa03e45afb8f"
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
dependencies = [
"core-foundation-sys",
"libc",
]
[[package]]
name = "core-foundation-sys"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.8.7"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "773648b94d0e5d620f64f280777445740e61fe701025087ec8b57f45c791888b"
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
[[package]]
name = "countme"
version = "3.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7704b5fdd17b18ae31c4c1da5a2e0305a2bf17b5249300a9ee9ed7b72114c636"
[[package]]
name = "cpufeatures"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.2.13"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "51e852e6dc9a5bed1fae92dd2375037bf2b768725bf3be87811edee3249d09ad"
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
dependencies = [
"libc",
]
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
[[package]]
name = "crc32fast"
version = "1.4.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a97769d94ddab943e4510d138150169a2758b5ef3eb191a9ee688de3e23ef7b3"
dependencies = [
"cfg-if",
]
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
[[package]]
name = "criterion"
Bump Criterion lib (#504) <!-- Thank you for submitting this PR! :) --> ## Description Benchmarks are running pretty slowly in Github, let's check it's not an old library version problem. --------- Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: db1a70c5465cf475fa66d2afc981fd496eccacaa
2024-04-24 18:52:47 +03:00
version = "0.5.1"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Criterion lib (#504) <!-- Thank you for submitting this PR! :) --> ## Description Benchmarks are running pretty slowly in Github, let's check it's not an old library version problem. --------- Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: db1a70c5465cf475fa66d2afc981fd496eccacaa
2024-04-24 18:52:47 +03:00
checksum = "f2b12d017a929603d80db1831cd3a24082f8137ce19c69e6447f54f5fc8d692f"
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
dependencies = [
"anes",
"cast",
"ciborium",
Bump Criterion lib (#504) <!-- Thank you for submitting this PR! :) --> ## Description Benchmarks are running pretty slowly in Github, let's check it's not an old library version problem. --------- Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: db1a70c5465cf475fa66d2afc981fd496eccacaa
2024-04-24 18:52:47 +03:00
"clap",
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
"criterion-plot",
"futures",
Bump Criterion lib (#504) <!-- Thank you for submitting this PR! :) --> ## Description Benchmarks are running pretty slowly in Github, let's check it's not an old library version problem. --------- Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: db1a70c5465cf475fa66d2afc981fd496eccacaa
2024-04-24 18:52:47 +03:00
"is-terminal",
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
"itertools 0.10.5",
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
"num-traits",
Bump Criterion lib (#504) <!-- Thank you for submitting this PR! :) --> ## Description Benchmarks are running pretty slowly in Github, let's check it's not an old library version problem. --------- Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: db1a70c5465cf475fa66d2afc981fd496eccacaa
2024-04-24 18:52:47 +03:00
"once_cell",
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
"oorandom",
"plotters",
"rayon",
"regex",
"serde",
"serde_derive",
"serde_json",
"tinytemplate",
"tokio",
"walkdir",
]
[[package]]
name = "criterion-plot"
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6b50826342786a51a89e2da3a28f1c32b06e387201bc2d19791f622c673706b1"
dependencies = [
"cast",
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
"itertools 0.10.5",
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
]
[[package]]
name = "critical-section"
Update to Rust v1.80.1. (#1002) ### What Upgrade to the latest version of Rust. ### How I modified `rust-toolchain.toml` and ran `cargo update`. V3_GIT_ORIGIN_REV_ID: 5fe675ee5dc568cd24de542c826ffd2d355f90ff
2024-08-22 11:08:47 +03:00
version = "1.1.3"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update to Rust v1.80.1. (#1002) ### What Upgrade to the latest version of Rust. ### How I modified `rust-toolchain.toml` and ran `cargo update`. V3_GIT_ORIGIN_REV_ID: 5fe675ee5dc568cd24de542c826ffd2d355f90ff
2024-08-22 11:08:47 +03:00
checksum = "f64009896348fc5af4222e9cf7d7d82a95a256c634ebcf61c53e4ea461422242"
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
[[package]]
name = "crossbeam-channel"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.5.13"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "33480d6946193aa8033910124896ca395333cae7e2d1113d1fef6c3272217df2"
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
dependencies = [
"crossbeam-utils",
]
[[package]]
name = "crossbeam-deque"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.8.5"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "613f8cc01fe9cf1a3eb3d7f488fd2fa8388403e97039e2f73692932e291a770d"
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
dependencies = [
"crossbeam-epoch",
"crossbeam-utils",
]
[[package]]
name = "crossbeam-epoch"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.9.18"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "5b82ac4a3c2ca9c3460964f020e1402edd5753411d7737aa39c3714ad1b5420e"
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
dependencies = [
"crossbeam-utils",
]
[[package]]
name = "crossbeam-utils"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.8.20"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "22ec99545bb0ed0ea7bb9b8e1e9122ea386ff8a48c0922e43f36d45ab09e0e80"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
[[package]]
name = "crunchy"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7a81dae078cea95a014a339291cec439d2f232ebe854a9d672b796c6afafa9b7"
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
[[package]]
name = "crypto-bigint"
Update to Rust v1.80.1. (#1002) ### What Upgrade to the latest version of Rust. ### How I modified `rust-toolchain.toml` and ran `cargo update`. V3_GIT_ORIGIN_REV_ID: 5fe675ee5dc568cd24de542c826ffd2d355f90ff
2024-08-22 11:08:47 +03:00
version = "0.2.11"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update to Rust v1.80.1. (#1002) ### What Upgrade to the latest version of Rust. ### How I modified `rust-toolchain.toml` and ran `cargo update`. V3_GIT_ORIGIN_REV_ID: 5fe675ee5dc568cd24de542c826ffd2d355f90ff
2024-08-22 11:08:47 +03:00
checksum = "f83bd3bb4314701c568e340cd8cf78c975aa0ca79e03d3f6d1677d5b0c9c0c03"
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
dependencies = [
"generic-array",
"rand_core",
"subtle",
"zeroize",
]
add field arguments in schema and execution (#695) ### TODO - [x] Validate the presence of arguments in the data connector schema - [x] Add test for IR - [x] Add test using custom connector ## Description JIRA: https://hasurahq.atlassian.net/browse/V3ENGINE-148 This is part 2 of the field arguments. This will add the field arguments to the graphql schema and also handles the execution part. ![image](https://github.com/hasura/v3-engine/assets/85472423/c8f55d70-6539-42ef-ab5a-91b74e5699e2) ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> Add support for field arguments <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> --------- Co-authored-by: Anon Ray <ecthiender@users.noreply.github.com> Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: ea06b896feaca30419f81cd070fd4cfd608ef35b
2024-06-19 11:14:24 +03:00
[[package]]
name = "crypto-common"
version = "0.1.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1bfb12502f3fc46cca1bb51ac28df9d618d813cdc3d2f25b9fe775a34af26bb3"
dependencies = [
"generic-array",
"typenum",
]
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
[[package]]
name = "crypto-mac"
Update to Rust v1.80.1. (#1002) ### What Upgrade to the latest version of Rust. ### How I modified `rust-toolchain.toml` and ran `cargo update`. V3_GIT_ORIGIN_REV_ID: 5fe675ee5dc568cd24de542c826ffd2d355f90ff
2024-08-22 11:08:47 +03:00
version = "0.11.1"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update to Rust v1.80.1. (#1002) ### What Upgrade to the latest version of Rust. ### How I modified `rust-toolchain.toml` and ran `cargo update`. V3_GIT_ORIGIN_REV_ID: 5fe675ee5dc568cd24de542c826ffd2d355f90ff
2024-08-22 11:08:47 +03:00
checksum = "b1d1a86f49236c215f271d40892d5fc950490551400b02ef360692c29815c714"
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
dependencies = [
"generic-array",
"subtle",
]
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
[[package]]
name = "csv"
version = "1.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ac574ff4d437a7b5ad237ef331c17ccca63c46479e5b5453eb8e10bb99a759fe"
dependencies = [
"csv-core",
"itoa",
"ryu",
"serde",
]
[[package]]
name = "csv-core"
version = "0.1.11"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5efa2b3d7902f4b634a20cae3c9c4e6209dc4779feb6863329607560143efa70"
dependencies = [
"memchr",
]
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
[[package]]
name = "custom-connector"
Use v3.0.0 as the version number. (#999) ### What Updates the version number to `3.0.0`, now we're officially at GA. ### How I updated the version number, and also updated some dependencies. The `Cargo.lock` file was not up to date. V3_GIT_ORIGIN_REV_ID: 3e9b784c8ad856556193e56aee9fa607fa8ce19e
2024-08-21 17:02:43 +03:00
version = "3.0.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
dependencies = [
Bundle custom connector data with the binary. (#480) This changes the way we build the custom connector so that the data is baked in at compile time, not loaded from the file system at runtime. This simplifies packaging. I also took the liberty to switch out `.unwrap()` for `anyhow`, and to avoid parsing a string to construct the socket address. V3_GIT_ORIGIN_REV_ID: d562e0a9852b4e3ecde45bd6938d8eb1b066211b
2024-04-19 18:05:23 +03:00
"anyhow",
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
"axum",
Add graceful shutdown to all cloud servers (#1023) <!-- The PR description should answer 2 important questions: --> ### What Put graceful shutdown code in a new crate. ### How <!-- How is it trying to accomplish it (what are the implementation steps)? --> V3_GIT_ORIGIN_REV_ID: 262cd85064f0420d2170a3bf710ab72853b5764d
2024-08-28 13:23:08 +03:00
"axum-ext",
Add support for HTTP/2 to the custom connector. (#581) Enable HTTP/2 support for Axum, so that we can make use of request multiplexing from the engine in the future. I also added an `env_logger` to the custom connector so we can see what's going on there. V3_GIT_ORIGIN_REV_ID: 3082b988ae3d149ee548f94638308876734b26df
2024-05-14 18:10:42 +03:00
"env_logger",
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"indexmap 2.4.0",
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 0.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
"regex",
Argument presets for DataConnectorLink Pt. 2 (#675) ## Description This PR implements argument presets for `DataConnectorLink`, which can be used to forward request headers as function/procedure arguments to NDC. This PR implements the execution part. **Note**: response header forwarding is not implemented yet. V3_GIT_ORIGIN_REV_ID: ff69129aee3e3052367ca42acdec3922cbc2cb0c
2024-06-06 19:03:41 +03:00
"serde",
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
"serde_json",
add field arguments in schema and execution (#695) ### TODO - [x] Validate the presence of arguments in the data connector schema - [x] Add test for IR - [x] Add test using custom connector ## Description JIRA: https://hasurahq.atlassian.net/browse/V3ENGINE-148 This is part 2 of the field arguments. This will add the field arguments to the graphql schema and also handles the execution part. ![image](https://github.com/hasura/v3-engine/assets/85472423/c8f55d70-6539-42ef-ab5a-91b74e5699e2) ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> Add support for field arguments <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> --------- Co-authored-by: Anon Ray <ecthiender@users.noreply.github.com> Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: ea06b896feaca30419f81cd070fd4cfd608ef35b
2024-06-19 11:14:24 +03:00
"sha2 0.10.8",
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
"tokio",
forward headers from commands as response headers (#707) ## Description According to NDC headers pass-through spec, commands can include headers in their responses, which are forwarded as response headers by the engine to the client. This PR implements it. V3_GIT_ORIGIN_REV_ID: 4fe458db02c5dd51f4674e4e013312f8e179c087
2024-06-25 10:26:22 +03:00
"uuid",
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
]
[[package]]
name = "darling"
Bump darling from 0.20.9 to 0.20.10 (#862) Bumps [darling](https://github.com/TedDriggs/darling) from 0.20.9 to 0.20.10. V3_GIT_ORIGIN_REV_ID: c5ced551c5a019f7416ac70d367197a41bafa7b7
2024-07-22 10:40:10 +03:00
version = "0.20.10"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump darling from 0.20.9 to 0.20.10 (#862) Bumps [darling](https://github.com/TedDriggs/darling) from 0.20.9 to 0.20.10. V3_GIT_ORIGIN_REV_ID: c5ced551c5a019f7416ac70d367197a41bafa7b7
2024-07-22 10:40:10 +03:00
checksum = "6f63b86c8a8826a49b8c21f08a2d07338eec8d900540f8630dc76284be802989"
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
dependencies = [
Use `syn` v2 in our own macros. (#574) This upgrades `darling` and `schemars` too, so they also use `syn` v2. V3_GIT_ORIGIN_REV_ID: 731160389115dfa079fb1e13e831204d278f5a40
2024-05-14 10:49:52 +03:00
"darling_core",
"darling_macro",
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
]
[[package]]
name = "darling_core"
Bump darling from 0.20.9 to 0.20.10 (#862) Bumps [darling](https://github.com/TedDriggs/darling) from 0.20.9 to 0.20.10. V3_GIT_ORIGIN_REV_ID: c5ced551c5a019f7416ac70d367197a41bafa7b7
2024-07-22 10:40:10 +03:00
version = "0.20.10"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump darling from 0.20.9 to 0.20.10 (#862) Bumps [darling](https://github.com/TedDriggs/darling) from 0.20.9 to 0.20.10. V3_GIT_ORIGIN_REV_ID: c5ced551c5a019f7416ac70d367197a41bafa7b7
2024-07-22 10:40:10 +03:00
checksum = "95133861a8032aaea082871032f5815eb9e98cef03fa916ab4500513994df9e5"
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
dependencies = [
"fnv",
"ident_case",
"proc-macro2",
"quote",
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
"strsim",
Bump syn from 2.0.75 to 2.0.76 (#1017) Bumps [syn](https://github.com/dtolnay/syn) from 2.0.75 to 2.0.76. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/syn/releases">syn's releases</a>.</em></p> <blockquote> <h2>2.0.76</h2> <ul> <li>Enforce that tail call <code>become</code> keyword is followed by an expression (<a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/syn/commit/ef3e9c6dde79be7590fc90278772663ca31c1a73"><code>ef3e9c6</code></a> Release 2.0.76</li> <li><a href="https://github.com/dtolnay/syn/commit/8f7365ff9685c8ca9527c2de409204179a3efcdf"><code>8f7365f</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a> from dtolnay/tailcall</li> <li><a href="https://github.com/dtolnay/syn/commit/6cddd9ea714fe034466b4f02d3f7abb484c65ea0"><code>6cddd9e</code></a> Make tail call expr mandatory</li> <li>See full diff in <a href="https://github.com/dtolnay/syn/compare/2.0.75...2.0.76">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=syn&package-manager=cargo&previous-version=2.0.75&new-version=2.0.76)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d261ad30ffeb10034a80f9044504cb9d6c7c1ff7
2024-08-26 14:39:45 +03:00
"syn 2.0.76",
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
]
[[package]]
name = "darling_macro"
Bump darling from 0.20.9 to 0.20.10 (#862) Bumps [darling](https://github.com/TedDriggs/darling) from 0.20.9 to 0.20.10. V3_GIT_ORIGIN_REV_ID: c5ced551c5a019f7416ac70d367197a41bafa7b7
2024-07-22 10:40:10 +03:00
version = "0.20.10"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump darling from 0.20.9 to 0.20.10 (#862) Bumps [darling](https://github.com/TedDriggs/darling) from 0.20.9 to 0.20.10. V3_GIT_ORIGIN_REV_ID: c5ced551c5a019f7416ac70d367197a41bafa7b7
2024-07-22 10:40:10 +03:00
checksum = "d336a2a514f6ccccaa3e09b02d41d35330c07ddf03a62165fcec10bb561c7806"
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
dependencies = [
Use `syn` v2 in our own macros. (#574) This upgrades `darling` and `schemars` too, so they also use `syn` v2. V3_GIT_ORIGIN_REV_ID: 731160389115dfa079fb1e13e831204d278f5a40
2024-05-14 10:49:52 +03:00
"darling_core",
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
"quote",
Bump syn from 2.0.75 to 2.0.76 (#1017) Bumps [syn](https://github.com/dtolnay/syn) from 2.0.75 to 2.0.76. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/syn/releases">syn's releases</a>.</em></p> <blockquote> <h2>2.0.76</h2> <ul> <li>Enforce that tail call <code>become</code> keyword is followed by an expression (<a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/syn/commit/ef3e9c6dde79be7590fc90278772663ca31c1a73"><code>ef3e9c6</code></a> Release 2.0.76</li> <li><a href="https://github.com/dtolnay/syn/commit/8f7365ff9685c8ca9527c2de409204179a3efcdf"><code>8f7365f</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a> from dtolnay/tailcall</li> <li><a href="https://github.com/dtolnay/syn/commit/6cddd9ea714fe034466b4f02d3f7abb484c65ea0"><code>6cddd9e</code></a> Make tail call expr mandatory</li> <li>See full diff in <a href="https://github.com/dtolnay/syn/compare/2.0.75...2.0.76">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=syn&package-manager=cargo&previous-version=2.0.75&new-version=2.0.76)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d261ad30ffeb10034a80f9044504cb9d6c7c1ff7
2024-08-26 14:39:45 +03:00
"syn 2.0.76",
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
]
[[package]]
name = "dashmap"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
version = "6.0.1"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
checksum = "804c8821570c3f8b70230c2ba75ffa5c0f9a4189b9a432b6656c536712acae28"
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
dependencies = [
"cfg-if",
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
"crossbeam-utils",
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
"hashbrown 0.14.5",
"lock_api",
"once_cell",
"parking_lot_core",
]
[[package]]
name = "datafusion"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
version = "41.0.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
checksum = "e4fd4a99fc70d40ef7e52b243b4a399c3f8d353a40d5ecb200deee05e49c61bb"
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
dependencies = [
"ahash",
"arrow",
"arrow-array",
"arrow-ipc",
"arrow-schema",
"async-compression",
"async-trait",
"bytes",
"bzip2",
"chrono",
"dashmap",
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
"datafusion-catalog",
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
"datafusion-common",
"datafusion-common-runtime",
"datafusion-execution",
"datafusion-expr",
"datafusion-functions",
"datafusion-functions-aggregate",
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
"datafusion-functions-nested",
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
"datafusion-optimizer",
"datafusion-physical-expr",
"datafusion-physical-expr-common",
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
"datafusion-physical-optimizer",
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
"datafusion-physical-plan",
"datafusion-sql",
"flate2",
"futures",
"glob",
"half",
"hashbrown 0.14.5",
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"indexmap 2.4.0",
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
"itertools 0.12.1",
"log",
"num_cpus",
"object_store",
"parking_lot",
"parquet",
"paste",
"pin-project-lite",
"rand",
"sqlparser",
"tempfile",
"tokio",
"tokio-util",
"url",
"uuid",
"xz2",
"zstd",
]
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
[[package]]
name = "datafusion-catalog"
version = "41.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e13b3cfbd84c6003594ae1972314e3df303a27ce8ce755fcea3240c90f4c0529"
dependencies = [
"arrow-schema",
"async-trait",
"datafusion-common",
"datafusion-execution",
"datafusion-expr",
"datafusion-physical-plan",
]
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
[[package]]
name = "datafusion-common"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
version = "41.0.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
checksum = "44fdbc877e3e40dcf88cc8f283d9f5c8851f0a3aa07fee657b1b75ac1ad49b9c"
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
dependencies = [
"ahash",
"arrow",
"arrow-array",
"arrow-buffer",
"arrow-schema",
"chrono",
"half",
"hashbrown 0.14.5",
"instant",
"libc",
"num_cpus",
"object_store",
"parquet",
"sqlparser",
]
[[package]]
name = "datafusion-common-runtime"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
version = "41.0.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
checksum = "8a7496d1f664179f6ce3a5cbef6566056ccaf3ea4aa72cc455f80e62c1dd86b1"
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
dependencies = [
"tokio",
]
[[package]]
name = "datafusion-execution"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
version = "41.0.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
checksum = "799e70968c815b611116951e3dd876aef04bf217da31b72eec01ee6a959336a1"
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
dependencies = [
"arrow",
"chrono",
"dashmap",
"datafusion-common",
"datafusion-expr",
"futures",
"hashbrown 0.14.5",
"log",
"object_store",
"parking_lot",
"rand",
"tempfile",
"url",
]
[[package]]
name = "datafusion-expr"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
version = "41.0.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
checksum = "1c1841c409d9518c17971d15c9bae62e629eb937e6fb6c68cd32e9186f8b30d2"
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
dependencies = [
"ahash",
"arrow",
"arrow-array",
"arrow-buffer",
"chrono",
"datafusion-common",
"paste",
"serde_json",
"sqlparser",
"strum",
"strum_macros",
]
[[package]]
name = "datafusion-functions"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
version = "41.0.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
checksum = "a8e481cf34d2a444bd8fa09b65945f0ce83dc92df8665b761505b3d9f351bebb"
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
dependencies = [
"arrow",
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
"arrow-buffer",
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
"base64 0.22.1",
"blake2",
"blake3",
"chrono",
"datafusion-common",
"datafusion-execution",
"datafusion-expr",
"hashbrown 0.14.5",
"hex",
"itertools 0.12.1",
"log",
"md-5",
"rand",
"regex",
"sha2 0.10.8",
"unicode-segmentation",
"uuid",
]
[[package]]
name = "datafusion-functions-aggregate"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
version = "41.0.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
checksum = "2b4ece19f73c02727e5e8654d79cd5652de371352c1df3c4ac3e419ecd6943fb"
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
dependencies = [
"ahash",
"arrow",
"arrow-schema",
"datafusion-common",
"datafusion-execution",
"datafusion-expr",
"datafusion-physical-expr-common",
"log",
"paste",
"sqlparser",
]
[[package]]
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
name = "datafusion-functions-nested"
version = "41.0.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
checksum = "a1474552cc824e8c9c88177d454db5781d4b66757d4aca75719306b8343a5e8d"
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
dependencies = [
"arrow",
"arrow-array",
"arrow-buffer",
"arrow-ord",
"arrow-schema",
"datafusion-common",
"datafusion-execution",
"datafusion-expr",
"datafusion-functions",
Bump datafusion from 39.0.0 to 40.0.0 (#831) Bumps [datafusion](https://github.com/apache/datafusion) from 39.0.0 to 40.0.0. V3_GIT_ORIGIN_REV_ID: 9712564df13c0e6f9bd2f551566385f8a9fe86c8
2024-07-15 14:14:04 +03:00
"datafusion-functions-aggregate",
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
"itertools 0.12.1",
"log",
"paste",
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
"rand",
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
]
[[package]]
name = "datafusion-optimizer"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
version = "41.0.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
checksum = "791ff56f55608bc542d1ea7a68a64bdc86a9413f5a381d06a39fd49c2a3ab906"
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
dependencies = [
"arrow",
"async-trait",
"chrono",
"datafusion-common",
"datafusion-expr",
"datafusion-physical-expr",
"hashbrown 0.14.5",
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"indexmap 2.4.0",
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
"itertools 0.12.1",
"log",
Bump datafusion from 39.0.0 to 40.0.0 (#831) Bumps [datafusion](https://github.com/apache/datafusion) from 39.0.0 to 40.0.0. V3_GIT_ORIGIN_REV_ID: 9712564df13c0e6f9bd2f551566385f8a9fe86c8
2024-07-15 14:14:04 +03:00
"paste",
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
"regex-syntax",
]
[[package]]
name = "datafusion-physical-expr"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
version = "41.0.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
checksum = "9a223962b3041304a3e20ed07a21d5de3d88d7e4e71ca192135db6d24e3365a4"
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
dependencies = [
"ahash",
"arrow",
"arrow-array",
"arrow-buffer",
"arrow-ord",
"arrow-schema",
"arrow-string",
"base64 0.22.1",
"chrono",
"datafusion-common",
"datafusion-execution",
"datafusion-expr",
"datafusion-physical-expr-common",
"half",
"hashbrown 0.14.5",
"hex",
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"indexmap 2.4.0",
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
"itertools 0.12.1",
"log",
"paste",
"petgraph",
"regex",
]
[[package]]
name = "datafusion-physical-expr-common"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
version = "41.0.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
checksum = "db5e7d8532a1601cd916881db87a70b0a599900d23f3db2897d389032da53bc6"
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
dependencies = [
Bump datafusion from 39.0.0 to 40.0.0 (#831) Bumps [datafusion](https://github.com/apache/datafusion) from 39.0.0 to 40.0.0. V3_GIT_ORIGIN_REV_ID: 9712564df13c0e6f9bd2f551566385f8a9fe86c8
2024-07-15 14:14:04 +03:00
"ahash",
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
"arrow",
"datafusion-common",
"datafusion-expr",
Bump datafusion from 39.0.0 to 40.0.0 (#831) Bumps [datafusion](https://github.com/apache/datafusion) from 39.0.0 to 40.0.0. V3_GIT_ORIGIN_REV_ID: 9712564df13c0e6f9bd2f551566385f8a9fe86c8
2024-07-15 14:14:04 +03:00
"hashbrown 0.14.5",
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
"rand",
]
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
[[package]]
name = "datafusion-physical-optimizer"
version = "41.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fdb9c78f308e050f5004671039786a925c3fee83b90004e9fcfd328d7febdcc0"
dependencies = [
"datafusion-common",
"datafusion-execution",
"datafusion-physical-expr",
"datafusion-physical-plan",
]
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
[[package]]
name = "datafusion-physical-plan"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
version = "41.0.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
checksum = "8d1116949432eb2d30f6362707e2846d942e491052a206f2ddcb42d08aea1ffe"
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
dependencies = [
"ahash",
"arrow",
"arrow-array",
"arrow-buffer",
"arrow-ord",
"arrow-schema",
"async-trait",
"chrono",
"datafusion-common",
"datafusion-common-runtime",
"datafusion-execution",
"datafusion-expr",
"datafusion-functions-aggregate",
"datafusion-physical-expr",
"datafusion-physical-expr-common",
"futures",
"half",
"hashbrown 0.14.5",
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"indexmap 2.4.0",
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
"itertools 0.12.1",
"log",
"once_cell",
"parking_lot",
"pin-project-lite",
"rand",
"tokio",
]
[[package]]
name = "datafusion-sql"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
version = "41.0.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
checksum = "b45d0180711165fe94015d7c4123eb3e1cf5fb60b1506453200b8d1ce666bef0"
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
dependencies = [
"arrow",
"arrow-array",
"arrow-schema",
"datafusion-common",
"datafusion-expr",
"log",
"regex",
"sqlparser",
"strum",
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
]
[[package]]
name = "der"
version = "0.4.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "79b71cca7d95d7681a4b3b9cdf63c8dbc3730d0584c2c74e31416d64a90493f4"
dependencies = [
"const-oid",
]
[[package]]
name = "deranged"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.3.11"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "b42b6fa04a440b495c8b04d0e71b707c585f83cb9cb28cf8cd0d976c315e31b4"
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
dependencies = [
"powerfmt",
"serde",
]
[[package]]
name = "derive_more"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.99.18"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "5f33878137e4dafd7fa914ad4e259e18a4e8e532b9617a2d0150262bf53abfce"
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
dependencies = [
Custom deserializer for OpenDd objects (#313) V3_GIT_ORIGIN_REV_ID: 4c7a9380e517ac8e7ac1bd44dbe879918bd0d9a2
2024-03-11 15:16:53 +03:00
"convert_case 0.4.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
"proc-macro2",
"quote",
"rustc_version",
Bump syn from 2.0.75 to 2.0.76 (#1017) Bumps [syn](https://github.com/dtolnay/syn) from 2.0.75 to 2.0.76. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/syn/releases">syn's releases</a>.</em></p> <blockquote> <h2>2.0.76</h2> <ul> <li>Enforce that tail call <code>become</code> keyword is followed by an expression (<a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/syn/commit/ef3e9c6dde79be7590fc90278772663ca31c1a73"><code>ef3e9c6</code></a> Release 2.0.76</li> <li><a href="https://github.com/dtolnay/syn/commit/8f7365ff9685c8ca9527c2de409204179a3efcdf"><code>8f7365f</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a> from dtolnay/tailcall</li> <li><a href="https://github.com/dtolnay/syn/commit/6cddd9ea714fe034466b4f02d3f7abb484c65ea0"><code>6cddd9e</code></a> Make tail call expr mandatory</li> <li>See full diff in <a href="https://github.com/dtolnay/syn/compare/2.0.75...2.0.76">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=syn&package-manager=cargo&previous-version=2.0.75&new-version=2.0.76)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d261ad30ffeb10034a80f9044504cb9d6c7c1ff7
2024-08-26 14:39:45 +03:00
"syn 2.0.76",
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
]
Include the dev-auth-webhook crate in the workspace. (#500) Now that the Dockerfile is in the root, there's no reason not to. V3_GIT_ORIGIN_REV_ID: 62199715c2a5aaaf1ac45e22c9d8bdac6838fd72
2024-04-24 11:11:48 +03:00
[[package]]
name = "dev-auth-webhook"
Use v3.0.0 as the version number. (#999) ### What Updates the version number to `3.0.0`, now we're officially at GA. ### How I updated the version number, and also updated some dependencies. The `Cargo.lock` file was not up to date. V3_GIT_ORIGIN_REV_ID: 3e9b784c8ad856556193e56aee9fa607fa8ce19e
2024-08-21 17:02:43 +03:00
version = "3.0.0"
Include the dev-auth-webhook crate in the workspace. (#500) Now that the Dockerfile is in the root, there's no reason not to. V3_GIT_ORIGIN_REV_ID: 62199715c2a5aaaf1ac45e22c9d8bdac6838fd72
2024-04-24 11:11:48 +03:00
dependencies = [
"anyhow",
"axum",
Add graceful shutdown to all cloud servers (#1023) <!-- The PR description should answer 2 important questions: --> ### What Put graceful shutdown code in a new crate. ### How <!-- How is it trying to accomplish it (what are the implementation steps)? --> V3_GIT_ORIGIN_REV_ID: 262cd85064f0420d2170a3bf710ab72853b5764d
2024-08-28 13:23:08 +03:00
"axum-ext",
add a flag to log traces to stdout (#931) ### What Add a flag `--export-traces-stdout` to log traces to stdout. Default is disabled. Command-line flag - `--export-traces-stdout` Env var - `EXPORT_TRACES_STDOUT` ### How Introduce a new command line flag. Make `initialize_tracing` accept a `bool`, and setup the stdout exporter based on that. <!-- How is it trying to accomplish it (what are the implementation steps)? --> V3_GIT_ORIGIN_REV_ID: f39d6f863fd2bca65ad89f1cef4b077aa9eabc5b
2024-08-05 11:01:38 +03:00
"clap",
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
"http",
add a flag to log traces to stdout (#931) ### What Add a flag `--export-traces-stdout` to log traces to stdout. Default is disabled. Command-line flag - `--export-traces-stdout` Env var - `EXPORT_TRACES_STDOUT` ### How Introduce a new command line flag. Make `initialize_tracing` accept a `bool`, and setup the stdout exporter based on that. <!-- How is it trying to accomplish it (what are the implementation steps)? --> V3_GIT_ORIGIN_REV_ID: f39d6f863fd2bca65ad89f1cef4b077aa9eabc5b
2024-08-05 11:01:38 +03:00
"serde",
Include the dev-auth-webhook crate in the workspace. (#500) Now that the Dockerfile is in the root, there's no reason not to. V3_GIT_ORIGIN_REV_ID: 62199715c2a5aaaf1ac45e22c9d8bdac6838fd72
2024-04-24 11:11:48 +03:00
"serde_json",
"tokio",
"tower-http",
"tracing",
"tracing-util",
]
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
[[package]]
name = "diff"
version = "0.1.13"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "56254986775e3233ffa9c4d7d3faaf6d36a2c09d30b20687e9f88bc8bafc16c8"
[[package]]
name = "diffy"
Bump diffy from 0.3.0 to 0.4.0 (#718) Bumps [diffy](https://github.com/bmwill/diffy) from 0.3.0 to 0.4.0. Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: a8d610058bfb0f0fd7af547882724457202c25f8
2024-06-17 08:29:16 +03:00
version = "0.4.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
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump diffy from 0.3.0 to 0.4.0 (#718) Bumps [diffy](https://github.com/bmwill/diffy) from 0.3.0 to 0.4.0. Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: a8d610058bfb0f0fd7af547882724457202c25f8
2024-06-17 08:29:16 +03:00
checksum = "5d3041965b7a63e70447ec818a46b1e5297f7fcae3058356d226c02750c4e6cb"
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
dependencies = [
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"nu-ansi-term 0.50.1",
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
]
[[package]]
name = "digest"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d3dd60d1080a57a05ab032377049e0591415d2b31afd7028356dbf3cc6dcb066"
dependencies = [
"generic-array",
]
add field arguments in schema and execution (#695) ### TODO - [x] Validate the presence of arguments in the data connector schema - [x] Add test for IR - [x] Add test using custom connector ## Description JIRA: https://hasurahq.atlassian.net/browse/V3ENGINE-148 This is part 2 of the field arguments. This will add the field arguments to the graphql schema and also handles the execution part. ![image](https://github.com/hasura/v3-engine/assets/85472423/c8f55d70-6539-42ef-ab5a-91b74e5699e2) ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> Add support for field arguments <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> --------- Co-authored-by: Anon Ray <ecthiender@users.noreply.github.com> Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: ea06b896feaca30419f81cd070fd4cfd608ef35b
2024-06-19 11:14:24 +03:00
[[package]]
name = "digest"
version = "0.10.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9ed9a281f7bc9b7576e61468ba615a66a5c8cfdff42420a70aa82701a3b1e292"
dependencies = [
"block-buffer 0.10.4",
"crypto-common",
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
"subtle",
add field arguments in schema and execution (#695) ### TODO - [x] Validate the presence of arguments in the data connector schema - [x] Add test for IR - [x] Add test using custom connector ## Description JIRA: https://hasurahq.atlassian.net/browse/V3ENGINE-148 This is part 2 of the field arguments. This will add the field arguments to the graphql schema and also handles the execution part. ![image](https://github.com/hasura/v3-engine/assets/85472423/c8f55d70-6539-42ef-ab5a-91b74e5699e2) ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> Add support for field arguments <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> --------- Co-authored-by: Anon Ray <ecthiender@users.noreply.github.com> Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: ea06b896feaca30419f81cd070fd4cfd608ef35b
2024-06-19 11:14:24 +03:00
]
lang-graphql: add parser tests (#290) Co-authored-by: Abhinav Gupta <127770473+abhinav-hasura@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d7b70a3cc70e6b9ead5867fd4b4fc56809878ebd
2024-01-30 20:41:48 +03:00
[[package]]
name = "dissimilar"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "1.0.9"
lang-graphql: add parser tests (#290) Co-authored-by: Abhinav Gupta <127770473+abhinav-hasura@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d7b70a3cc70e6b9ead5867fd4b4fc56809878ebd
2024-01-30 20:41:48 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "59f8e79d1fbf76bdfbde321e902714bf6c49df88a7dda6fc682fc2979226962d"
lang-graphql: add parser tests (#290) Co-authored-by: Abhinav Gupta <127770473+abhinav-hasura@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d7b70a3cc70e6b9ead5867fd4b4fc56809878ebd
2024-01-30 20:41:48 +03:00
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
[[package]]
name = "doc-comment"
version = "0.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fea41bba32d969b513997752735605054bc0dfa92b4c56bf1189f2e174be7a10"
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
[[package]]
name = "dyn-clone"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "1.0.17"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "0d6ef0072f8a535281e4876be788938b528e9a1d43900b82c2569af7da799125"
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
[[package]]
name = "ecdsa"
version = "0.12.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "43ee23aa5b4f68c7a092b5c3beb25f50c406adc75e2363634f242f28ab255372"
dependencies = [
"der",
"elliptic-curve",
"hmac",
"signature",
]
[[package]]
name = "either"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "1.13.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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "60b1af1c220855b6ceac025d3f6ecdd2b7c4894bfe9cd9bda4fbb4bc7c0d4cf0"
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
[[package]]
name = "elliptic-curve"
Update to Rust v1.80.1. (#1002) ### What Upgrade to the latest version of Rust. ### How I modified `rust-toolchain.toml` and ran `cargo update`. V3_GIT_ORIGIN_REV_ID: 5fe675ee5dc568cd24de542c826ffd2d355f90ff
2024-08-22 11:08:47 +03:00
version = "0.10.6"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update to Rust v1.80.1. (#1002) ### What Upgrade to the latest version of Rust. ### How I modified `rust-toolchain.toml` and ran `cargo update`. V3_GIT_ORIGIN_REV_ID: 5fe675ee5dc568cd24de542c826ffd2d355f90ff
2024-08-22 11:08:47 +03:00
checksum = "beca177dcb8eb540133e7680baff45e7cc4d93bf22002676cec549f82343721b"
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
dependencies = [
"crypto-bigint",
"ff",
"generic-array",
"group",
"pkcs8",
"rand_core",
"subtle",
"zeroize",
]
[[package]]
name = "embedded-io"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ef1a6892d9eef45c8fa6b9e0086428a2cca8491aca8f787c534a3d6d0bcb3ced"
Update to Rust v1.80.1. (#1002) ### What Upgrade to the latest version of Rust. ### How I modified `rust-toolchain.toml` and ran `cargo update`. V3_GIT_ORIGIN_REV_ID: 5fe675ee5dc568cd24de542c826ffd2d355f90ff
2024-08-22 11:08:47 +03:00
[[package]]
name = "embedded-io"
version = "0.6.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "edd0f118536f44f5ccd48bcb8b111bdc3de888b58c74639dfb034a357d0f206d"
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
[[package]]
name = "encode_unicode"
version = "0.3.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a357d28ed41a50f9c765dbfe56cbc04a64e53e5fc58ba79fbc34c10ef3df831f"
[[package]]
name = "encoding_rs"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.8.34"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "b45de904aa0b010bce2ab45264d0631681847fa7b6f2eaa7dab7619943bc4f59"
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
dependencies = [
"cfg-if",
]
[[package]]
name = "engine"
Use v3.0.0 as the version number. (#999) ### What Updates the version number to `3.0.0`, now we're officially at GA. ### How I updated the version number, and also updated some dependencies. The `Cargo.lock` file was not up to date. V3_GIT_ORIGIN_REV_ID: 3e9b784c8ad856556193e56aee9fa607fa8ce19e
2024-08-21 17:02:43 +03:00
version = "3.0.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
dependencies = [
Custom deserializer for OpenDd objects (#313) V3_GIT_ORIGIN_REV_ID: 4c7a9380e517ac8e7ac1bd44dbe879918bd0d9a2
2024-03-11 15:16:53 +03:00
"anyhow",
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
"axum",
Add graceful shutdown to all cloud servers (#1023) <!-- The PR description should answer 2 important questions: --> ### What Put graceful shutdown code in a new crate. ### How <!-- How is it trying to accomplish it (what are the implementation steps)? --> V3_GIT_ORIGIN_REV_ID: 262cd85064f0420d2170a3bf710ab72853b5764d
2024-08-28 13:23:08 +03:00
"axum-ext",
Bump base64 from 0.22.0 to 0.22.1 (#551) V3_GIT_ORIGIN_REV_ID: 5cebb181c8edd4dc539ce7166156cc9a2d6c47a4
2024-05-07 11:21:15 +03:00
"base64 0.22.1",
use short commit SHA as version and mark non-release builds as dev (#295) V3_GIT_ORIGIN_REV_ID: 78475725003cd57790361caa8659c7a7146eacf2
2024-01-25 11:53:24 +03:00
"build-data",
Bump Criterion lib (#504) <!-- Thank you for submitting this PR! :) --> ## Description Benchmarks are running pretty slowly in Github, let's check it's not an old library version problem. --------- Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: db1a70c5465cf475fa66d2afc981fd496eccacaa
2024-04-24 18:52:47 +03:00
"clap",
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
"criterion",
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
"execute",
Expose request type in multitenant metrics (#1009) <!-- The PR description should answer 2 important questions: --> ### What Expose operation type in query and explain endpoints. V3_GIT_ORIGIN_REV_ID: 852276fc04b3173a9364e593c33d1ceb6bd88064
2024-08-28 13:58:08 +03:00
"futures-util",
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
"goldenfile",
"hasura-authn-core",
"hasura-authn-jwt",
Implement `NoAuth` mode in `AuthConfig` (#877) <!-- The PR description should answer 2 (maybe 3) important questions: --> ### What We'd like to make it simpler to try out DDN, by starting with a mode that uses no auth. <!-- What is this PR trying to accomplish (and why, if it's not obvious)? --> <!-- Consider: do we need to add a changelog entry? --> ### How Add a `NoAuth` `AuthConfig` mode that is configured thus: ```json "noAuth": { "role": "admin", "sessionVariables": { "x-hasura-user-id": "1" } } ``` Given the above config: - If no `x-hasura-role` is sent with a request, we run it as `admin`. - If a `x-hasura-role` header is sent and it's `admin`, it continues to work - If any other `x-hasura-role` header is sent, an error will happen. - All other headers are ignored, and we always set `x-hasura-user-id` to 1 <!-- How is it trying to accomplish it (what are the implementation steps)? --> V3_GIT_ORIGIN_REV_ID: dddcfbee9c3a31e84dfc8013de32e3a9bf31943d
2024-07-25 18:48:35 +03:00
"hasura-authn-noauth",
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
"hasura-authn-webhook",
"json_value_merge",
"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
"metadata-resolve",
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",
if no plugins make middleware no-op (#948) <!-- The PR description should answer 2 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? --> <!-- Does this PR introduce new validation that might break old builds? --> <!-- Consider: do we need to put new checks behind a flag? --> Just an improvement to the middleware plugin ### How <!-- How is it trying to accomplish it (what are the implementation steps)? --> We now take a nonempty list of plugins. This ensures that we only do things if we have plugins. V3_GIT_ORIGIN_REV_ID: c8fb548f763cdefe3526c67d7c801104ad5c527a
2024-08-09 18:17:29 +03:00
"nonempty",
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
"open-dds",
Custom deserializer for OpenDd objects (#313) V3_GIT_ORIGIN_REV_ID: 4c7a9380e517ac8e7ac1bd44dbe879918bd0d9a2
2024-03-11 15:16:53 +03:00
"opendds-derive",
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
"pre-execution-plugin",
Enforce titles are set on most metadata json schemas (#434) - Adds titles to json schemas where missing - Adds tests to ensure we don't miss titles in the future (modulo some exceptions) This is required to be able to autogenerate the docs for the metadata V3_GIT_ORIGIN_REV_ID: e2027f3e3d5ee3546af99ff5c2d6de59604a3aec
2024-04-03 02:38:51 +03:00
"pretty_assertions",
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
"reqwest",
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
"schema",
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
"schemars",
"serde",
"serde_json",
Custom deserializer for OpenDd objects (#313) V3_GIT_ORIGIN_REV_ID: 4c7a9380e517ac8e7ac1bd44dbe879918bd0d9a2
2024-03-11 15:16:53 +03:00
"serde_path_to_error",
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
"sql",
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
"thiserror",
"tokio",
"tokio-test",
enable CORS in engine server (#560) <!-- Thank you for submitting this PR! :) --> ## Description JIRA: https://hasurahq.atlassian.net/browse/V3ENGINE-135 Introduce an option to enable CORS in engine's single tenant server. - `--enable-cors` CLI flag or `ENABLE_CORS=true` env var to support preflight CORS request and include relevant headers in responses. - `--cors-allow-origin` CLI option or `CORS_ALLOW_ORIGIN=` env var that accepts comma-separated list of allowed origin domains. <!-- Questions to consider answering: 1. What user-facing changes are being made? 2. What are issues related to this PR? (Consider adding `(close #<issue-no>)` to the PR title) 3. What is the conceptual design behind this PR? 4. How can this PR be tested/verified? 5. Does the PR have limitations? 6. Does the PR introduce breaking changes? --> ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [ ] community-edition - [ ] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [ ] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> _Replace with changelog entry_ <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> --------- Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: d562cde28898416cfbfd00ffd97e7b668ff3c953
2024-05-08 17:03:38 +03:00
"tower",
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
"tower-http",
"tracing-util",
]
Add support for HTTP/2 to the custom connector. (#581) Enable HTTP/2 support for Axum, so that we can make use of request multiplexing from the engine in the future. I also added an `env_logger` to the custom connector so we can see what's going on there. V3_GIT_ORIGIN_REV_ID: 3082b988ae3d149ee548f94638308876734b26df
2024-05-14 18:10:42 +03:00
[[package]]
name = "env_filter"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.1.2"
Add support for HTTP/2 to the custom connector. (#581) Enable HTTP/2 support for Axum, so that we can make use of request multiplexing from the engine in the future. I also added an `env_logger` to the custom connector so we can see what's going on there. V3_GIT_ORIGIN_REV_ID: 3082b988ae3d149ee548f94638308876734b26df
2024-05-14 18:10:42 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "4f2c92ceda6ceec50f43169f9ee8424fe2db276791afde7b2cd8bc084cb376ab"
Add support for HTTP/2 to the custom connector. (#581) Enable HTTP/2 support for Axum, so that we can make use of request multiplexing from the engine in the future. I also added an `env_logger` to the custom connector so we can see what's going on there. V3_GIT_ORIGIN_REV_ID: 3082b988ae3d149ee548f94638308876734b26df
2024-05-14 18:10:42 +03:00
dependencies = [
"log",
"regex",
]
[[package]]
name = "env_logger"
Bump env_logger from 0.11.3 to 0.11.5 (#896) Bumps [env_logger](https://github.com/rust-cli/env_logger) from 0.11.3 to 0.11.5. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/rust-cli/env_logger/releases">env_logger's releases</a>.</em></p> <blockquote> <h2>v0.11.5</h2> <h2>[0.11.5] - 2024-07-25</h2> <h2>v0.11.4</h2> <h2>[0.11.4] - 2024-07-23</h2> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/rust-cli/env_logger/blob/main/CHANGELOG.md">env_logger's changelog</a>.</em></p> <blockquote> <h2>[0.11.5] - 2024-07-25</h2> <h2>[0.11.4] - 2024-07-23</h2> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/rust-cli/env_logger/commit/73bb4188026f1ad5e6409c4148d37d572cc921bd"><code>73bb418</code></a> chore: Release</li> <li><a href="https://github.com/rust-cli/env_logger/commit/57f1bb7aaead25cfbaad629c344f027a8fd8615b"><code>57f1bb7</code></a> chore: Release</li> <li><a href="https://github.com/rust-cli/env_logger/commit/ba2748f48cbc5fe2b57be0075278adaeb5b5570c"><code>ba2748f</code></a> chore: Release</li> <li><a href="https://github.com/rust-cli/env_logger/commit/4dd976b01e8613b4c65d4eb4d8a69c7dd0fc869c"><code>4dd976b</code></a> Merge pull request <a href="https://redirect.github.com/rust-cli/env_logger/issues/324">#324</a> from Maximkaaa/try_parse</li> <li><a href="https://github.com/rust-cli/env_logger/commit/05aacb93c5193624c664177ad5f473f7efc5c94d"><code>05aacb9</code></a> feat: Add Builder::try_parse method</li> <li><a href="https://github.com/rust-cli/env_logger/commit/faf5b3e4998b2a5babf44e3dac7f6ebe1a85c4c0"><code>faf5b3e</code></a> chore: Tests for <code>parse_spec</code> error messages</li> <li><a href="https://github.com/rust-cli/env_logger/commit/c42511cc3cb31d4d6e908af7ac33a7cd9ce8674a"><code>c42511c</code></a> refactor: Return errors from <code>parse_spec</code></li> <li><a href="https://github.com/rust-cli/env_logger/commit/0e25d9e993241f1c57f6f7c2ab775a407a87fa3f"><code>0e25d9e</code></a> chore(deps): Update Rust Stable to v1.79 (<a href="https://redirect.github.com/rust-cli/env_logger/issues/322">#322</a>)</li> <li><a href="https://github.com/rust-cli/env_logger/commit/e1640c493d537999281e87815ac03ca6d23fe36d"><code>e1640c4</code></a> Merge pull request <a href="https://redirect.github.com/rust-cli/env_logger/issues/320">#320</a> from epage/template</li> <li><a href="https://github.com/rust-cli/env_logger/commit/f8acfee6861bc427f181a0c0d0892605f77bf0e9"><code>f8acfee</code></a> chore: Update from _rust/main template</li> <li>Additional commits viewable in <a href="https://github.com/rust-cli/env_logger/compare/v0.11.3...v0.11.5">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=env_logger&package-manager=cargo&previous-version=0.11.3&new-version=0.11.5)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: 1e051c353b7c5ff1e2ab6aaa43a5231858de517a
2024-07-29 13:09:00 +03:00
version = "0.11.5"
Add support for HTTP/2 to the custom connector. (#581) Enable HTTP/2 support for Axum, so that we can make use of request multiplexing from the engine in the future. I also added an `env_logger` to the custom connector so we can see what's going on there. V3_GIT_ORIGIN_REV_ID: 3082b988ae3d149ee548f94638308876734b26df
2024-05-14 18:10:42 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump env_logger from 0.11.3 to 0.11.5 (#896) Bumps [env_logger](https://github.com/rust-cli/env_logger) from 0.11.3 to 0.11.5. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/rust-cli/env_logger/releases">env_logger's releases</a>.</em></p> <blockquote> <h2>v0.11.5</h2> <h2>[0.11.5] - 2024-07-25</h2> <h2>v0.11.4</h2> <h2>[0.11.4] - 2024-07-23</h2> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/rust-cli/env_logger/blob/main/CHANGELOG.md">env_logger's changelog</a>.</em></p> <blockquote> <h2>[0.11.5] - 2024-07-25</h2> <h2>[0.11.4] - 2024-07-23</h2> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/rust-cli/env_logger/commit/73bb4188026f1ad5e6409c4148d37d572cc921bd"><code>73bb418</code></a> chore: Release</li> <li><a href="https://github.com/rust-cli/env_logger/commit/57f1bb7aaead25cfbaad629c344f027a8fd8615b"><code>57f1bb7</code></a> chore: Release</li> <li><a href="https://github.com/rust-cli/env_logger/commit/ba2748f48cbc5fe2b57be0075278adaeb5b5570c"><code>ba2748f</code></a> chore: Release</li> <li><a href="https://github.com/rust-cli/env_logger/commit/4dd976b01e8613b4c65d4eb4d8a69c7dd0fc869c"><code>4dd976b</code></a> Merge pull request <a href="https://redirect.github.com/rust-cli/env_logger/issues/324">#324</a> from Maximkaaa/try_parse</li> <li><a href="https://github.com/rust-cli/env_logger/commit/05aacb93c5193624c664177ad5f473f7efc5c94d"><code>05aacb9</code></a> feat: Add Builder::try_parse method</li> <li><a href="https://github.com/rust-cli/env_logger/commit/faf5b3e4998b2a5babf44e3dac7f6ebe1a85c4c0"><code>faf5b3e</code></a> chore: Tests for <code>parse_spec</code> error messages</li> <li><a href="https://github.com/rust-cli/env_logger/commit/c42511cc3cb31d4d6e908af7ac33a7cd9ce8674a"><code>c42511c</code></a> refactor: Return errors from <code>parse_spec</code></li> <li><a href="https://github.com/rust-cli/env_logger/commit/0e25d9e993241f1c57f6f7c2ab775a407a87fa3f"><code>0e25d9e</code></a> chore(deps): Update Rust Stable to v1.79 (<a href="https://redirect.github.com/rust-cli/env_logger/issues/322">#322</a>)</li> <li><a href="https://github.com/rust-cli/env_logger/commit/e1640c493d537999281e87815ac03ca6d23fe36d"><code>e1640c4</code></a> Merge pull request <a href="https://redirect.github.com/rust-cli/env_logger/issues/320">#320</a> from epage/template</li> <li><a href="https://github.com/rust-cli/env_logger/commit/f8acfee6861bc427f181a0c0d0892605f77bf0e9"><code>f8acfee</code></a> chore: Update from _rust/main template</li> <li>Additional commits viewable in <a href="https://github.com/rust-cli/env_logger/compare/v0.11.3...v0.11.5">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=env_logger&package-manager=cargo&previous-version=0.11.3&new-version=0.11.5)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: 1e051c353b7c5ff1e2ab6aaa43a5231858de517a
2024-07-29 13:09:00 +03:00
checksum = "e13fa619b91fb2381732789fc5de83b45675e882f66623b7d8cb4f643017018d"
Add support for HTTP/2 to the custom connector. (#581) Enable HTTP/2 support for Axum, so that we can make use of request multiplexing from the engine in the future. I also added an `env_logger` to the custom connector so we can see what's going on there. V3_GIT_ORIGIN_REV_ID: 3082b988ae3d149ee548f94638308876734b26df
2024-05-14 18:10:42 +03:00
dependencies = [
"anstream",
"anstyle",
"env_filter",
"humantime",
"log",
]
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
[[package]]
name = "equivalent"
version = "1.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5443807d6dff69373d433ab9ef5378ad8df50ca6298caf15de6e52e24aaf54d5"
[[package]]
name = "errno"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.3.9"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "534c5cf6194dfab3db3242765c03bbe257cf92f22b38f6bc0c58d59108a820ba"
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
dependencies = [
"libc",
"windows-sys 0.52.0",
]
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
[[package]]
name = "execute"
Use v3.0.0 as the version number. (#999) ### What Updates the version number to `3.0.0`, now we're officially at GA. ### How I updated the version number, and also updated some dependencies. The `Cargo.lock` file was not up to date. V3_GIT_ORIGIN_REV_ID: 3e9b784c8ad856556193e56aee9fa607fa8ce19e
2024-08-21 17:02:43 +03:00
version = "3.0.0"
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
dependencies = [
"async-recursion",
"axum",
"base64 0.22.1",
"bytes",
"criterion",
test for concurrent execution of query root fields (#609) ## Description Add a helper function which execute items of an iterator concurrently. Add unit tests for that. Use the helper function in query root fields execution. V3_GIT_ORIGIN_REV_ID: a034291684135072cbaf957dc788a269b5a33459
2024-05-23 15:57:08 +03:00
"futures-ext",
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
"futures-util",
"goldenfile",
"hasura-authn-core",
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"indexmap 2.4.0",
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
"ir",
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
"json-ext",
"lang-graphql",
"metadata-resolve",
"mockito",
Use ndc-models 0.1.6 (#1013) <!-- The PR description should answer 2 important questions: --> ### What Update `v3-engine` to use `ndc-models` 0.1.6. ### How Update in Cargo.toml, check everything builds. V3_GIT_ORIGIN_REV_ID: 64d8b5b8126f593c10ffa89ba21791f326aefedd
2024-08-26 16:46:12 +03:00
"ndc-models 0.1.6",
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 0.2.0",
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
"nonempty",
"open-dds",
"pretty_assertions",
Implement query usage analytics (#713) JIRA: https://hasurahq.atlassian.net/browse/V3ENGINE-176 This PR implements usage analytics ([RFC](https://docs.google.com/document/d/1k8_ZniiejxHhD0SphtEJ2mg6MoJON0dkk0q4b5WZWDE/edit)) for a GraphQL query when a request is made. The analytics data JSON is attached to the span, whose details are provided below: Span name - `execute` Attribute - `internal.query_usage_analytics = <JSON-string>` OR `internal.query_usage_analytics_error = <String>` Refs: - [Link](https://github.com/hasura/v3-engine/pull/606) to the PR, where data types for usage analytics were added. - [Link](https://github.com/hasura/v3-engine/pull/715) to the PR, where some improvements are made to the analytics data types. Note: Changelog entry is added. V3_GIT_ORIGIN_REV_ID: f4089f3354b638533ff72fbec72951e883c31100
2024-07-01 15:09:27 +03:00
"query-usage-analytics",
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
"reqwest",
"schema",
"serde",
"serde_json",
"thiserror",
"tokio",
"tracing-util",
"transitive",
"url",
]
lang-graphql: add parser tests (#290) Co-authored-by: Abhinav Gupta <127770473+abhinav-hasura@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d7b70a3cc70e6b9ead5867fd4b4fc56809878ebd
2024-01-30 20:41:48 +03:00
[[package]]
name = "expect-test"
Bump expect-test from 1.4.1 to 1.5.0 (#571) V3_GIT_ORIGIN_REV_ID: b85e7346211b3e2f647974ca9d95661a412df00e
2024-05-13 16:28:41 +03:00
version = "1.5.0"
lang-graphql: add parser tests (#290) Co-authored-by: Abhinav Gupta <127770473+abhinav-hasura@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d7b70a3cc70e6b9ead5867fd4b4fc56809878ebd
2024-01-30 20:41:48 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump expect-test from 1.4.1 to 1.5.0 (#571) V3_GIT_ORIGIN_REV_ID: b85e7346211b3e2f647974ca9d95661a412df00e
2024-05-13 16:28:41 +03:00
checksum = "9e0be0a561335815e06dab7c62e50353134c796e7a6155402a64bcff66b6a5e0"
lang-graphql: add parser tests (#290) Co-authored-by: Abhinav Gupta <127770473+abhinav-hasura@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d7b70a3cc70e6b9ead5867fd4b4fc56809878ebd
2024-01-30 20:41:48 +03:00
dependencies = [
"dissimilar",
"once_cell",
]
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
[[package]]
name = "fastrand"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "2.1.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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "9fc0510504f03c51ada170672ac806f1f105a88aa97a5281117e1ddc3368e51a"
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
[[package]]
name = "ff"
version = "0.10.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d0f40b2dcd8bc322217a5f6559ae5f9e9d1de202a2ecee2e9eafcbece7562a4f"
dependencies = [
"rand_core",
"subtle",
]
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
[[package]]
name = "fixedbitset"
version = "0.4.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0ce7134b9999ecaf8bcd65542e436736ef32ddca1b3e06094cb6ec5755203b80"
[[package]]
name = "flatbuffers"
version = "24.3.25"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8add37afff2d4ffa83bc748a70b4b1370984f6980768554182424ef71447c35f"
dependencies = [
"bitflags 1.3.2",
"rustc_version",
]
[[package]]
name = "flate2"
Update to Rust v1.80.1. (#1002) ### What Upgrade to the latest version of Rust. ### How I modified `rust-toolchain.toml` and ran `cargo update`. V3_GIT_ORIGIN_REV_ID: 5fe675ee5dc568cd24de542c826ffd2d355f90ff
2024-08-22 11:08:47 +03:00
version = "1.0.32"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update to Rust v1.80.1. (#1002) ### What Upgrade to the latest version of Rust. ### How I modified `rust-toolchain.toml` and ran `cargo update`. V3_GIT_ORIGIN_REV_ID: 5fe675ee5dc568cd24de542c826ffd2d355f90ff
2024-08-22 11:08:47 +03:00
checksum = "9c0596c1eac1f9e04ed902702e9878208b336edc9d6fddc8a48387349bab3666"
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
dependencies = [
"crc32fast",
Update to Rust v1.80.1. (#1002) ### What Upgrade to the latest version of Rust. ### How I modified `rust-toolchain.toml` and ran `cargo update`. V3_GIT_ORIGIN_REV_ID: 5fe675ee5dc568cd24de542c826ffd2d355f90ff
2024-08-22 11:08:47 +03:00
"miniz_oxide 0.8.0",
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
]
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
[[package]]
name = "fluent-uri"
version = "0.1.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "17c704e9dbe1ddd863da1e6ff3567795087b1eb201ce80d8fa81162e1516500d"
dependencies = [
"bitflags 1.3.2",
]
[[package]]
name = "fnv"
version = "1.0.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3f9eec918d3f24069decb9af1554cad7c880e2da24a9afd88aca000531ab82c1"
[[package]]
name = "foreign-types"
version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f6f339eb8adc052cd2ca78910fda869aefa38d22d5cb648e6485e4d3fc06f3b1"
dependencies = [
"foreign-types-shared",
]
[[package]]
name = "foreign-types-shared"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "00b0228411908ca8685dba7fc2cdd70ec9990a6e753e89b6ac91a84c40fbaf4b"
[[package]]
name = "form_urlencoded"
version = "1.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e13624c2627564efccf4934284bdd98cbaa14e79b0b5a141218e507b3a823456"
dependencies = [
Remove unused dependencies using `cargo machete`. (#413) `cargo machete` is a very useful tool that figures out when you aren't using a dependency. I have run this locally to remove unused dependencies. I've also added a CI job to make sure we catch these in the future. Sometimes it reports false positives, e.g. when a dependency isn't used directly but in macro-generated code (e.g. with `strum`). I have added `"ignored"` clauses to the `Cargo.toml` files where appropriate. V3_GIT_ORIGIN_REV_ID: ed015089b695cec8eeb03ce455d6dd3cd312a016
2024-03-28 12:16:54 +03:00
"percent-encoding",
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
]
[[package]]
name = "funty"
version = "2.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e6d5a32815ae3f33302d95fdcb2ce17862f8c65363dcfd29360480ba1001fc9c"
[[package]]
name = "futures"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.3.30"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "645c6916888f6cb6350d2550b80fb63e734897a8498abe35cfb732b6487804b0"
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
dependencies = [
"futures-channel",
"futures-core",
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
"futures-executor",
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
"futures-io",
"futures-sink",
"futures-task",
"futures-util",
]
[[package]]
name = "futures-channel"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.3.30"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "eac8f7d7865dcb88bd4373ab671c8cf4508703796caa2b1985a9ca867b3fcb78"
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
dependencies = [
"futures-core",
"futures-sink",
]
[[package]]
name = "futures-core"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.3.30"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "dfc6580bb841c5a68e9ef15c77ccc837b40a7504914d52e47b8b0e9bbda25a1d"
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
[[package]]
name = "futures-executor"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.3.30"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "a576fc72ae164fca6b9db127eaa9a9dda0d61316034f33a0a0d4eda41f02b01d"
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
dependencies = [
"futures-core",
"futures-task",
"futures-util",
]
test for concurrent execution of query root fields (#609) ## Description Add a helper function which execute items of an iterator concurrently. Add unit tests for that. Use the helper function in query root fields execution. V3_GIT_ORIGIN_REV_ID: a034291684135072cbaf957dc788a269b5a33459
2024-05-23 15:57:08 +03:00
[[package]]
name = "futures-ext"
Use v3.0.0 as the version number. (#999) ### What Updates the version number to `3.0.0`, now we're officially at GA. ### How I updated the version number, and also updated some dependencies. The `Cargo.lock` file was not up to date. V3_GIT_ORIGIN_REV_ID: 3e9b784c8ad856556193e56aee9fa607fa8ce19e
2024-08-21 17:02:43 +03:00
version = "3.0.0"
test for concurrent execution of query root fields (#609) ## Description Add a helper function which execute items of an iterator concurrently. Add unit tests for that. Use the helper function in query root fields execution. V3_GIT_ORIGIN_REV_ID: a034291684135072cbaf957dc788a269b5a33459
2024-05-23 15:57:08 +03:00
dependencies = [
"futures-util",
"tokio",
]
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
[[package]]
name = "futures-io"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.3.30"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "a44623e20b9681a318efdd71c299b6b222ed6f231972bfe2f224ebad6311f0c1"
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
[[package]]
name = "futures-macro"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.3.30"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "87750cf4b7a4c0625b1529e4c543c2182106e4dedc60a2a6455e00d212c489ac"
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
dependencies = [
"proc-macro2",
"quote",
Bump syn from 2.0.75 to 2.0.76 (#1017) Bumps [syn](https://github.com/dtolnay/syn) from 2.0.75 to 2.0.76. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/syn/releases">syn's releases</a>.</em></p> <blockquote> <h2>2.0.76</h2> <ul> <li>Enforce that tail call <code>become</code> keyword is followed by an expression (<a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/syn/commit/ef3e9c6dde79be7590fc90278772663ca31c1a73"><code>ef3e9c6</code></a> Release 2.0.76</li> <li><a href="https://github.com/dtolnay/syn/commit/8f7365ff9685c8ca9527c2de409204179a3efcdf"><code>8f7365f</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a> from dtolnay/tailcall</li> <li><a href="https://github.com/dtolnay/syn/commit/6cddd9ea714fe034466b4f02d3f7abb484c65ea0"><code>6cddd9e</code></a> Make tail call expr mandatory</li> <li>See full diff in <a href="https://github.com/dtolnay/syn/compare/2.0.75...2.0.76">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=syn&package-manager=cargo&previous-version=2.0.75&new-version=2.0.76)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d261ad30ffeb10034a80f9044504cb9d6c7c1ff7
2024-08-26 14:39:45 +03:00
"syn 2.0.76",
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
]
[[package]]
name = "futures-sink"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.3.30"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "9fb8e00e87438d937621c1c6269e53f536c14d3fbd6a042bb24879e57d474fb5"
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
[[package]]
name = "futures-task"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.3.30"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "38d84fa142264698cdce1a9f9172cf383a0c82de1bddcf3092901442c4097004"
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
[[package]]
name = "futures-util"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.3.30"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "3d6401deb83407ab3da39eba7e33987a73c3df0c82b4bb5813ee871c19c41d48"
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
dependencies = [
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
"futures-channel",
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
"futures-core",
"futures-io",
"futures-macro",
"futures-sink",
"futures-task",
"memchr",
"pin-project-lite",
"pin-utils",
"slab",
]
[[package]]
name = "generic-array"
version = "0.14.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "85649ca51fd72272d7821adaf274ad91c288277713d9c18820d8499a7ff69e9a"
dependencies = [
"typenum",
"version_check",
]
[[package]]
name = "getrandom"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.2.15"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "c4567c8db10ae91089c99af84c68c38da3ec2f087c3f82960bcdbf3656b6f4d7"
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
dependencies = [
"cfg-if",
"libc",
"wasi",
]
[[package]]
name = "gimli"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.29.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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "40ecd4077b5ae9fd2e9e169b102c6c330d0605168eb0e8bf79952b256dbefffd"
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
OpenDD types for new boolean expressions (#599) <!-- Thank you for submitting this PR! :) --> ## Description We have a new `BooleanExpressionType` metadata kind. This adds it, tests it can be parsed, but hides it from generated metadata and throws an error if one is actually used in the engine. V3_GIT_ORIGIN_REV_ID: 036b5fd9c32475d1c5a5e5e6321fb736fe6caefa
2024-05-21 12:28:02 +03:00
[[package]]
name = "glob"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d2fabcfbdc87f4758337ca535fb41a6d701b65693ce38287d856d1674551ec9b"
Take snapshots of passing and failing metadata resolution. (#763) ### What In order to more easily monitor and review changes to metadata resolution, this introduces snapshot testing for both successful and failing calls to `resolve`. I used [Insta](https://insta.rs/) for this. ### How For tests of the failure case, we already had a text file with the expected error, so I have turned those files into snapshot files. I wrote a small script to move the files rather than deleting and recreating them so I could guarantee that the contents have not changed. (Unfortunately, Git's diff doesn't always recognise the move as a move because Insta has added a header.) For tests of the successful case, I added a line to snapshot the metadata rather than discarding it. I also rewrote the tests to use `insta::glob` so we could get rid of `test_each`. V3_GIT_ORIGIN_REV_ID: 41bef4cf77bddb8d20d7c101df52ae149e8b0476
2024-06-26 11:14:34 +03:00
[[package]]
name = "globset"
version = "0.4.14"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "57da3b9b5b85bd66f31093f8c408b90a74431672542466497dcbdfdc02034be1"
dependencies = [
"aho-corasick",
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"bstr",
Take snapshots of passing and failing metadata resolution. (#763) ### What In order to more easily monitor and review changes to metadata resolution, this introduces snapshot testing for both successful and failing calls to `resolve`. I used [Insta](https://insta.rs/) for this. ### How For tests of the failure case, we already had a text file with the expected error, so I have turned those files into snapshot files. I wrote a small script to move the files rather than deleting and recreating them so I could guarantee that the contents have not changed. (Unfortunately, Git's diff doesn't always recognise the move as a move because Insta has added a header.) For tests of the successful case, I added a line to snapshot the metadata rather than discarding it. I also rewrote the tests to use `insta::glob` so we could get rid of `test_each`. V3_GIT_ORIGIN_REV_ID: 41bef4cf77bddb8d20d7c101df52ae149e8b0476
2024-06-26 11:14:34 +03:00
"log",
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"regex-automata",
Take snapshots of passing and failing metadata resolution. (#763) ### What In order to more easily monitor and review changes to metadata resolution, this introduces snapshot testing for both successful and failing calls to `resolve`. I used [Insta](https://insta.rs/) for this. ### How For tests of the failure case, we already had a text file with the expected error, so I have turned those files into snapshot files. I wrote a small script to move the files rather than deleting and recreating them so I could guarantee that the contents have not changed. (Unfortunately, Git's diff doesn't always recognise the move as a move because Insta has added a header.) For tests of the successful case, I added a line to snapshot the metadata rather than discarding it. I also rewrote the tests to use `insta::glob` so we could get rid of `test_each`. V3_GIT_ORIGIN_REV_ID: 41bef4cf77bddb8d20d7c101df52ae149e8b0476
2024-06-26 11:14:34 +03:00
"regex-syntax",
]
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
[[package]]
name = "goldenfile"
Bump goldenfile from 1.6.0 to 1.7.1 (#552) V3_GIT_ORIGIN_REV_ID: 68a37111246c8a923a9e881f5bb944b770b17d8c
2024-05-07 12:12:49 +03:00
version = "1.7.1"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump goldenfile from 1.6.0 to 1.7.1 (#552) V3_GIT_ORIGIN_REV_ID: 68a37111246c8a923a9e881f5bb944b770b17d8c
2024-05-07 12:12:49 +03:00
checksum = "a0d5c44265baec620ea19c97b4ce9f068e28f8c3d7faccc483f02968b5e3c587"
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
dependencies = [
"scopeguard",
"similar-asserts",
"tempfile",
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
"yansi 1.0.1",
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
]
[[package]]
name = "graphql-parser"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d2ebc8013b4426d5b81a4364c419a95ed0b404af2b82e2457de52d9348f0e474"
dependencies = [
"combine",
"thiserror",
]
[[package]]
name = "group"
version = "0.10.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1c363a5301b8f153d80747126a04b3c82073b9fe3130571a9d170cacdeaf7912"
dependencies = [
"ff",
"rand_core",
"subtle",
]
[[package]]
name = "h2"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.3.26"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "81fe527a889e1532da5c525686d96d4c2e74cdd345badf8dfef9f6b39dd5f5e8"
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
dependencies = [
"bytes",
"fnv",
"futures-core",
"futures-sink",
"futures-util",
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
"http",
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"indexmap 2.4.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
"slab",
"tokio",
"tokio-util",
"tracing",
]
[[package]]
name = "half"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "2.4.1"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "6dd08c532ae367adf81c312a4580bc67f1d0fe8bc9c460520283f4c0ff277888"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
dependencies = [
"cfg-if",
"crunchy",
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
"num-traits",
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
]
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
[[package]]
name = "hash32"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b0c35f58762feb77d74ebe43bdbc3210f09be9fe6742234d573bacc26ed92b67"
dependencies = [
"byteorder",
]
[[package]]
name = "hashbrown"
version = "0.12.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8a9ee70c43aaf417c914396645a0fa852624801b24ebb7ae78fe8272889ac888"
[[package]]
name = "hashbrown"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.14.5"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "e5274423e17b7c9fc20b6e7e208532f9b19825d82dfd615708b70edd83df41f1"
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
dependencies = [
"ahash",
"allocator-api2",
]
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
[[package]]
name = "hasura-authn-core"
Use v3.0.0 as the version number. (#999) ### What Updates the version number to `3.0.0`, now we're officially at GA. ### How I updated the version number, and also updated some dependencies. The `Cargo.lock` file was not up to date. V3_GIT_ORIGIN_REV_ID: 3e9b784c8ad856556193e56aee9fa607fa8ce19e
2024-08-21 17:02:43 +03:00
version = "3.0.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
dependencies = [
"axum",
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
"http",
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
"lang-graphql",
"open-dds",
"pretty_assertions",
"schemars",
"serde",
Avoid `.unwrap` in favor of `anyhow` for better error messages in tests. (#430) I am struggling to diagnose some errors and `.unwrap` is not helping, as it doesn't properly capture stack traces or anything else that might be useful. `anyhow` was built for this. Let's use it. I had to convert `SessionError` to a real `Error`, which I don't think is a bad thing. V3_GIT_ORIGIN_REV_ID: 3b8a70bb87e12e7b9e39515cd5f769fbd2cbfb39
2024-04-02 20:06:13 +03:00
"thiserror",
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
]
[[package]]
name = "hasura-authn-jwt"
Use v3.0.0 as the version number. (#999) ### What Updates the version number to `3.0.0`, now we're officially at GA. ### How I updated the version number, and also updated some dependencies. The `Cargo.lock` file was not up to date. V3_GIT_ORIGIN_REV_ID: 3e9b784c8ad856556193e56aee9fa607fa8ce19e
2024-08-21 17:02:43 +03:00
version = "3.0.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
dependencies = [
Use `anyhow` in tests instead of unwrapping everywhere. (#475) Just a minor change to make tests more readable by avoiding `.unwrap()`. V3_GIT_ORIGIN_REV_ID: 2cc13b9750e24ea82dfefcc68a05ffd63e1b4b7c
2024-04-18 11:57:22 +03:00
"anyhow",
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
"axum",
"cookie",
"hasura-authn-core",
"jsonptr",
"jsonwebkey",
"jsonwebtoken",
"lang-graphql",
"mockito",
"open-dds",
"openssl",
"reqwest",
"schemars",
"serde",
"serde_json",
"thiserror",
"tokio",
"tracing-util",
Remove unused dependencies using `cargo machete`. (#413) `cargo machete` is a very useful tool that figures out when you aren't using a dependency. I have run this locally to remove unused dependencies. I've also added a CI job to make sure we catch these in the future. Sometimes it reports false positives, e.g. when a dependency isn't used directly but in macro-generated code (e.g. with `strum`). I have added `"ignored"` clauses to the `Cargo.toml` files where appropriate. V3_GIT_ORIGIN_REV_ID: ed015089b695cec8eeb03ce455d6dd3cd312a016
2024-03-28 12:16:54 +03:00
"url",
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
]
Implement `NoAuth` mode in `AuthConfig` (#877) <!-- The PR description should answer 2 (maybe 3) important questions: --> ### What We'd like to make it simpler to try out DDN, by starting with a mode that uses no auth. <!-- What is this PR trying to accomplish (and why, if it's not obvious)? --> <!-- Consider: do we need to add a changelog entry? --> ### How Add a `NoAuth` `AuthConfig` mode that is configured thus: ```json "noAuth": { "role": "admin", "sessionVariables": { "x-hasura-user-id": "1" } } ``` Given the above config: - If no `x-hasura-role` is sent with a request, we run it as `admin`. - If a `x-hasura-role` header is sent and it's `admin`, it continues to work - If any other `x-hasura-role` header is sent, an error will happen. - All other headers are ignored, and we always set `x-hasura-user-id` to 1 <!-- How is it trying to accomplish it (what are the implementation steps)? --> V3_GIT_ORIGIN_REV_ID: dddcfbee9c3a31e84dfc8013de32e3a9bf31943d
2024-07-25 18:48:35 +03:00
[[package]]
name = "hasura-authn-noauth"
Use v3.0.0 as the version number. (#999) ### What Updates the version number to `3.0.0`, now we're officially at GA. ### How I updated the version number, and also updated some dependencies. The `Cargo.lock` file was not up to date. V3_GIT_ORIGIN_REV_ID: 3e9b784c8ad856556193e56aee9fa607fa8ce19e
2024-08-21 17:02:43 +03:00
version = "3.0.0"
Implement `NoAuth` mode in `AuthConfig` (#877) <!-- The PR description should answer 2 (maybe 3) important questions: --> ### What We'd like to make it simpler to try out DDN, by starting with a mode that uses no auth. <!-- What is this PR trying to accomplish (and why, if it's not obvious)? --> <!-- Consider: do we need to add a changelog entry? --> ### How Add a `NoAuth` `AuthConfig` mode that is configured thus: ```json "noAuth": { "role": "admin", "sessionVariables": { "x-hasura-user-id": "1" } } ``` Given the above config: - If no `x-hasura-role` is sent with a request, we run it as `admin`. - If a `x-hasura-role` header is sent and it's `admin`, it continues to work - If any other `x-hasura-role` header is sent, an error will happen. - All other headers are ignored, and we always set `x-hasura-user-id` to 1 <!-- How is it trying to accomplish it (what are the implementation steps)? --> V3_GIT_ORIGIN_REV_ID: dddcfbee9c3a31e84dfc8013de32e3a9bf31943d
2024-07-25 18:48:35 +03:00
dependencies = [
"hasura-authn-core",
"schemars",
"serde",
"serde_json",
]
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
[[package]]
name = "hasura-authn-webhook"
Use v3.0.0 as the version number. (#999) ### What Updates the version number to `3.0.0`, now we're officially at GA. ### How I updated the version number, and also updated some dependencies. The `Cargo.lock` file was not up to date. V3_GIT_ORIGIN_REV_ID: 3e9b784c8ad856556193e56aee9fa607fa8ce19e
2024-08-21 17:02:43 +03:00
version = "3.0.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
dependencies = [
"axum",
"hasura-authn-core",
"lang-graphql",
"mockito",
"open-dds",
"rand",
"reqwest",
"schemars",
"serde",
"serde_json",
"thiserror",
"tokio",
"tracing-util",
]
[[package]]
name = "heapless"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.7.17"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "cdc6457c0eb62c71aac4bc17216026d8410337c4126773b9c5daba343f17964f"
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
dependencies = [
"atomic-polyfill",
"hash32",
"rustc_version",
"serde",
"spin 0.9.8",
"stable_deref_trait",
]
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
[[package]]
name = "heck"
version = "0.4.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "95505c38b4572b2d910cecb0281560f54b440a19336cbbcb27bf6ce6adc6f5a8"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
[[package]]
name = "heck"
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2304e00983f87ffb38b55b444b5e3b60a884b5d30c0fca7d82fe33449bbe55ea"
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
[[package]]
name = "hermit-abi"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.3.9"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "d231dfb89cfffdbc30e7fc41579ed6066ad03abda9e567ccafae602b97ec5024"
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
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
[[package]]
name = "hermit-abi"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fbf6a919d6cf397374f7dfeeea91d974c7c0a7221d0d0f4f20d859d329e53fcc"
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
[[package]]
name = "hex"
version = "0.4.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7f24254aa9a54b5c858eaee2f5bccdb46aaf0e486a595ed5fd8f86ba55232a70"
[[package]]
name = "hmac"
version = "0.11.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2a2a2320eb7ec0ebe8da8f744d7812d9fc4cb4d09344ac01898dbcb6a20ae69b"
dependencies = [
"crypto-mac",
add field arguments in schema and execution (#695) ### TODO - [x] Validate the presence of arguments in the data connector schema - [x] Add test for IR - [x] Add test using custom connector ## Description JIRA: https://hasurahq.atlassian.net/browse/V3ENGINE-148 This is part 2 of the field arguments. This will add the field arguments to the graphql schema and also handles the execution part. ![image](https://github.com/hasura/v3-engine/assets/85472423/c8f55d70-6539-42ef-ab5a-91b74e5699e2) ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> Add support for field arguments <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> --------- Co-authored-by: Anon Ray <ecthiender@users.noreply.github.com> Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: ea06b896feaca30419f81cd070fd4cfd608ef35b
2024-06-19 11:14:24 +03:00
"digest 0.9.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
]
[[package]]
name = "http"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.2.12"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "601cbb57e577e2f5ef5be8e7b83f0f63994f25aa94d673e54a92d5c516d101f1"
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
dependencies = [
"bytes",
"fnv",
"itoa",
]
[[package]]
name = "http-body"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.4.6"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "7ceab25649e9960c0311ea418d17bee82c0dcec1bd053b5f9a66e265a693bed2"
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
dependencies = [
"bytes",
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
"http",
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
"pin-project-lite",
]
[[package]]
name = "http-range-header"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "add0ab9360ddbd88cfeb3bd9574a1d85cfdfa14db10b3e21d3700dbc4328758f"
[[package]]
name = "httparse"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "1.9.4"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "0fcc0b4a115bf80b728eb8ea024ad5bd707b615bfed49e0665b6e0f86fd082d9"
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
[[package]]
name = "httpdate"
version = "1.0.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "df3b46402a9d5adb4c86a0cf463f42e19994e3ee891101b1841f30a545cb49a9"
[[package]]
name = "human_bytes"
version = "0.4.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "91f255a4535024abf7640cb288260811fc14794f62b063652ed349f9a6c2348e"
Add support for HTTP/2 to the custom connector. (#581) Enable HTTP/2 support for Axum, so that we can make use of request multiplexing from the engine in the future. I also added an `env_logger` to the custom connector so we can see what's going on there. V3_GIT_ORIGIN_REV_ID: 3082b988ae3d149ee548f94638308876734b26df
2024-05-14 18:10:42 +03:00
[[package]]
name = "humantime"
version = "2.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9a3a5bfb195931eeb336b2a7b4d761daec841b97f947d34394601737a7bba5e4"
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
[[package]]
name = "hyper"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.14.30"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "a152ddd61dfaec7273fe8419ab357f33aee0d914c5f4efbf0d96fa749eea5ec9"
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
dependencies = [
"bytes",
"futures-channel",
"futures-core",
"futures-util",
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
"h2",
"http",
"http-body",
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
"httparse",
"httpdate",
"itoa",
"pin-project-lite",
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
"socket2",
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
"tokio",
"tower-service",
"tracing",
"want",
]
[[package]]
name = "hyper-timeout"
version = "0.4.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bbb958482e8c7be4bc3cf272a766a2b0bf1a6755e7a6ae777f017a31d11b13b1"
dependencies = [
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
"hyper",
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
"pin-project-lite",
"tokio",
"tokio-io-timeout",
]
[[package]]
name = "hyper-tls"
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d6183ddfa99b85da61a140bea0efc93fdf56ceaa041b37d553518030827f9905"
dependencies = [
"bytes",
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
"hyper",
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
"native-tls",
"tokio",
"tokio-native-tls",
]
[[package]]
name = "iana-time-zone"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.1.60"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "e7ffbb5a1b541ea2561f8c41c087286cc091e21e556a4f09a8f6cbf17b69b141"
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
dependencies = [
"android_system_properties",
"core-foundation-sys",
"iana-time-zone-haiku",
"js-sys",
"wasm-bindgen",
"windows-core",
]
[[package]]
name = "iana-time-zone-haiku"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f31827a206f56af32e590ba56d5d2d085f558508192593743f16b2306495269f"
dependencies = [
"cc",
]
[[package]]
name = "ident_case"
version = "1.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b9e0384b61958566e926dc50660321d12159025e767c18e043daf26b70104c39"
[[package]]
name = "idna"
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "634d9b1461af396cad843f47fdba5597a4f9e6ddd4bfb6ff5d85028c25cb12f6"
dependencies = [
"unicode-bidi",
"unicode-normalization",
]
[[package]]
name = "indexmap"
version = "1.9.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bd070e393353796e801d209ad339e89596eb4c8d430d18ede6a1cced8fafbd99"
dependencies = [
"autocfg",
"hashbrown 0.12.3",
"serde",
]
[[package]]
name = "indexmap"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "2.4.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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "93ead53efc7ea8ed3cfb0c79fc8023fbb782a5432b52830b6518941cebe6505c"
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
dependencies = [
"equivalent",
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
"hashbrown 0.14.5",
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
"serde",
]
Add ability to override interpretations of roles (#660) This PR refactors the schema crate to enable overriding the interpretation of roles at runtime. By providing a `NamespacedGetter` that ignores roles entirely (i.e. `GDSNamespacedGetterAgnostic`) to schema generation functions it is possible to derive a GraphQL schema that ignores permissions and presets. This PR leaves back a few opportunities to improve code clarity, which I hope to address in follow-up PRs. For instance, it seems superfluous to make sense for generic code parametrised `<S: SchemaContext>` to carry around both a `S::Namespace` and a `S::NamespaceGetter`, when all that code could ever do with that `S::Namespace` value anyway is apply it to the `S::NamespaceGetter`. Taking this line of reasoning to its conclusion suggests that we can reduce the complexity of `trait SchemaContext` and its associated types and kit. --------- Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: c84555fd88279582670919faa5a62bbd00b714bd
2024-06-04 16:03:44 +03:00
[[package]]
name = "insta"
version = "1.39.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "810ae6042d48e2c9e9215043563a58a80b877bc863228a74cf10c49d4620a6f5"
dependencies = [
"console",
Take snapshots of passing and failing metadata resolution. (#763) ### What In order to more easily monitor and review changes to metadata resolution, this introduces snapshot testing for both successful and failing calls to `resolve`. I used [Insta](https://insta.rs/) for this. ### How For tests of the failure case, we already had a text file with the expected error, so I have turned those files into snapshot files. I wrote a small script to move the files rather than deleting and recreating them so I could guarantee that the contents have not changed. (Unfortunately, Git's diff doesn't always recognise the move as a move because Insta has added a header.) For tests of the successful case, I added a line to snapshot the metadata rather than discarding it. I also rewrote the tests to use `insta::glob` so we could get rid of `test_each`. V3_GIT_ORIGIN_REV_ID: 41bef4cf77bddb8d20d7c101df52ae149e8b0476
2024-06-26 11:14:34 +03:00
"globset",
Add ability to override interpretations of roles (#660) This PR refactors the schema crate to enable overriding the interpretation of roles at runtime. By providing a `NamespacedGetter` that ignores roles entirely (i.e. `GDSNamespacedGetterAgnostic`) to schema generation functions it is possible to derive a GraphQL schema that ignores permissions and presets. This PR leaves back a few opportunities to improve code clarity, which I hope to address in follow-up PRs. For instance, it seems superfluous to make sense for generic code parametrised `<S: SchemaContext>` to carry around both a `S::Namespace` and a `S::NamespaceGetter`, when all that code could ever do with that `S::Namespace` value anyway is apply it to the `S::NamespaceGetter`. Taking this line of reasoning to its conclusion suggests that we can reduce the complexity of `trait SchemaContext` and its associated types and kit. --------- Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: c84555fd88279582670919faa5a62bbd00b714bd
2024-06-04 16:03:44 +03:00
"lazy_static",
"linked-hash-map",
"similar",
Take snapshots of passing and failing metadata resolution. (#763) ### What In order to more easily monitor and review changes to metadata resolution, this introduces snapshot testing for both successful and failing calls to `resolve`. I used [Insta](https://insta.rs/) for this. ### How For tests of the failure case, we already had a text file with the expected error, so I have turned those files into snapshot files. I wrote a small script to move the files rather than deleting and recreating them so I could guarantee that the contents have not changed. (Unfortunately, Git's diff doesn't always recognise the move as a move because Insta has added a header.) For tests of the successful case, I added a line to snapshot the metadata rather than discarding it. I also rewrote the tests to use `insta::glob` so we could get rid of `test_each`. V3_GIT_ORIGIN_REV_ID: 41bef4cf77bddb8d20d7c101df52ae149e8b0476
2024-06-26 11:14:34 +03:00
"walkdir",
Add ability to override interpretations of roles (#660) This PR refactors the schema crate to enable overriding the interpretation of roles at runtime. By providing a `NamespacedGetter` that ignores roles entirely (i.e. `GDSNamespacedGetterAgnostic`) to schema generation functions it is possible to derive a GraphQL schema that ignores permissions and presets. This PR leaves back a few opportunities to improve code clarity, which I hope to address in follow-up PRs. For instance, it seems superfluous to make sense for generic code parametrised `<S: SchemaContext>` to carry around both a `S::Namespace` and a `S::NamespaceGetter`, when all that code could ever do with that `S::Namespace` value anyway is apply it to the `S::NamespaceGetter`. Taking this line of reasoning to its conclusion suggests that we can reduce the complexity of `trait SchemaContext` and its associated types and kit. --------- Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: c84555fd88279582670919faa5a62bbd00b714bd
2024-06-04 16:03:44 +03:00
]
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
[[package]]
name = "instant"
version = "0.1.13"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e0242819d153cba4b4b05a5a8f2a7e9bbf97b6055b2a002b395c96b5ff3c0222"
dependencies = [
"cfg-if",
"js-sys",
"wasm-bindgen",
"web-sys",
]
[[package]]
name = "integer-encoding"
version = "3.0.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8bb03732005da905c88227371639bf1ad885cc712789c011c31c5fb3ab3ccf02"
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
[[package]]
name = "ipnet"
version = "2.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8f518f335dce6725a761382244631d86cf0ccb2863413590b31338feb467f9c3"
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
[[package]]
name = "ir"
Use v3.0.0 as the version number. (#999) ### What Updates the version number to `3.0.0`, now we're officially at GA. ### How I updated the version number, and also updated some dependencies. The `Cargo.lock` file was not up to date. V3_GIT_ORIGIN_REV_ID: 3e9b784c8ad856556193e56aee9fa607fa8ce19e
2024-08-21 17:02:43 +03:00
version = "3.0.0"
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
dependencies = [
"base64 0.22.1",
"derive_more",
"hasura-authn-core",
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"indexmap 2.4.0",
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
"json-ext",
"lang-graphql",
"metadata-resolve",
"ndc-models 0.2.0",
"nonempty",
"open-dds",
"reqwest",
"schema",
"schemars",
"serde",
"serde_json",
"smol_str",
"thiserror",
"tracing-util",
"transitive",
]
Bump Criterion lib (#504) <!-- Thank you for submitting this PR! :) --> ## Description Benchmarks are running pretty slowly in Github, let's check it's not an old library version problem. --------- Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: db1a70c5465cf475fa66d2afc981fd496eccacaa
2024-04-24 18:52:47 +03:00
[[package]]
name = "is-terminal"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.4.13"
Bump Criterion lib (#504) <!-- Thank you for submitting this PR! :) --> ## Description Benchmarks are running pretty slowly in Github, let's check it's not an old library version problem. --------- Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: db1a70c5465cf475fa66d2afc981fd496eccacaa
2024-04-24 18:52:47 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "261f68e344040fbd0edea105bef17c66edf46f984ddb1115b775ce31be948f4b"
Bump Criterion lib (#504) <!-- Thank you for submitting this PR! :) --> ## Description Benchmarks are running pretty slowly in Github, let's check it's not an old library version problem. --------- Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: db1a70c5465cf475fa66d2afc981fd496eccacaa
2024-04-24 18:52:47 +03:00
dependencies = [
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"hermit-abi 0.4.0",
Bump Criterion lib (#504) <!-- Thank you for submitting this PR! :) --> ## Description Benchmarks are running pretty slowly in Github, let's check it's not an old library version problem. --------- Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: db1a70c5465cf475fa66d2afc981fd496eccacaa
2024-04-24 18:52:47 +03:00
"libc",
"windows-sys 0.52.0",
]
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
[[package]]
name = "is_terminal_polyfill"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "1.70.1"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "7943c866cc5cd64cbc25b2e01621d07fa8eb2a1a23160ee81ce38704e97b8ecf"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
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
[[package]]
name = "itertools"
version = "0.10.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b0fd2260e829bddf4cb6ea802289de2f86d6a7a690192fbe91b3f46e0f2c8473"
dependencies = [
"either",
]
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
[[package]]
name = "itertools"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.12.1"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "ba291022dbbd398a455acf126c1e341954079855bc60dfdda641363bd6922569"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
dependencies = [
"either",
]
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
[[package]]
name = "itertools"
version = "0.13.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "413ee7dfc52ee1a4949ceeb7dbc8a33f2d6c088194d9f922fb8318faf1f01186"
dependencies = [
"either",
]
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
[[package]]
name = "itoa"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "1.0.11"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "49f1f14873335454500d59611f1cf4a4b0f786f9ac11f4312a78e4cf2566695b"
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
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
[[package]]
name = "jobserver"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.1.32"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "48d1dbcbbeb6a7fec7e059840aa538bd62aaccf972c7346c4d9d2059312853d0"
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
dependencies = [
"libc",
]
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
[[package]]
name = "js-sys"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.3.70"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "1868808506b929d7b0cfa8f75951347aa71bb21144b7791bae35d9bccfcfe37a"
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
dependencies = [
"wasm-bindgen",
]
Move utils into `json_ext` crate (#555) <!-- Thank you for submitting this PR! :) --> ## Description We'd like to split the engine into smaller crates where possible, to enforce boundaries better. The next step is splitting `schema`, but it uses things in `engine/utils`. This splits those utils into a `json_ext` package, as they all seem like JSON helpers. Functional no-op. V3_GIT_ORIGIN_REV_ID: 44d93a7346dc83194abaa46158be2b8401905bd0
2024-05-07 15:45:49 +03:00
[[package]]
name = "json-ext"
Use v3.0.0 as the version number. (#999) ### What Updates the version number to `3.0.0`, now we're officially at GA. ### How I updated the version number, and also updated some dependencies. The `Cargo.lock` file was not up to date. V3_GIT_ORIGIN_REV_ID: 3e9b784c8ad856556193e56aee9fa607fa8ce19e
2024-08-21 17:02:43 +03:00
version = "3.0.0"
Move utils into `json_ext` crate (#555) <!-- Thank you for submitting this PR! :) --> ## Description We'd like to split the engine into smaller crates where possible, to enforce boundaries better. The next step is splitting `schema`, but it uses things in `engine/utils`. This splits those utils into a `json_ext` package, as they all seem like JSON helpers. Functional no-op. V3_GIT_ORIGIN_REV_ID: 44d93a7346dc83194abaa46158be2b8401905bd0
2024-05-07 15:45:49 +03:00
dependencies = [
"serde",
"serde_json",
]
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
[[package]]
name = "json_value_merge"
version = "2.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2b0a3aadd8aaadfe2be6fd22bbdb5dbc63494ce22b7c124211f684fd757b3215"
dependencies = [
"serde_json",
]
[[package]]
name = "jsonptr"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.4.7"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "1c6e529149475ca0b2820835d3dce8fcc41c6b943ca608d32f35b449255e4627"
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
dependencies = [
"fluent-uri",
"serde",
"serde_json",
]
Remove duplicate JSON Schema entries (#692) <!-- Thank you for submitting this PR! :) --> ## Description When we generate a JSON schema via `schemars`, we end up with duplicate types in the schema, which get names like `ValueExpression2`, `Role2`, and so on. This isn't ideal, and seems to arise for two reasons: 1. The type is polymorphic, and is monomorphised in two ways, and thus the types can't be unified. 2. The type is monomorphic, but is used inside and outside of its home module. The first problem was fixed previously by splitting polymorphic types, but the second has proven to be a bit more work. This PR finally solves the problem by introducing a new library, `jsonschema-tidying`: * First, we search the definitions within the JSON schema for any whose names end in a number, such as `ValueExpression2` or `MetadataV2`. * Then, we look for types whose names match everything up to the final numeric digits, and discard any types for whom we can't find a match (so we keep `ValueExpression2` because `ValueExpression` exists, but discard `MetadataV2` because `MetadataV` does not). * Next, we remove the duplicate definition from the definitions map, potentially breaking links in both the schema _and_ the rest of the definitions map. * Finally, we traverse the entirety of the tree looking for any references to the duplicate entry, and replace them with references to the original entry. This PR has no direct user-facing change, however it _will_ have an effect on the docs generation code, which will hopefully result in tidier documentation. <!-- Questions to consider answering: 1. What user-facing changes are being made? 4. What are issues related to this PR? (Consider adding `(close #<issue-no>)` to the PR title) 5. What is the conceptual design behind this PR? 6. How can this PR be tested/verified? 7. Does the PR have limitations? 8. Does the PR introduce breaking changes? --> ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [ ] community-edition - [ ] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [x] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> _Replace with changelog entry_ <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: fe73acf7d9df0b9867852e673e53cb086e3725d3
2024-06-11 11:27:42 +03:00
[[package]]
name = "jsonschema-tidying"
Use v3.0.0 as the version number. (#999) ### What Updates the version number to `3.0.0`, now we're officially at GA. ### How I updated the version number, and also updated some dependencies. The `Cargo.lock` file was not up to date. V3_GIT_ORIGIN_REV_ID: 3e9b784c8ad856556193e56aee9fa607fa8ce19e
2024-08-21 17:02:43 +03:00
version = "3.0.0"
Remove duplicate JSON Schema entries (#692) <!-- Thank you for submitting this PR! :) --> ## Description When we generate a JSON schema via `schemars`, we end up with duplicate types in the schema, which get names like `ValueExpression2`, `Role2`, and so on. This isn't ideal, and seems to arise for two reasons: 1. The type is polymorphic, and is monomorphised in two ways, and thus the types can't be unified. 2. The type is monomorphic, but is used inside and outside of its home module. The first problem was fixed previously by splitting polymorphic types, but the second has proven to be a bit more work. This PR finally solves the problem by introducing a new library, `jsonschema-tidying`: * First, we search the definitions within the JSON schema for any whose names end in a number, such as `ValueExpression2` or `MetadataV2`. * Then, we look for types whose names match everything up to the final numeric digits, and discard any types for whom we can't find a match (so we keep `ValueExpression2` because `ValueExpression` exists, but discard `MetadataV2` because `MetadataV` does not). * Next, we remove the duplicate definition from the definitions map, potentially breaking links in both the schema _and_ the rest of the definitions map. * Finally, we traverse the entirety of the tree looking for any references to the duplicate entry, and replace them with references to the original entry. This PR has no direct user-facing change, however it _will_ have an effect on the docs generation code, which will hopefully result in tidier documentation. <!-- Questions to consider answering: 1. What user-facing changes are being made? 4. What are issues related to this PR? (Consider adding `(close #<issue-no>)` to the PR title) 5. What is the conceptual design behind this PR? 6. How can this PR be tested/verified? 7. Does the PR have limitations? 8. Does the PR introduce breaking changes? --> ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [ ] community-edition - [ ] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [x] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> _Replace with changelog entry_ <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: fe73acf7d9df0b9867852e673e53cb086e3725d3
2024-06-11 11:27:42 +03:00
dependencies = [
"regex",
"schemars",
]
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
[[package]]
name = "jsonwebkey"
version = "0.3.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c57c852b14147e2bd58c14fde40398864453403ef632b1101db130282ee6e2cc"
dependencies = [
"base64 0.13.1",
"bitflags 1.3.2",
"generic-array",
"jsonwebtoken",
"num-bigint",
"p256",
"rand",
"serde",
"serde_json",
"thiserror",
"yasna",
"zeroize",
]
[[package]]
name = "jsonwebtoken"
version = "8.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6971da4d9c3aa03c3d8f3ff0f4155b534aad021292003895a469716b2a230378"
dependencies = [
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
"base64 0.21.7",
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
"pem",
"ring",
"serde",
"serde_json",
"simple_asn1",
]
[[package]]
name = "lang-graphql"
Use v3.0.0 as the version number. (#999) ### What Updates the version number to `3.0.0`, now we're officially at GA. ### How I updated the version number, and also updated some dependencies. The `Cargo.lock` file was not up to date. V3_GIT_ORIGIN_REV_ID: 3e9b784c8ad856556193e56aee9fa607fa8ce19e
2024-08-21 17:02:43 +03:00
version = "3.0.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
dependencies = [
Avoid returning a `Result` when it is unnecessary. (#726) Return a `T` instead of a `Result<T, E>` when we never return an error (`E`) case. I also enabled some more warnings. `unnecessary_box_returns` has been suppressed where appropriate, and `unused_async` doesn't seem to be violated anywhere any more. I got rid of some calls to `.unwrap()` too. V3_GIT_ORIGIN_REV_ID: 015ebd05978cf8c2d87474a90e0cd4333779a761
2024-06-18 15:02:18 +03:00
"anyhow",
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
"apollo-parser",
"async-graphql-parser",
"axum",
"bincode",
"bson",
"criterion",
"diffy",
lang-graphql: add parser tests (#290) Co-authored-by: Abhinav Gupta <127770473+abhinav-hasura@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d7b70a3cc70e6b9ead5867fd4b4fc56809878ebd
2024-01-30 20:41:48 +03:00
"expect-test",
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
"graphql-parser",
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
"http",
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
"human_bytes",
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"indexmap 2.4.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
"lexical-core",
"nonempty",
"postcard",
"pretty_assertions",
lang-graphql: limit recursion to avoid stack overflows This was a simple solution to prevent crashes from the cases that I was able to discover, refactored into a macro that can be used elsewhere; but I suspect there's a more idiomatic rust solution (entailing a big refactor?). There's also the stacker crate, and see also discussion here: https://hasurahq.slack.com/archives/C04PUMV4X16/p1707337409839869?thread_ts=1701302324.058369&cid=C04PUMV4X16 Note that the compiled binary was built and fuzzed with `--release`. Many discovered cases caused crashes when run into non-optimized binary (probably stack overflows but I did not look into it) V3_GIT_ORIGIN_REV_ID: 31acfc9e358c807be80ba6a5efa78ace78306291
2024-02-13 23:27:48 +03:00
"recursion_limit_macro",
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
"rmp-serde",
"schemars",
"serde",
"serde_json",
upgrade to ndc v0.1.3 (#629) Upgrade engine to ndc v0.1.3. Also updates custom connector. --------- Co-authored-by: Samir Talwar <samir.talwar@hasura.io> Co-authored-by: Gil Mizrahi <gil@hasura.io> V3_GIT_ORIGIN_REV_ID: 80959d4702ef785b7809d6432e092b6477ef88c1
2024-06-05 13:15:25 +03:00
"serde_with",
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
"smol_str",
"thiserror",
]
[[package]]
name = "lazy_static"
Bump lazy_static from 1.4.0 to 1.5.0 (#744) V3_GIT_ORIGIN_REV_ID: 87e1467dbc477b2a9a1d2980484a3fb9082502ec
2024-06-24 10:53:08 +03:00
version = "1.5.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
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump lazy_static from 1.4.0 to 1.5.0 (#744) V3_GIT_ORIGIN_REV_ID: 87e1467dbc477b2a9a1d2980484a3fb9082502ec
2024-06-24 10:53:08 +03:00
checksum = "bbd2bcb4c963f2ddae06a2efc7e9f3591312473c50c6685e1f298068316e66fe"
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
[[package]]
name = "lexical-core"
version = "0.8.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2cde5de06e8d4c2faabc400238f9ae1c74d5412d03a7bd067645ccbc47070e46"
dependencies = [
"lexical-parse-float",
"lexical-parse-integer",
"lexical-util",
"lexical-write-float",
"lexical-write-integer",
]
[[package]]
name = "lexical-parse-float"
version = "0.8.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "683b3a5ebd0130b8fb52ba0bdc718cc56815b6a097e28ae5a6997d0ad17dc05f"
dependencies = [
"lexical-parse-integer",
"lexical-util",
"static_assertions",
]
[[package]]
name = "lexical-parse-integer"
version = "0.8.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6d0994485ed0c312f6d965766754ea177d07f9c00c9b82a5ee62ed5b47945ee9"
dependencies = [
"lexical-util",
"static_assertions",
]
[[package]]
name = "lexical-util"
version = "0.8.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5255b9ff16ff898710eb9eb63cb39248ea8a5bb036bea8085b1a767ff6c4e3fc"
dependencies = [
"static_assertions",
]
[[package]]
name = "lexical-write-float"
version = "0.8.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "accabaa1c4581f05a3923d1b4cfd124c329352288b7b9da09e766b0668116862"
dependencies = [
"lexical-util",
"lexical-write-integer",
"static_assertions",
]
[[package]]
name = "lexical-write-integer"
version = "0.8.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e1b6f3d1f4422866b68192d62f77bc5c700bee84f3069f2469d7bc8c77852446"
dependencies = [
"lexical-util",
"static_assertions",
]
[[package]]
name = "libc"
Update to Rust v1.80.1. (#1002) ### What Upgrade to the latest version of Rust. ### How I modified `rust-toolchain.toml` and ran `cargo update`. V3_GIT_ORIGIN_REV_ID: 5fe675ee5dc568cd24de542c826ffd2d355f90ff
2024-08-22 11:08:47 +03:00
version = "0.2.158"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update to Rust v1.80.1. (#1002) ### What Upgrade to the latest version of Rust. ### How I modified `rust-toolchain.toml` and ran `cargo update`. V3_GIT_ORIGIN_REV_ID: 5fe675ee5dc568cd24de542c826ffd2d355f90ff
2024-08-22 11:08:47 +03:00
checksum = "d8adc4bb1803a324070e64a98ae98f38934d91957a99cfb3a43dcbc01bc56439"
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
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
[[package]]
name = "libm"
version = "0.2.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4ec2a862134d2a7d32d7983ddcdd1c4923530833c9f2ea1a44fc5fa473989058"
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
[[package]]
name = "libmimalloc-sys"
version = "0.1.39"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "23aa6811d3bd4deb8a84dde645f943476d13b248d818edcf8ce0b2f37f036b44"
dependencies = [
"cc",
"libc",
]
Add ability to override interpretations of roles (#660) This PR refactors the schema crate to enable overriding the interpretation of roles at runtime. By providing a `NamespacedGetter` that ignores roles entirely (i.e. `GDSNamespacedGetterAgnostic`) to schema generation functions it is possible to derive a GraphQL schema that ignores permissions and presets. This PR leaves back a few opportunities to improve code clarity, which I hope to address in follow-up PRs. For instance, it seems superfluous to make sense for generic code parametrised `<S: SchemaContext>` to carry around both a `S::Namespace` and a `S::NamespaceGetter`, when all that code could ever do with that `S::Namespace` value anyway is apply it to the `S::NamespaceGetter`. Taking this line of reasoning to its conclusion suggests that we can reduce the complexity of `trait SchemaContext` and its associated types and kit. --------- Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: c84555fd88279582670919faa5a62bbd00b714bd
2024-06-04 16:03:44 +03:00
[[package]]
name = "linked-hash-map"
version = "0.5.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0717cef1bc8b636c6e1c1bbdefc09e6322da8a9321966e8928ef80d20f7f770f"
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
[[package]]
name = "linux-raw-sys"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.4.14"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "78b3ae25bc7c8c38cec158d1f2757ee79e9b3740fbc7ccf0e59e4b08d793fa89"
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
[[package]]
name = "lock_api"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.4.12"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "07af8b9cdd281b7915f413fa73f29ebd5d55d0d3f0155584dade1ff18cea1b17"
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
dependencies = [
"autocfg",
"scopeguard",
]
[[package]]
name = "log"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.4.22"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "a7a70ba024b9dc04c27ea2f0c0548feb474ec5c54bba33a7f72f873a39d07b24"
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
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
[[package]]
name = "lz4_flex"
version = "0.11.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "75761162ae2b0e580d7e7c390558127e5f01b4194debd6221fd8c207fc80e3f5"
dependencies = [
"twox-hash",
]
[[package]]
name = "lzma-sys"
version = "0.1.20"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5fda04ab3764e6cde78b9974eec4f779acaba7c4e84b36eca3cf77c581b85d27"
dependencies = [
"cc",
"libc",
"pkg-config",
]
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
[[package]]
name = "matchit"
version = "0.7.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0e7465ac9959cc2b1404e8e2367b43684a6d13790fe23056cc8c6c5a6b7bcb94"
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
[[package]]
name = "md-5"
version = "0.10.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d89e7ee0cfbedfc4da3340218492196241d89eefb6dab27de5df917a6d2e78cf"
dependencies = [
"cfg-if",
"digest 0.10.7",
]
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
[[package]]
name = "memchr"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "2.7.4"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "78ca9ab1a0babb1e7d5695e3530886289c18cf2f87ec19a575a0abdce112e3a3"
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
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
[[package]]
name = "metadata-resolve"
Use v3.0.0 as the version number. (#999) ### What Updates the version number to `3.0.0`, now we're officially at GA. ### How I updated the version number, and also updated some dependencies. The `Cargo.lock` file was not up to date. V3_GIT_ORIGIN_REV_ID: 3e9b784c8ad856556193e56aee9fa607fa8ce19e
2024-08-21 17:02:43 +03:00
version = "3.0.0"
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
dependencies = [
Metadata resolve for OrderByExpression (#840) <!-- The PR description should answer 2 (maybe 3) important questions: --> ### What - Add metadata resolver for the new `OrderByExpression` metadata object kind. - When resolving a v1 `Model`, generate an `OrderByExpression` based on the model's `orderable_fields`. ### How `OrderByExpression` was added to OpenDD in https://github.com/hasura/v3-engine/pull/780. This PR adds metadata resolvers for this new metadata object kind. The OpenDD changes involved a new version v2 of `Model` where `orderableFields` was moved out of the out of the model definition. The model now references an `OrderByExpression` instead. To retain backwards compatibility with `Model` v1, the model metadata resolver now extracts the `orderableFields` from a v1 model and uses them to create a new `OrderByExpression` for internal use by the resolved metadata. V3_GIT_ORIGIN_REV_ID: a7dbafe860e586efdb2e03c23020a067011c57a1
2024-08-07 01:30:53 +03:00
"derive_more",
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
"hasura-authn-core",
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"indexmap 2.4.0",
Take snapshots of passing and failing metadata resolution. (#763) ### What In order to more easily monitor and review changes to metadata resolution, this introduces snapshot testing for both successful and failing calls to `resolve`. I used [Insta](https://insta.rs/) for this. ### How For tests of the failure case, we already had a text file with the expected error, so I have turned those files into snapshot files. I wrote a small script to move the files rather than deleting and recreating them so I could guarantee that the contents have not changed. (Unfortunately, Git's diff doesn't always recognise the move as a move because Insta has added a header.) For tests of the successful case, I added a line to snapshot the metadata rather than discarding it. I also rewrote the tests to use `insta::glob` so we could get rid of `test_each`. V3_GIT_ORIGIN_REV_ID: 41bef4cf77bddb8d20d7c101df52ae149e8b0476
2024-06-26 11:14:34 +03:00
"insta",
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
"lang-graphql",
Use ndc-models 0.1.6 (#1013) <!-- The PR description should answer 2 important questions: --> ### What Update `v3-engine` to use `ndc-models` 0.1.6. ### How Update in Cargo.toml, check everything builds. V3_GIT_ORIGIN_REV_ID: 64d8b5b8126f593c10ffa89ba21791f326aefedd
2024-08-26 16:46:12 +03:00
"ndc-models 0.1.6",
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 0.2.0",
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
"nonempty",
"open-dds",
use a newtype for data connector object type (#542) ## Description Introduce a newtype for data connector object type for the added context. V3_GIT_ORIGIN_REV_ID: b499d3a9cd2610fec05a4bc2e1b3cf522f198b9c
2024-05-03 12:32:28 +03:00
"ref-cast",
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
"reqwest",
Improvements to query usage analytics data shape (#715) This PR introduces the following changes to query usage analytics data shape: - The `name` field in `RelationshipUsage` is just `RelationshipName` without `Qualified` wrapper. The `source` is already qualified, and the same qualification applies to `name`. - The `used` for both field and input field is a list. A field can use multiple opendd objects at a time. - Example: A root field can use `Model` and `Permission` (with both filter and argument presets). - The permission usage now revamped to express available permissions in the opendd - Filter predicate - provides lists of fields and relationships - Field presets - provides a list of fields involved - Argument presets - provides a list of arguments involved - The `GqlFieldArgument` is dropped in favor of `GqlInputField`. - Opendd object usage is not specified for `GqlFieldArgument`. An input argument with object type can have field presets permission. It is replaced with `GqlInputField` to allow specifying the permission usage. This PR also includes JSON schema for the data shape with a golden test to verify. V3_GIT_ORIGIN_REV_ID: f0bf9ba201471af367ef5027bc2c8b9f915994ac
2024-06-25 10:56:31 +03:00
"schemars",
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",
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
"serde",
"serde_json",
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
"strum",
"strum_macros",
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
"thiserror",
"url",
]
Add a binary for generating the OpenAPI schema for the metadata type. (#453) <!-- Thank you for submitting this PR! :) --> ## Description I needed this, so I made it. It's nothing too complex: we just pretty-print the `schemars` schema for the root `Metadata` type. <!-- Questions to consider answering: 1. What user-facing changes are being made? 2. What are issues related to this PR? (Consider adding `(close #<issue-no>)` to the PR title) 3. What is the conceptual design behind this PR? 4. How can this PR be tested/verified? 5. Does the PR have limitations? 6. Does the PR introduce breaking changes? --> ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [ ] community-edition - [ ] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [ ] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> _Replace with changelog entry_ <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: a9e75bfa06c35577c17d8cbf0d021b1f56826a28
2024-04-10 10:35:59 +03:00
[[package]]
name = "metadata-schema-generator"
Use v3.0.0 as the version number. (#999) ### What Updates the version number to `3.0.0`, now we're officially at GA. ### How I updated the version number, and also updated some dependencies. The `Cargo.lock` file was not up to date. V3_GIT_ORIGIN_REV_ID: 3e9b784c8ad856556193e56aee9fa607fa8ce19e
2024-08-21 17:02:43 +03:00
version = "3.0.0"
Add a binary for generating the OpenAPI schema for the metadata type. (#453) <!-- Thank you for submitting this PR! :) --> ## Description I needed this, so I made it. It's nothing too complex: we just pretty-print the `schemars` schema for the root `Metadata` type. <!-- Questions to consider answering: 1. What user-facing changes are being made? 2. What are issues related to this PR? (Consider adding `(close #<issue-no>)` to the PR title) 3. What is the conceptual design behind this PR? 4. How can this PR be tested/verified? 5. Does the PR have limitations? 6. Does the PR introduce breaking changes? --> ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [ ] community-edition - [ ] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [ ] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> _Replace with changelog entry_ <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: a9e75bfa06c35577c17d8cbf0d021b1f56826a28
2024-04-10 10:35:59 +03:00
dependencies = [
"open-dds",
"schemars",
"serde_json",
]
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
[[package]]
name = "mimalloc"
version = "0.1.43"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "68914350ae34959d83f732418d51e2427a794055d0b9529f48259ac07af65633"
dependencies = [
"libmimalloc-sys",
]
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
[[package]]
name = "mime"
version = "0.3.17"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6877bb514081ee2a7ff5ef9de3281f14a4dd4bceac4c09388074a6b5df8a139a"
[[package]]
name = "mime_guess"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "2.0.5"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "f7c44f8e672c00fe5308fa235f821cb4198414e1c77935c1ab6948d3fd78550e"
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
dependencies = [
"mime",
"unicase",
]
[[package]]
name = "miniz_oxide"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.7.4"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "b8a240ddb74feaf34a79a7add65a741f3167852fba007066dcac1ca548d89c08"
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
dependencies = [
"adler",
]
Update to Rust v1.80.1. (#1002) ### What Upgrade to the latest version of Rust. ### How I modified `rust-toolchain.toml` and ran `cargo update`. V3_GIT_ORIGIN_REV_ID: 5fe675ee5dc568cd24de542c826ffd2d355f90ff
2024-08-22 11:08:47 +03:00
[[package]]
name = "miniz_oxide"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e2d80299ef12ff69b16a84bb182e3b9df68b5a91574d3d4fa6e41b65deec4df1"
dependencies = [
"adler2",
]
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
[[package]]
name = "mio"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "1.0.2"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "80e04d1dcff3aae0704555fe5fee3bcfaf3d1fdf8a7e521d5b9d2b42acb52cec"
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
dependencies = [
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"hermit-abi 0.3.9",
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
"libc",
"wasi",
Bump tokio from 1.38.1 to 1.39.2 (#897) Bumps [tokio](https://github.com/tokio-rs/tokio) from 1.38.1 to 1.39.2. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/tokio-rs/tokio/releases">tokio's releases</a>.</em></p> <blockquote> <h2>Tokio v1.39.2</h2> <h1>1.39.2 (July 27th, 2024)</h1> <p>This release fixes a regression where the <code>select!</code> macro stopped accepting expressions that make use of temporary lifetime extension. (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6722">#6722</a>)</p> <p><a href="https://redirect.github.com/tokio-rs/tokio/issues/6722">#6722</a>: <a href="https://redirect.github.com/tokio-rs/tokio/pull/6722">tokio-rs/tokio#6722</a></p> <h2>Tokio v1.39.1</h2> <h1>1.39.1 (July 23rd, 2024)</h1> <p>This release reverts &quot;time: avoid traversing entries in the time wheel twice&quot; because it contains a bug. (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6715">#6715</a>)</p> <p><a href="https://redirect.github.com/tokio-rs/tokio/issues/6715">#6715</a>: <a href="https://redirect.github.com/tokio-rs/tokio/pull/6715">tokio-rs/tokio#6715</a></p> <h2>Tokio v1.39.0</h2> <h1>1.39.0 (July 23rd, 2024)</h1> <ul> <li>This release bumps the MSRV to 1.70. (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6645">#6645</a>)</li> <li>This release upgrades to mio v1. (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6635">#6635</a>)</li> <li>This release upgrades to windows-sys v0.52 (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6154">#6154</a>)</li> </ul> <h3>Added</h3> <ul> <li>io: implement <code>AsyncSeek</code> for <code>Empty</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6663">#6663</a>)</li> <li>metrics: stabilize <code>num_alive_tasks</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6619">#6619</a>, <a href="https://redirect.github.com/tokio-rs/tokio/issues/6667">#6667</a>)</li> <li>process: add <code>Command::as_std_mut</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6608">#6608</a>)</li> <li>sync: add <code>watch::Sender::same_channel</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6637">#6637</a>)</li> <li>sync: add <code>{Receiver,UnboundedReceiver}::{sender_strong_count,sender_weak_count}</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6661">#6661</a>)</li> <li>sync: implement <code>Default</code> for <code>watch::Sender</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6626">#6626</a>)</li> <li>task: implement <code>Clone</code> for <code>AbortHandle</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6621">#6621</a>)</li> <li>task: stabilize <code>consume_budget</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6622">#6622</a>)</li> </ul> <h3>Changed</h3> <ul> <li>io: improve panic message of <code>ReadBuf::put_slice()</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6629">#6629</a>)</li> <li>io: read during write in <code>copy_bidirectional</code> and <code>copy</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6532">#6532</a>)</li> <li>runtime: replace <code>num_cpus</code> with <code>available_parallelism</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6709">#6709</a>)</li> <li>task: avoid stack overflow when passing large future to <code>block_on</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6692">#6692</a>)</li> <li>time: avoid traversing entries in the time wheel twice (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6584">#6584</a>)</li> <li>time: support <code>IntoFuture</code> with <code>timeout</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6666">#6666</a>)</li> <li>macros: support <code>IntoFuture</code> with <code>join!</code> and <code>select!</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6710">#6710</a>)</li> </ul> <h3>Fixed</h3> <ul> <li>docs: fix docsrs builds with the fs feature enabled (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6585">#6585</a>)</li> <li>io: only use short-read optimization on known-to-be-compatible platforms (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6668">#6668</a>)</li> <li>time: fix overflow panic when using large durations with <code>Interval</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6612">#6612</a>)</li> </ul> <h3>Added (unstable)</h3> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/tokio-rs/tokio/commit/f602eae49988dbad2a11fd83e6b3fbd4f094713c"><code>f602eae</code></a> chore: prepare Tokio v1.39.2 (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6730">#6730</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/438def79579a7e285beb5f0d93b1eb6a9f8062b3"><code>438def7</code></a> macros: allow temporary lifetime extension in select (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6722">#6722</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/ee8d4d1b0546c67198af3cd053d6b7b8b4fd26c3"><code>ee8d4d1</code></a> chore: fix ci failures (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6725">#6725</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/32970527633bb72fc4f01d02523484a9376ac26a"><code>3297052</code></a> ci: test Quinn in CI (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6719">#6719</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/f8fe0ffb23c2279708cb5dada7c88defdae60845"><code>f8fe0ff</code></a> chore: prepare Tokio v1.39.1 (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6716">#6716</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/47210a8e6eeb82b51aa778074fdc4d757b953b8c"><code>47210a8</code></a> time: revert &quot;avoid traversing entries in the time wheel twice&quot; (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6715">#6715</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/29545d90370d925a7264ff8636013ee6bf1760e6"><code>29545d9</code></a> runtime: ignore many_oneshot_futures test for alt scheduler (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6712">#6712</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/48e35c11d924ffa3a009b89fbb6d36e57b835da4"><code>48e35c1</code></a> chore: release Tokio v1.39.0 (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6711">#6711</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/dd1d37167d1f4008ca5d3df500e86826112a8cad"><code>dd1d371</code></a> macros: accept <code>IntoFuture</code> args for macros (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6710">#6710</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/6a1a7b15912d1a86ab4c0d09e1a8f0a221dbfeee"><code>6a1a7b1</code></a> chore: prepare tokio-macros v2.4.0 (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6707">#6707</a>)</li> <li>Additional commits viewable in <a href="https://github.com/tokio-rs/tokio/compare/tokio-1.38.1...tokio-1.39.2">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=tokio&package-manager=cargo&previous-version=1.38.1&new-version=1.39.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: 0cb6c24bedcd6553e8936334df936f49023b8308
2024-07-29 13:07:48 +03:00
"windows-sys 0.52.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
]
[[package]]
name = "mockito"
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
version = "1.4.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
source = "registry+https://github.com/rust-lang/crates.io-index"
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
checksum = "d2f6e023aa5bdf392aa06c78e4a4e6d498baab5138d0c993503350ebbc37bf1e"
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
dependencies = [
"assert-json-diff",
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
"futures-core",
"hyper",
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
"log",
"rand",
"regex",
"serde_json",
"serde_urlencoded",
"similar",
"tokio",
]
[[package]]
name = "native-tls"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.2.12"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "a8614eb2c83d59d1c8cc974dd3f920198647674a0a035e1af1fa58707e317466"
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
dependencies = [
"libc",
"log",
"openssl",
"openssl-probe",
"openssl-sys",
"schannel",
"security-framework",
"security-framework-sys",
"tempfile",
]
[[package]]
Update to ndc-spec-0.1.2 (#443) <!-- Thank you for submitting this PR! :) --> ## Description - Update to `ndc-spec`-`0.1.2` - Use `ndc_models` since `ndc_client` was removed - Use `Int32` in `custom_connector` everywhere <!-- Questions to consider answering: 1. What user-facing changes are being made? 2. What are issues related to this PR? (Consider adding `(close #<issue-no>)` to the PR title) 3. What is the conceptual design behind this PR? 4. How can this PR be tested/verified? 5. Does the PR have limitations? 6. Does the PR introduce breaking changes? --> V3_GIT_ORIGIN_REV_ID: 00c6e7a6c213ab0de31303a93f8446c1d371c538
2024-04-05 12:35:01 +03:00
name = "ndc-models"
Use ndc-models 0.1.6 (#1013) <!-- The PR description should answer 2 important questions: --> ### What Update `v3-engine` to use `ndc-models` 0.1.6. ### How Update in Cargo.toml, check everything builds. V3_GIT_ORIGIN_REV_ID: 64d8b5b8126f593c10ffa89ba21791f326aefedd
2024-08-26 16:46:12 +03:00
version = "0.1.6"
source = "git+https://github.com/hasura/ndc-spec.git?tag=v0.1.6#d1be19e9cdd86ac7b6ad003ff82b7e5b4e96b84f"
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
dependencies = [
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"indexmap 2.4.0",
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
"ref-cast",
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
"schemars",
"serde",
"serde_json",
upgrade to ndc v0.1.3 (#629) Upgrade engine to ndc v0.1.3. Also updates custom connector. --------- Co-authored-by: Samir Talwar <samir.talwar@hasura.io> Co-authored-by: Gil Mizrahi <gil@hasura.io> V3_GIT_ORIGIN_REV_ID: 80959d4702ef785b7809d6432e092b6477ef88c1
2024-06-05 13:15:25 +03:00
"serde_with",
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
"smol_str",
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
]
Add support for multiple versions of ndc-spec to Open DD and metadata-resolve (#781) This PR introduces support for multiple versions of the ndc-spec by adding a new `VersionedSchemaAndCapabilities` enum variant under the `DataConnectorLink` in OpenDD. This allows the capture of both ndc v0.1.* and v0.2.* schema and capabilities. This is achieved by referencing the `ndc-models` crate twice, once for `v0.1.4` and once for the first commit after `v0.1.4`. That commit was chosen to avoid actual v0.2.0 breaking changes for now, while we lay in this multiple version support plumbing. Future PRs will use a newer commit and adopt the breaking changes where necessary. The `VersionedSchemaAndCapabilities::V02` variant uses the the v0.2 reference of `ndc-models`. Then, during metadata resolve, when we resolve the `DataConnectorContext` from `DataConnectorLink`, we perform a migration of v0.1 types to v0.2 types and store and use the v0.2 types during metadata resolve. This migration is performed in the new module `ndc_migration`. We also record the `NdcVersion` (either `V01` or `V02`) in the `DataConnectorLink`. The `execute` crate will need to use this to determine which version to send to the connector at runtime (to be implemented in a future PR). The new changes to OpenDD are hidden from the JSON Schema via a new `UnstableFeatures` flag, and the use of the new variant is gated behind it in metadata resolve, since we don't yet support it upstream in the `execute` crate. V3_GIT_ORIGIN_REV_ID: d6d8a768ea3537c0b5e620799e94d3dd1e529526
2024-06-28 14:56:52 +03:00
[[package]]
name = "ndc-models"
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
version = "0.2.0"
source = "git+https://github.com/hasura/ndc-spec.git?tag=v0.2.0-rc.0#2893acd5de273667e84f9f87a25901615b368593"
Add support for multiple versions of ndc-spec to Open DD and metadata-resolve (#781) This PR introduces support for multiple versions of the ndc-spec by adding a new `VersionedSchemaAndCapabilities` enum variant under the `DataConnectorLink` in OpenDD. This allows the capture of both ndc v0.1.* and v0.2.* schema and capabilities. This is achieved by referencing the `ndc-models` crate twice, once for `v0.1.4` and once for the first commit after `v0.1.4`. That commit was chosen to avoid actual v0.2.0 breaking changes for now, while we lay in this multiple version support plumbing. Future PRs will use a newer commit and adopt the breaking changes where necessary. The `VersionedSchemaAndCapabilities::V02` variant uses the the v0.2 reference of `ndc-models`. Then, during metadata resolve, when we resolve the `DataConnectorContext` from `DataConnectorLink`, we perform a migration of v0.1 types to v0.2 types and store and use the v0.2 types during metadata resolve. This migration is performed in the new module `ndc_migration`. We also record the `NdcVersion` (either `V01` or `V02`) in the `DataConnectorLink`. The `execute` crate will need to use this to determine which version to send to the connector at runtime (to be implemented in a future PR). The new changes to OpenDD are hidden from the JSON Schema via a new `UnstableFeatures` flag, and the use of the new variant is gated behind it in metadata resolve, since we don't yet support it upstream in the `execute` crate. V3_GIT_ORIGIN_REV_ID: d6d8a768ea3537c0b5e620799e94d3dd1e529526
2024-06-28 14:56:52 +03:00
dependencies = [
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"indexmap 2.4.0",
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
"ref-cast",
Add support for multiple versions of ndc-spec to Open DD and metadata-resolve (#781) This PR introduces support for multiple versions of the ndc-spec by adding a new `VersionedSchemaAndCapabilities` enum variant under the `DataConnectorLink` in OpenDD. This allows the capture of both ndc v0.1.* and v0.2.* schema and capabilities. This is achieved by referencing the `ndc-models` crate twice, once for `v0.1.4` and once for the first commit after `v0.1.4`. That commit was chosen to avoid actual v0.2.0 breaking changes for now, while we lay in this multiple version support plumbing. Future PRs will use a newer commit and adopt the breaking changes where necessary. The `VersionedSchemaAndCapabilities::V02` variant uses the the v0.2 reference of `ndc-models`. Then, during metadata resolve, when we resolve the `DataConnectorContext` from `DataConnectorLink`, we perform a migration of v0.1 types to v0.2 types and store and use the v0.2 types during metadata resolve. This migration is performed in the new module `ndc_migration`. We also record the `NdcVersion` (either `V01` or `V02`) in the `DataConnectorLink`. The `execute` crate will need to use this to determine which version to send to the connector at runtime (to be implemented in a future PR). The new changes to OpenDD are hidden from the JSON Schema via a new `UnstableFeatures` flag, and the use of the new variant is gated behind it in metadata resolve, since we don't yet support it upstream in the `execute` crate. V3_GIT_ORIGIN_REV_ID: d6d8a768ea3537c0b5e620799e94d3dd1e529526
2024-06-28 14:56:52 +03:00
"schemars",
"serde",
"serde_json",
"serde_with",
Update ndc-models to latest version which includes new name newtypes (#791) This PR updated ndc-models to the latest version on main. This version is still a 0.1.x version, but it now includes all the [new newtypes](https://github.com/hasura/ndc-spec/pull/156) that wrap previously stringly-typed things. For example, `ArgumentName`, `FieldName`, etc. This pervades across the entire engine, but thankfully the changes are mostly mechanical repetitive changes. Usually you will see conversions from `String`-typed variables into the newtypes using this sort of form: `FieldName::from(string.as_str())`, which is the most efficient way copying the value (the str slice is copied). Or you will see usages of the newtype as a raw string by `.as_str()`-ing it. Converting the newtypes into a String can be done with `.into()` if owned, but if referenced `.as_str().to_owned()` performs the clone and type conversion. Other changes: * A few minor instances of `ok_or()` usages (or similar) have been converted into lazy error construction variants (eg `ok_or_else()`) V3_GIT_ORIGIN_REV_ID: 64a371ae6197ef3be98a6f7cdc4052d654a43da0
2024-07-04 11:57:06 +03:00
"smol_str",
Add support for multiple versions of ndc-spec to Open DD and metadata-resolve (#781) This PR introduces support for multiple versions of the ndc-spec by adding a new `VersionedSchemaAndCapabilities` enum variant under the `DataConnectorLink` in OpenDD. This allows the capture of both ndc v0.1.* and v0.2.* schema and capabilities. This is achieved by referencing the `ndc-models` crate twice, once for `v0.1.4` and once for the first commit after `v0.1.4`. That commit was chosen to avoid actual v0.2.0 breaking changes for now, while we lay in this multiple version support plumbing. Future PRs will use a newer commit and adopt the breaking changes where necessary. The `VersionedSchemaAndCapabilities::V02` variant uses the the v0.2 reference of `ndc-models`. Then, during metadata resolve, when we resolve the `DataConnectorContext` from `DataConnectorLink`, we perform a migration of v0.1 types to v0.2 types and store and use the v0.2 types during metadata resolve. This migration is performed in the new module `ndc_migration`. We also record the `NdcVersion` (either `V01` or `V02`) in the `DataConnectorLink`. The `execute` crate will need to use this to determine which version to send to the connector at runtime (to be implemented in a future PR). The new changes to OpenDD are hidden from the JSON Schema via a new `UnstableFeatures` flag, and the use of the new variant is gated behind it in metadata resolve, since we don't yet support it upstream in the `execute` crate. V3_GIT_ORIGIN_REV_ID: d6d8a768ea3537c0b5e620799e94d3dd1e529526
2024-06-28 14:56:52 +03:00
]
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
[[package]]
name = "nonempty"
Bump nonempty from 0.8.1 to 0.10.0 (#463) Bumps [nonempty](https://github.com/cloudhead/nonempty) from 0.8.1 to 0.10.0. <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/cloudhead/nonempty/commits">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=nonempty&package-manager=cargo&previous-version=0.8.1&new-version=0.10.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: 11c6454b5e7e9877b52075f0e0efe6839ecf3be1
2024-04-15 11:40:59 +03:00
version = "0.10.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
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump nonempty from 0.8.1 to 0.10.0 (#463) Bumps [nonempty](https://github.com/cloudhead/nonempty) from 0.8.1 to 0.10.0. <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/cloudhead/nonempty/commits">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=nonempty&package-manager=cargo&previous-version=0.8.1&new-version=0.10.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: 11c6454b5e7e9877b52075f0e0efe6839ecf3be1
2024-04-15 11:40:59 +03:00
checksum = "303e8749c804ccd6ca3b428de7fe0d86cb86bc7606bc15291f100fd487960bb8"
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
dependencies = [
"serde",
]
[[package]]
name = "nu-ansi-term"
version = "0.46.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "77a8165726e8236064dbb45459242600304b42a5ea24ee2948e18e023bf7ba84"
dependencies = [
"overload",
"winapi",
]
Bump diffy from 0.3.0 to 0.4.0 (#718) Bumps [diffy](https://github.com/bmwill/diffy) from 0.3.0 to 0.4.0. Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: a8d610058bfb0f0fd7af547882724457202c25f8
2024-06-17 08:29:16 +03:00
[[package]]
name = "nu-ansi-term"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.50.1"
Bump diffy from 0.3.0 to 0.4.0 (#718) Bumps [diffy](https://github.com/bmwill/diffy) from 0.3.0 to 0.4.0. Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: a8d610058bfb0f0fd7af547882724457202c25f8
2024-06-17 08:29:16 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "d4a28e057d01f97e61255210fcff094d74ed0466038633e95017f5beb68e4399"
Bump diffy from 0.3.0 to 0.4.0 (#718) Bumps [diffy](https://github.com/bmwill/diffy) from 0.3.0 to 0.4.0. Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: a8d610058bfb0f0fd7af547882724457202c25f8
2024-06-17 08:29:16 +03:00
dependencies = [
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"windows-sys 0.52.0",
Bump diffy from 0.3.0 to 0.4.0 (#718) Bumps [diffy](https://github.com/bmwill/diffy) from 0.3.0 to 0.4.0. Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: a8d610058bfb0f0fd7af547882724457202c25f8
2024-06-17 08:29:16 +03:00
]
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
[[package]]
name = "num"
version = "0.4.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "35bd024e8b2ff75562e5f34e7f4905839deb4b22955ef5e73d2fea1b9813cb23"
dependencies = [
"num-bigint",
"num-complex",
"num-integer",
"num-iter",
"num-rational",
"num-traits",
]
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
[[package]]
name = "num-bigint"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.4.6"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "a5e44f723f1133c9deac646763579fdb3ac745e418f2a7af9cd0c431da1f20b9"
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
dependencies = [
"num-integer",
"num-traits",
]
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
[[package]]
name = "num-complex"
version = "0.4.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "73f88a1307638156682bada9d7604135552957b7818057dcef22705b4d509495"
dependencies = [
"num-traits",
]
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
[[package]]
name = "num-conv"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "51d515d32fb182ee37cda2ccdcb92950d6a3c2893aa280e540671c2cd0f3b1d9"
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
[[package]]
name = "num-integer"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.1.46"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "7969661fd2958a5cb096e56c8e1ad0444ac2bbcd0061bd28660485a44879858f"
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
dependencies = [
"num-traits",
]
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
[[package]]
name = "num-iter"
version = "0.1.45"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1429034a0490724d0075ebb2bc9e875d6503c3cf69e235a8941aa757d83ef5bf"
dependencies = [
"autocfg",
"num-integer",
"num-traits",
]
[[package]]
name = "num-rational"
version = "0.4.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f83d14da390562dca69fc84082e73e548e1ad308d24accdedd2720017cb37824"
dependencies = [
"num-bigint",
"num-integer",
"num-traits",
]
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
[[package]]
name = "num-traits"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.2.19"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "071dfc062690e90b734c0b2273ce72ad0ffa95f0c74596bc250dcfd960262841"
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
dependencies = [
"autocfg",
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
"libm",
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
]
[[package]]
name = "num_cpus"
version = "1.16.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4161fcb6d602d4d2081af7c3a45852d875a03dd337a6bfdd6e06407b61342a43"
dependencies = [
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"hermit-abi 0.3.9",
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
"libc",
]
[[package]]
name = "object"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.36.3"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "27b64972346851a39438c60b341ebc01bba47464ae329e55cf343eb93964efd9"
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
dependencies = [
"memchr",
]
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
[[package]]
name = "object_store"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
version = "0.10.2"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
checksum = "e6da452820c715ce78221e8202ccc599b4a52f3e1eb3eedb487b680c81a8e3f3"
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
dependencies = [
"async-trait",
"bytes",
"chrono",
"futures",
"humantime",
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
"itertools 0.13.0",
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
"parking_lot",
"percent-encoding",
"snafu",
"tokio",
"tracing",
"url",
"walkdir",
]
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
[[package]]
name = "once_cell"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "1.19.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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "3fdb12b2476b595f9358c5161aa467c2438859caa136dec86c26fdd2efe17b92"
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
[[package]]
name = "oorandom"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "11.1.4"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "b410bbe7e14ab526a0e86877eb47c6996a2bd7746f027ba551028c925390e4e9"
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
[[package]]
name = "opaque-debug"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.3.1"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "c08d65885ee38876c4f86fa503fb49d7b507c2b62552df7c70b2fce627e06381"
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
[[package]]
name = "open-dds"
Use v3.0.0 as the version number. (#999) ### What Updates the version number to `3.0.0`, now we're officially at GA. ### How I updated the version number, and also updated some dependencies. The `Cargo.lock` file was not up to date. V3_GIT_ORIGIN_REV_ID: 3e9b784c8ad856556193e56aee9fa607fa8ce19e
2024-08-21 17:02:43 +03:00
version = "3.0.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
dependencies = [
"derive_more",
"goldenfile",
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"indexmap 2.4.0",
Remove duplicate JSON Schema entries (#692) <!-- Thank you for submitting this PR! :) --> ## Description When we generate a JSON schema via `schemars`, we end up with duplicate types in the schema, which get names like `ValueExpression2`, `Role2`, and so on. This isn't ideal, and seems to arise for two reasons: 1. The type is polymorphic, and is monomorphised in two ways, and thus the types can't be unified. 2. The type is monomorphic, but is used inside and outside of its home module. The first problem was fixed previously by splitting polymorphic types, but the second has proven to be a bit more work. This PR finally solves the problem by introducing a new library, `jsonschema-tidying`: * First, we search the definitions within the JSON schema for any whose names end in a number, such as `ValueExpression2` or `MetadataV2`. * Then, we look for types whose names match everything up to the final numeric digits, and discard any types for whom we can't find a match (so we keep `ValueExpression2` because `ValueExpression` exists, but discard `MetadataV2` because `MetadataV` does not). * Next, we remove the duplicate definition from the definitions map, potentially breaking links in both the schema _and_ the rest of the definitions map. * Finally, we traverse the entirety of the tree looking for any references to the duplicate entry, and replace them with references to the original entry. This PR has no direct user-facing change, however it _will_ have an effect on the docs generation code, which will hopefully result in tidier documentation. <!-- Questions to consider answering: 1. What user-facing changes are being made? 4. What are issues related to this PR? (Consider adding `(close #<issue-no>)` to the PR title) 5. What is the conceptual design behind this PR? 6. How can this PR be tested/verified? 7. Does the PR have limitations? 8. Does the PR introduce breaking changes? --> ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [ ] community-edition - [ ] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [x] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> _Replace with changelog entry_ <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: fe73acf7d9df0b9867852e673e53cb086e3725d3
2024-06-11 11:27:42 +03:00
"jsonschema-tidying",
Use ndc-models 0.1.6 (#1013) <!-- The PR description should answer 2 important questions: --> ### What Update `v3-engine` to use `ndc-models` 0.1.6. ### How Update in Cargo.toml, check everything builds. V3_GIT_ORIGIN_REV_ID: 64d8b5b8126f593c10ffa89ba21791f326aefedd
2024-08-26 16:46:12 +03:00
"ndc-models 0.1.6",
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 0.2.0",
Custom deserializer for OpenDd objects (#313) V3_GIT_ORIGIN_REV_ID: 4c7a9380e517ac8e7ac1bd44dbe879918bd0d9a2
2024-03-11 15:16:53 +03:00
"opendds-derive",
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
"pretty_assertions",
use a newtype for data connector object type (#542) ## Description Introduce a newtype for data connector object type for the added context. V3_GIT_ORIGIN_REV_ID: b499d3a9cd2610fec05a4bc2e1b3cf522f198b9c
2024-05-03 12:32:28 +03:00
"ref-cast",
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
"schemars",
"serde",
"serde_json",
Custom deserializer for OpenDd objects (#313) V3_GIT_ORIGIN_REV_ID: 4c7a9380e517ac8e7ac1bd44dbe879918bd0d9a2
2024-03-11 15:16:53 +03:00
"serde_path_to_error",
Use `SubgraphIdentifier` in the metadata accessor, and `SmolStr` internally. (#768) ### What Using `String` everywhere to represent subgraph identifiers is definitely going to cause problems at some point. We can avoid this by using `open_dds::identifier::SubgraphIdentifier` instead. `Identifier` and `SubgraphIdentifier` were wrappers around `String`. I have also changed them to wrap `SmolStr` instead, for better performance as they're cloned a lot. ### How First of all, I hid the innards of `Identifier` and `SubgraphIdentifier`, instead exposing certain behaviors as methods. Mostly, this means exposing `as_str()` and `to_string()`. Then I replaced the internals with `SmolStr`. I had to change one place where `RefCast` was used, but that was pretty much it. Finally, I switched out `String` for `SubgraphIdentifier` in `QualifiedObject`. This necessitated a couple of constants for the two "magic" subgraphs, `__globals` and `__unknown_namespace`, but was otherwise fine. I didn't touch `Qualified` for now. V3_GIT_ORIGIN_REV_ID: 28664609c3173b181c3789093cb9796896642eb7
2024-06-27 01:03:31 +03:00
"smol_str",
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
"strum",
"strum_macros",
"thiserror",
]
Custom deserializer for OpenDd objects (#313) V3_GIT_ORIGIN_REV_ID: 4c7a9380e517ac8e7ac1bd44dbe879918bd0d9a2
2024-03-11 15:16:53 +03:00
[[package]]
name = "opendds-derive"
Use v3.0.0 as the version number. (#999) ### What Updates the version number to `3.0.0`, now we're officially at GA. ### How I updated the version number, and also updated some dependencies. The `Cargo.lock` file was not up to date. V3_GIT_ORIGIN_REV_ID: 3e9b784c8ad856556193e56aee9fa607fa8ce19e
2024-08-21 17:02:43 +03:00
version = "3.0.0"
Custom deserializer for OpenDd objects (#313) V3_GIT_ORIGIN_REV_ID: 4c7a9380e517ac8e7ac1bd44dbe879918bd0d9a2
2024-03-11 15:16:53 +03:00
dependencies = [
"convert_case 0.6.0",
Use `syn` v2 in our own macros. (#574) This upgrades `darling` and `schemars` too, so they also use `syn` v2. V3_GIT_ORIGIN_REV_ID: 731160389115dfa079fb1e13e831204d278f5a40
2024-05-14 10:49:52 +03:00
"darling",
Custom deserializer for OpenDd objects (#313) V3_GIT_ORIGIN_REV_ID: 4c7a9380e517ac8e7ac1bd44dbe879918bd0d9a2
2024-03-11 15:16:53 +03:00
"proc-macro2",
"quote",
Auto-generate schema titles that a code generator would like. (#696) It turns out that code generators based on JSON schemas don't always play nicely with characters such as `' '` or `'/'`. To work around this, when we use the schema name as a title, we replace any non-alphanumeric character or underscore with an underscore (`'_'`). V3_GIT_ORIGIN_REV_ID: 6af9a92c84c59294ff28bae27d7421627cde6a80
2024-06-11 16:39:56 +03:00
"regex",
Bump syn from 2.0.75 to 2.0.76 (#1017) Bumps [syn](https://github.com/dtolnay/syn) from 2.0.75 to 2.0.76. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/syn/releases">syn's releases</a>.</em></p> <blockquote> <h2>2.0.76</h2> <ul> <li>Enforce that tail call <code>become</code> keyword is followed by an expression (<a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/syn/commit/ef3e9c6dde79be7590fc90278772663ca31c1a73"><code>ef3e9c6</code></a> Release 2.0.76</li> <li><a href="https://github.com/dtolnay/syn/commit/8f7365ff9685c8ca9527c2de409204179a3efcdf"><code>8f7365f</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a> from dtolnay/tailcall</li> <li><a href="https://github.com/dtolnay/syn/commit/6cddd9ea714fe034466b4f02d3f7abb484c65ea0"><code>6cddd9e</code></a> Make tail call expr mandatory</li> <li>See full diff in <a href="https://github.com/dtolnay/syn/compare/2.0.75...2.0.76">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=syn&package-manager=cargo&previous-version=2.0.75&new-version=2.0.76)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d261ad30ffeb10034a80f9044504cb9d6c7c1ff7
2024-08-26 14:39:45 +03:00
"syn 2.0.76",
opendds-derive: Avoid panicking when unknown properties are encountered. (#528) By wrapping the errors we can work with both `syn` and `darling` errors, allowing us to avoid `.unwrap` and `.expect`. This makes failures way more useful. V3_GIT_ORIGIN_REV_ID: bd7c4a4e7de4a2360b4533d9238199f098a09a8d
2024-04-30 16:58:41 +03:00
"thiserror",
Custom deserializer for OpenDd objects (#313) V3_GIT_ORIGIN_REV_ID: 4c7a9380e517ac8e7ac1bd44dbe879918bd0d9a2
2024-03-11 15:16:53 +03:00
]
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
[[package]]
name = "openssl"
Bump openssl from 0.10.64 to 0.10.66 (#864) Bumps [openssl](https://github.com/sfackler/rust-openssl) from 0.10.64 to 0.10.66. V3_GIT_ORIGIN_REV_ID: b3d1e21b504122bb1a9e2332a60ee4b3f04781aa
2024-07-22 10:10:05 +03:00
version = "0.10.66"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump openssl from 0.10.64 to 0.10.66 (#864) Bumps [openssl](https://github.com/sfackler/rust-openssl) from 0.10.64 to 0.10.66. V3_GIT_ORIGIN_REV_ID: b3d1e21b504122bb1a9e2332a60ee4b3f04781aa
2024-07-22 10:10:05 +03:00
checksum = "9529f4786b70a3e8c61e11179af17ab6188ad8d0ded78c5529441ed39d4bd9c1"
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
dependencies = [
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
"bitflags 2.6.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
"cfg-if",
"foreign-types",
"libc",
"once_cell",
"openssl-macros",
"openssl-sys",
]
[[package]]
name = "openssl-macros"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a948666b637a0f465e8564c73e89d4dde00d72d4d473cc972f390fc3dcee7d9c"
dependencies = [
"proc-macro2",
"quote",
Bump syn from 2.0.75 to 2.0.76 (#1017) Bumps [syn](https://github.com/dtolnay/syn) from 2.0.75 to 2.0.76. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/syn/releases">syn's releases</a>.</em></p> <blockquote> <h2>2.0.76</h2> <ul> <li>Enforce that tail call <code>become</code> keyword is followed by an expression (<a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/syn/commit/ef3e9c6dde79be7590fc90278772663ca31c1a73"><code>ef3e9c6</code></a> Release 2.0.76</li> <li><a href="https://github.com/dtolnay/syn/commit/8f7365ff9685c8ca9527c2de409204179a3efcdf"><code>8f7365f</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a> from dtolnay/tailcall</li> <li><a href="https://github.com/dtolnay/syn/commit/6cddd9ea714fe034466b4f02d3f7abb484c65ea0"><code>6cddd9e</code></a> Make tail call expr mandatory</li> <li>See full diff in <a href="https://github.com/dtolnay/syn/compare/2.0.75...2.0.76">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=syn&package-manager=cargo&previous-version=2.0.75&new-version=2.0.76)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d261ad30ffeb10034a80f9044504cb9d6c7c1ff7
2024-08-26 14:39:45 +03:00
"syn 2.0.76",
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
]
[[package]]
name = "openssl-probe"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ff011a302c396a5197692431fc1948019154afc178baf7d8e37367442a4601cf"
[[package]]
name = "openssl-sys"
Bump openssl from 0.10.64 to 0.10.66 (#864) Bumps [openssl](https://github.com/sfackler/rust-openssl) from 0.10.64 to 0.10.66. V3_GIT_ORIGIN_REV_ID: b3d1e21b504122bb1a9e2332a60ee4b3f04781aa
2024-07-22 10:10:05 +03:00
version = "0.9.103"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump openssl from 0.10.64 to 0.10.66 (#864) Bumps [openssl](https://github.com/sfackler/rust-openssl) from 0.10.64 to 0.10.66. V3_GIT_ORIGIN_REV_ID: b3d1e21b504122bb1a9e2332a60ee4b3f04781aa
2024-07-22 10:10:05 +03:00
checksum = "7f9e8deee91df40a943c71b917e5874b951d32a802526c85721ce3b776c929d6"
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
dependencies = [
"cc",
"libc",
"pkg-config",
"vcpkg",
]
[[package]]
name = "opentelemetry"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.22.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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "900d57987be3f2aeb70d385fff9b27fb74c5723cc9a52d904d4f9c807a0667bf"
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
dependencies = [
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
"futures-core",
"futures-sink",
"js-sys",
"once_cell",
"pin-project-lite",
"thiserror",
"urlencoding",
add support for async span with parent context (#341) V3_GIT_ORIGIN_REV_ID: f24ff08407a4f00787dfb76a72f9de072b5a02a2
2024-03-15 12:25:41 +03:00
]
Pass `TraceContextResponsePropagator` to `set_text_map_propagator` (#884) <!-- The PR description should answer 2 (maybe 3) important questions: --> ### What In a recent engine change, we changed some of our trace context mapping to use the shared settings consistently. However, we needed to make sure we included `TraceContextResponsePropagator`, which returns the `traceresponse` header. Request from console after this fix: <img width="810" alt="Screenshot 2024-07-25 at 11 58 30" src="https://github.com/user-attachments/assets/c8e73c56-87fd-49da-a887-f91cdb6d607a"> <!-- What is this PR trying to accomplish (and why, if it's not obvious)? --> <!-- Consider: do we need to add a changelog entry? --> ### How Adds `TraceContextResponsePropagator` to the global set of text map propagators. <!-- How is it trying to accomplish it (what are the implementation steps)? --> V3_GIT_ORIGIN_REV_ID: 48df6a6fe55e78a48f1dc6bf82304199a0a7e248
2024-07-25 14:30:04 +03:00
[[package]]
name = "opentelemetry-contrib"
version = "0.14.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1d4c267ff82b3e9e9f548199267c3f722d9cffe3bfe4318b05fcf56fd5357aad"
dependencies = [
"once_cell",
"opentelemetry",
]
add support for async span with parent context (#341) V3_GIT_ORIGIN_REV_ID: f24ff08407a4f00787dfb76a72f9de072b5a02a2
2024-03-15 12:25:41 +03:00
[[package]]
name = "opentelemetry-http"
Bump opentelemetry-http from 0.11.0 to 0.11.1 (#570) V3_GIT_ORIGIN_REV_ID: 640702b99717dc86587a0e48798df27d85014c5a
2024-05-13 16:13:09 +03:00
version = "0.11.1"
add support for async span with parent context (#341) V3_GIT_ORIGIN_REV_ID: f24ff08407a4f00787dfb76a72f9de072b5a02a2
2024-03-15 12:25:41 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump opentelemetry-http from 0.11.0 to 0.11.1 (#570) V3_GIT_ORIGIN_REV_ID: 640702b99717dc86587a0e48798df27d85014c5a
2024-05-13 16:13:09 +03:00
checksum = "7690dc77bf776713848c4faa6501157469017eaf332baccd4eb1cea928743d94"
add support for async span with parent context (#341) V3_GIT_ORIGIN_REV_ID: f24ff08407a4f00787dfb76a72f9de072b5a02a2
2024-03-15 12:25:41 +03:00
dependencies = [
"async-trait",
"bytes",
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
"http",
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
"opentelemetry",
support OpenTelemetry zipkin propagator (#466) Support both W3C and Zipkin B3 headers and connectors will prefer B3 headers to extract traces because Cloud Run doesn't respect those headers. V3_GIT_ORIGIN_REV_ID: 1471b848e71d87420bc75b9adee60951f306c856
2024-04-16 17:55:54 +03:00
"reqwest",
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
]
[[package]]
name = "opentelemetry-otlp"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.15.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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "1a016b8d9495c639af2145ac22387dcb88e44118e45320d9238fbf4e7889abcb"
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
dependencies = [
"async-trait",
"futures-core",
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
"http",
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
"opentelemetry",
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
"opentelemetry-proto",
"opentelemetry-semantic-conventions",
Remove unused dependencies using `cargo machete`. (#413) `cargo machete` is a very useful tool that figures out when you aren't using a dependency. I have run this locally to remove unused dependencies. I've also added a CI job to make sure we catch these in the future. Sometimes it reports false positives, e.g. when a dependency isn't used directly but in macro-generated code (e.g. with `strum`). I have added `"ignored"` clauses to the `Cargo.toml` files where appropriate. V3_GIT_ORIGIN_REV_ID: ed015089b695cec8eeb03ce455d6dd3cd312a016
2024-03-28 12:16:54 +03:00
"opentelemetry_sdk",
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
"prost",
"thiserror",
"tokio",
"tonic",
]
[[package]]
name = "opentelemetry-proto"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.5.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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "3a8fddc9b68f5b80dae9d6f510b88e02396f006ad48cac349411fbecc80caae4"
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
dependencies = [
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
"opentelemetry",
Remove unused dependencies using `cargo machete`. (#413) `cargo machete` is a very useful tool that figures out when you aren't using a dependency. I have run this locally to remove unused dependencies. I've also added a CI job to make sure we catch these in the future. Sometimes it reports false positives, e.g. when a dependency isn't used directly but in macro-generated code (e.g. with `strum`). I have added `"ignored"` clauses to the `Cargo.toml` files where appropriate. V3_GIT_ORIGIN_REV_ID: ed015089b695cec8eeb03ce455d6dd3cd312a016
2024-03-28 12:16:54 +03:00
"opentelemetry_sdk",
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
"prost",
"tonic",
]
[[package]]
name = "opentelemetry-semantic-conventions"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.14.0"
add support for async span with parent context (#341) V3_GIT_ORIGIN_REV_ID: f24ff08407a4f00787dfb76a72f9de072b5a02a2
2024-03-15 12:25:41 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "f9ab5bd6c42fb9349dcf28af2ba9a0667f697f9bdcca045d39f2cec5543e2910"
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
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
[[package]]
name = "opentelemetry-stdout"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4bdf28b381f23afcd150afc0b38a4183dd321fc96320c1554752b6b761648f78"
dependencies = [
"chrono",
"futures-util",
"opentelemetry",
"opentelemetry_sdk",
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"ordered-float 4.2.2",
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
"serde",
"serde_json",
]
support OpenTelemetry zipkin propagator (#466) Support both W3C and Zipkin B3 headers and connectors will prefer B3 headers to extract traces because Cloud Run doesn't respect those headers. V3_GIT_ORIGIN_REV_ID: 1471b848e71d87420bc75b9adee60951f306c856
2024-04-16 17:55:54 +03:00
[[package]]
name = "opentelemetry-zipkin"
version = "0.20.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d6943c09b1b7c17b403ae842b00f23e6d5fc6f5ec06cccb3f39aca97094a899a"
dependencies = [
"async-trait",
"futures-core",
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
"http",
support OpenTelemetry zipkin propagator (#466) Support both W3C and Zipkin B3 headers and connectors will prefer B3 headers to extract traces because Cloud Run doesn't respect those headers. V3_GIT_ORIGIN_REV_ID: 1471b848e71d87420bc75b9adee60951f306c856
2024-04-16 17:55:54 +03:00
"once_cell",
"opentelemetry",
"opentelemetry-http",
"opentelemetry-semantic-conventions",
"opentelemetry_sdk",
"reqwest",
"serde",
"serde_json",
"thiserror",
"typed-builder",
]
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
[[package]]
name = "opentelemetry_sdk"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.22.1"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "9e90c7113be649e31e9a0f8b5ee24ed7a16923b322c3c5ab6367469c049d6b7e"
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
dependencies = [
"async-trait",
"crossbeam-channel",
"futures-channel",
"futures-executor",
"futures-util",
"once_cell",
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
"opentelemetry",
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"ordered-float 4.2.2",
Remove unused dependencies using `cargo machete`. (#413) `cargo machete` is a very useful tool that figures out when you aren't using a dependency. I have run this locally to remove unused dependencies. I've also added a CI job to make sure we catch these in the future. Sometimes it reports false positives, e.g. when a dependency isn't used directly but in macro-generated code (e.g. with `strum`). I have added `"ignored"` clauses to the `Cargo.toml` files where appropriate. V3_GIT_ORIGIN_REV_ID: ed015089b695cec8eeb03ce455d6dd3cd312a016
2024-03-28 12:16:54 +03:00
"percent-encoding",
add support for async span with parent context (#341) V3_GIT_ORIGIN_REV_ID: f24ff08407a4f00787dfb76a72f9de072b5a02a2
2024-03-15 12:25:41 +03:00
"rand",
"thiserror",
downgrade opentelemetry versions (#380) <!-- Thank you for submitting this PR! :) --> ## Description This PR downgrades the opentelemetry versions to 0.20. This fixed the tracing propagation issues faced [here](https://hasurahq.slack.com/archives/C066TKMH79R/p1710177836329809). ### TODOs: - [ ] Figure out the exact issue which caused the context propagation to stop working - [ ] Open an issue with [opentelemetry](https://github.com/open-telemetry/opentelemetry-rust) (if required). Co-authored-by: Anon Ray <ecthiender@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: 0bc4d8142bd2f671e04d1cbf806f4626e2217332
2024-03-21 12:56:35 +03:00
"tokio",
"tokio-stream",
add support for async span with parent context (#341) V3_GIT_ORIGIN_REV_ID: f24ff08407a4f00787dfb76a72f9de072b5a02a2
2024-03-15 12:25:41 +03:00
]
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
[[package]]
name = "ordered-float"
version = "2.10.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "68f19d67e5a2795c94e73e0bb1cc1a7edeb2e28efd39e2e1c9b7a40c1108b11c"
dependencies = [
"num-traits",
]
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
[[package]]
name = "ordered-float"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "4.2.2"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "4a91171844676f8c7990ce64959210cd2eaef32c2612c50f9fae9f8aaa6065a6"
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
dependencies = [
"num-traits",
]
[[package]]
name = "overload"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b15813163c1d831bf4a13c3610c05c0d03b39feb07f7e09fa234dac9b15aaf39"
[[package]]
name = "p256"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d053368e1bae4c8a672953397bd1bd7183dde1c72b0b7612a15719173148d186"
dependencies = [
"ecdsa",
"elliptic-curve",
add field arguments in schema and execution (#695) ### TODO - [x] Validate the presence of arguments in the data connector schema - [x] Add test for IR - [x] Add test using custom connector ## Description JIRA: https://hasurahq.atlassian.net/browse/V3ENGINE-148 This is part 2 of the field arguments. This will add the field arguments to the graphql schema and also handles the execution part. ![image](https://github.com/hasura/v3-engine/assets/85472423/c8f55d70-6539-42ef-ab5a-91b74e5699e2) ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> Add support for field arguments <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> --------- Co-authored-by: Anon Ray <ecthiender@users.noreply.github.com> Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: ea06b896feaca30419f81cd070fd4cfd608ef35b
2024-06-19 11:14:24 +03:00
"sha2 0.9.9",
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
]
[[package]]
name = "parking_lot"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.12.3"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "f1bf18183cf54e8d6059647fc3063646a1801cf30896933ec2311622cc4b9a27"
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
dependencies = [
"lock_api",
"parking_lot_core",
]
[[package]]
name = "parking_lot_core"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.9.10"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "1e401f977ab385c9e4e3ab30627d6f26d00e2c73eef317493c4ec6d468726cf8"
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
dependencies = [
"cfg-if",
"libc",
"redox_syscall",
"smallvec",
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"windows-targets 0.52.6",
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
]
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
[[package]]
name = "parquet"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
version = "52.2.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
checksum = "e977b9066b4d3b03555c22bdc442f3fadebd96a39111249113087d0edb2691cd"
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
dependencies = [
"ahash",
"arrow-array",
"arrow-buffer",
"arrow-cast",
"arrow-data",
"arrow-ipc",
"arrow-schema",
"arrow-select",
"base64 0.22.1",
"brotli",
"bytes",
"chrono",
"flate2",
"futures",
"half",
"hashbrown 0.14.5",
"lz4_flex",
"num",
"num-bigint",
"object_store",
"paste",
"seq-macro",
"snap",
"thrift",
"tokio",
"twox-hash",
"zstd",
"zstd-sys",
]
[[package]]
name = "parse-zoneinfo"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1f2a05b18d44e2957b88f96ba460715e295bc1d7510468a2f3d3b44535d26c24"
dependencies = [
"regex",
]
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
[[package]]
name = "paste"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "1.0.15"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "57c0d7b74b563b49d38dae00a0c37d4d6de9b432382b2892f0574ddcae73fd0a"
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
[[package]]
name = "pem"
version = "1.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a8835c273a76a90455d7344889b0964598e3316e2a79ede8e36f16bdcf2228b8"
dependencies = [
"base64 0.13.1",
]
[[package]]
name = "percent-encoding"
version = "2.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e3148f5046208a5d56bcfc03053e3ca6334e51da8dfb19b6cdc8b306fae3283e"
[[package]]
name = "pest"
Bump async-graphql-parser from 7.0.6 to 7.0.7 (#865) Bumps [async-graphql-parser](https://github.com/async-graphql/async-graphql) from 7.0.6 to 7.0.7. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/async-graphql/async-graphql/blob/master/CHANGELOG.md">async-graphql-parser's changelog</a>.</em></p> <blockquote> <h1>[7.0.7] 2024-07-14</h1> <ul> <li>Support raw values from serde_json <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1554">#1554</a></li> <li>The custom directive <code>ARGUMENT_DEFINITION</code> is not being output at the appropriate location in SDL <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1559">#1559</a></li> <li>Support for JSON extended representations of BSON ObjectId and Uuid <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1542">#1542</a></li> <li>feat: get directives from SelectionField <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1548">#1548</a></li> <li>Support Directives on Subscriptions <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1500">#1500</a></li> <li>fix subscription err typo <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1556">#1556</a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/async-graphql/async-graphql/commits">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=async-graphql-parser&package-manager=cargo&previous-version=7.0.6&new-version=7.0.7)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: 8c0d1a222a57c86cedf2f0870f6cccb0a861a3e6
2024-07-26 13:44:01 +03:00
version = "2.7.11"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump async-graphql-parser from 7.0.6 to 7.0.7 (#865) Bumps [async-graphql-parser](https://github.com/async-graphql/async-graphql) from 7.0.6 to 7.0.7. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/async-graphql/async-graphql/blob/master/CHANGELOG.md">async-graphql-parser's changelog</a>.</em></p> <blockquote> <h1>[7.0.7] 2024-07-14</h1> <ul> <li>Support raw values from serde_json <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1554">#1554</a></li> <li>The custom directive <code>ARGUMENT_DEFINITION</code> is not being output at the appropriate location in SDL <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1559">#1559</a></li> <li>Support for JSON extended representations of BSON ObjectId and Uuid <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1542">#1542</a></li> <li>feat: get directives from SelectionField <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1548">#1548</a></li> <li>Support Directives on Subscriptions <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1500">#1500</a></li> <li>fix subscription err typo <a href="https://redirect.github.com/async-graphql/async-graphql/pull/1556">#1556</a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/async-graphql/async-graphql/commits">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=async-graphql-parser&package-manager=cargo&previous-version=7.0.6&new-version=7.0.7)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: 8c0d1a222a57c86cedf2f0870f6cccb0a861a3e6
2024-07-26 13:44:01 +03:00
checksum = "cd53dff83f26735fdc1ca837098ccf133605d794cdae66acfc2bfac3ec809d95"
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
dependencies = [
"memchr",
"thiserror",
"ucd-trie",
]
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
[[package]]
name = "petgraph"
version = "0.6.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b4c5cc86750666a3ed20bdaf5ca2a0344f9c67674cae0515bec2da16fbaa47db"
dependencies = [
"fixedbitset",
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"indexmap 2.4.0",
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
]
[[package]]
name = "phf"
version = "0.11.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ade2d8b8f33c7333b51bcf0428d37e217e9f32192ae4772156f65063b8ce03dc"
dependencies = [
"phf_shared",
]
[[package]]
name = "phf_codegen"
version = "0.11.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e8d39688d359e6b34654d328e262234662d16cc0f60ec8dcbe5e718709342a5a"
dependencies = [
"phf_generator",
"phf_shared",
]
[[package]]
name = "phf_generator"
version = "0.11.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "48e4cc64c2ad9ebe670cb8fd69dd50ae301650392e81c05f9bfcb2d5bdbc24b0"
dependencies = [
"phf_shared",
"rand",
]
[[package]]
name = "phf_shared"
version = "0.11.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "90fcb95eef784c2ac79119d1dd819e162b5da872ce6f3c3abe1e8ca1c082f72b"
dependencies = [
"siphasher",
]
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
[[package]]
name = "pin-project"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "1.1.5"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "b6bf43b791c5b9e34c3d182969b4abb522f9343702850a2e57f460d00d09b4b3"
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
dependencies = [
"pin-project-internal",
]
[[package]]
name = "pin-project-internal"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "1.1.5"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "2f38a4412a78282e09a2cf38d195ea5420d15ba0602cb375210efbc877243965"
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
dependencies = [
"proc-macro2",
"quote",
Bump syn from 2.0.75 to 2.0.76 (#1017) Bumps [syn](https://github.com/dtolnay/syn) from 2.0.75 to 2.0.76. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/syn/releases">syn's releases</a>.</em></p> <blockquote> <h2>2.0.76</h2> <ul> <li>Enforce that tail call <code>become</code> keyword is followed by an expression (<a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/syn/commit/ef3e9c6dde79be7590fc90278772663ca31c1a73"><code>ef3e9c6</code></a> Release 2.0.76</li> <li><a href="https://github.com/dtolnay/syn/commit/8f7365ff9685c8ca9527c2de409204179a3efcdf"><code>8f7365f</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a> from dtolnay/tailcall</li> <li><a href="https://github.com/dtolnay/syn/commit/6cddd9ea714fe034466b4f02d3f7abb484c65ea0"><code>6cddd9e</code></a> Make tail call expr mandatory</li> <li>See full diff in <a href="https://github.com/dtolnay/syn/compare/2.0.75...2.0.76">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=syn&package-manager=cargo&previous-version=2.0.75&new-version=2.0.76)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d261ad30ffeb10034a80f9044504cb9d6c7c1ff7
2024-08-26 14:39:45 +03:00
"syn 2.0.76",
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
]
[[package]]
name = "pin-project-lite"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.2.14"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "bda66fc9667c18cb2758a2ac84d1167245054bcf85d5d1aaa6923f45801bdd02"
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
[[package]]
name = "pin-utils"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8b870d8c151b6f2fb93e84a13146138f05d02ed11c7e7c54f8826aaaf7c9f184"
[[package]]
name = "pkcs8"
version = "0.7.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ee3ef9b64d26bad0536099c816c6734379e45bbd5f14798def6809e5cc350447"
dependencies = [
"der",
"spki",
]
[[package]]
name = "pkg-config"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.3.30"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "d231b230927b5e4ad203db57bbcbee2802f6bce620b1e4a9024a07d94e2907ec"
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
[[package]]
name = "plotters"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.3.6"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "a15b6eccb8484002195a3e44fe65a4ce8e93a625797a063735536fd59cb01cf3"
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
dependencies = [
"num-traits",
"plotters-backend",
"plotters-svg",
"wasm-bindgen",
"web-sys",
]
[[package]]
name = "plotters-backend"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.3.6"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "414cec62c6634ae900ea1c56128dfe87cf63e7caece0852ec76aba307cebadb7"
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
[[package]]
name = "plotters-svg"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.3.6"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "81b30686a7d9c3e010b84284bdd26a29f2138574f52f5eb6f794fc0ad924e705"
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
dependencies = [
"plotters-backend",
]
[[package]]
name = "postcard"
Update to Rust v1.80.1. (#1002) ### What Upgrade to the latest version of Rust. ### How I modified `rust-toolchain.toml` and ran `cargo update`. V3_GIT_ORIGIN_REV_ID: 5fe675ee5dc568cd24de542c826ffd2d355f90ff
2024-08-22 11:08:47 +03:00
version = "1.0.10"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update to Rust v1.80.1. (#1002) ### What Upgrade to the latest version of Rust. ### How I modified `rust-toolchain.toml` and ran `cargo update`. V3_GIT_ORIGIN_REV_ID: 5fe675ee5dc568cd24de542c826ffd2d355f90ff
2024-08-22 11:08:47 +03:00
checksum = "5f7f0a8d620d71c457dd1d47df76bb18960378da56af4527aaa10f515eee732e"
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
dependencies = [
"cobs",
Update to Rust v1.80.1. (#1002) ### What Upgrade to the latest version of Rust. ### How I modified `rust-toolchain.toml` and ran `cargo update`. V3_GIT_ORIGIN_REV_ID: 5fe675ee5dc568cd24de542c826ffd2d355f90ff
2024-08-22 11:08:47 +03:00
"embedded-io 0.4.0",
"embedded-io 0.6.1",
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
"heapless",
"serde",
]
[[package]]
name = "powerfmt"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "439ee305def115ba05938db6eb1644ff94165c5ab5e9420d1c1bcedbba909391"
[[package]]
name = "ppv-lite86"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.2.20"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "77957b295656769bb8ad2b6a6b09d897d94f05c41b069aede1fcdaa675eaea04"
dependencies = [
"zerocopy",
]
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
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
[[package]]
name = "pre-execution-plugin"
Use v3.0.0 as the version number. (#999) ### What Updates the version number to `3.0.0`, now we're officially at GA. ### How I updated the version number, and also updated some dependencies. The `Cargo.lock` file was not up to date. V3_GIT_ORIGIN_REV_ID: 3e9b784c8ad856556193e56aee9fa607fa8ce19e
2024-08-21 17:02:43 +03:00
version = "3.0.0"
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
dependencies = [
"axum",
"hasura-authn-core",
"lang-graphql",
if no plugins make middleware no-op (#948) <!-- The PR description should answer 2 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? --> <!-- Does this PR introduce new validation that might break old builds? --> <!-- Consider: do we need to put new checks behind a flag? --> Just an improvement to the middleware plugin ### How <!-- How is it trying to accomplish it (what are the implementation steps)? --> We now take a nonempty list of plugins. This ensures that we only do things if we have plugins. V3_GIT_ORIGIN_REV_ID: c8fb548f763cdefe3526c67d7c801104ad5c527a
2024-08-09 18:17:29 +03:00
"nonempty",
plugins as opendd objects (#889) <!-- 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)? --> This PR introduces a new OpenDD object of kind `LifecyclePluginHook`. An example ```json { "kind": "LifecyclePluginHook", "version": "v1", "definition": { "pre": "parse", "name": "test", "url": "http://localhost:8787", "config": { "request": { "headers": { "additional": { "hasura-m-auth": { "value": "zZkhKqFjqXR4g5MZCsJUZCnhCcoPyZ" } } }, "session": {}, "rawRequest": { "query": {}, "variables": {} } } } } } ``` The plugin configs (only pre-parse plugins for now) are stored in the engine state and used wherever required. ### How We have added the OpenDD object. V3_GIT_ORIGIN_REV_ID: aa02315362e5fc9a36b63ead48909e1baa92779f
2024-08-08 12:00:51 +03:00
"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
"reqwest",
"serde",
"serde_json",
"thiserror",
"tracing-util",
]
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
[[package]]
name = "pretty_assertions"
version = "1.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "af7cee1a6c8a5b9208b3cb1061f10c0cb689087b3d8ce85fb9d2dd7a29b6ba66"
dependencies = [
"diff",
"yansi 0.5.1",
]
[[package]]
name = "proc-macro2"
Bump proc-macro2 from 1.0.85 to 1.0.86 (#743) V3_GIT_ORIGIN_REV_ID: e4ce81ae6a326c0fc667efbdf7ef676fde0d120c
2024-06-24 10:16:19 +03:00
version = "1.0.86"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump proc-macro2 from 1.0.85 to 1.0.86 (#743) V3_GIT_ORIGIN_REV_ID: e4ce81ae6a326c0fc667efbdf7ef676fde0d120c
2024-06-24 10:16:19 +03:00
checksum = "5e719e8df665df0d1c8fbfd238015744736151d4445ec0836b8e628aae103b77"
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
dependencies = [
"unicode-ident",
]
[[package]]
name = "prost"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.12.6"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "deb1435c188b76130da55f17a466d252ff7b1418b2ad3e037d127b94e3411f29"
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
dependencies = [
"bytes",
"prost-derive",
]
[[package]]
name = "prost-derive"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.12.6"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "81bddcdb20abf9501610992b6759a4c888aef7d1a7247ef75e2404275ac24af1"
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
dependencies = [
"anyhow",
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
"itertools 0.12.1",
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
"proc-macro2",
"quote",
Bump syn from 2.0.75 to 2.0.76 (#1017) Bumps [syn](https://github.com/dtolnay/syn) from 2.0.75 to 2.0.76. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/syn/releases">syn's releases</a>.</em></p> <blockquote> <h2>2.0.76</h2> <ul> <li>Enforce that tail call <code>become</code> keyword is followed by an expression (<a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/syn/commit/ef3e9c6dde79be7590fc90278772663ca31c1a73"><code>ef3e9c6</code></a> Release 2.0.76</li> <li><a href="https://github.com/dtolnay/syn/commit/8f7365ff9685c8ca9527c2de409204179a3efcdf"><code>8f7365f</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a> from dtolnay/tailcall</li> <li><a href="https://github.com/dtolnay/syn/commit/6cddd9ea714fe034466b4f02d3f7abb484c65ea0"><code>6cddd9e</code></a> Make tail call expr mandatory</li> <li>See full diff in <a href="https://github.com/dtolnay/syn/compare/2.0.75...2.0.76">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=syn&package-manager=cargo&previous-version=2.0.75&new-version=2.0.76)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d261ad30ffeb10034a80f9044504cb9d6c7c1ff7
2024-08-26 14:39:45 +03:00
"syn 2.0.76",
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
]
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
[[package]]
name = "query-usage-analytics"
Use v3.0.0 as the version number. (#999) ### What Updates the version number to `3.0.0`, now we're officially at GA. ### How I updated the version number, and also updated some dependencies. The `Cargo.lock` file was not up to date. V3_GIT_ORIGIN_REV_ID: 3e9b784c8ad856556193e56aee9fa607fa8ce19e
2024-08-21 17:02:43 +03:00
version = "3.0.0"
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
dependencies = [
Improvements to query usage analytics data shape (#715) This PR introduces the following changes to query usage analytics data shape: - The `name` field in `RelationshipUsage` is just `RelationshipName` without `Qualified` wrapper. The `source` is already qualified, and the same qualification applies to `name`. - The `used` for both field and input field is a list. A field can use multiple opendd objects at a time. - Example: A root field can use `Model` and `Permission` (with both filter and argument presets). - The permission usage now revamped to express available permissions in the opendd - Filter predicate - provides lists of fields and relationships - Field presets - provides a list of fields involved - Argument presets - provides a list of arguments involved - The `GqlFieldArgument` is dropped in favor of `GqlInputField`. - Opendd object usage is not specified for `GqlFieldArgument`. An input argument with object type can have field presets permission. It is replaced with `GqlInputField` to allow specifying the permission usage. This PR also includes JSON schema for the data shape with a golden test to verify. V3_GIT_ORIGIN_REV_ID: f0bf9ba201471af367ef5027bc2c8b9f915994ac
2024-06-25 10:56:31 +03:00
"goldenfile",
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
"metadata-resolve",
"open-dds",
Improvements to query usage analytics data shape (#715) This PR introduces the following changes to query usage analytics data shape: - The `name` field in `RelationshipUsage` is just `RelationshipName` without `Qualified` wrapper. The `source` is already qualified, and the same qualification applies to `name`. - The `used` for both field and input field is a list. A field can use multiple opendd objects at a time. - Example: A root field can use `Model` and `Permission` (with both filter and argument presets). - The permission usage now revamped to express available permissions in the opendd - Filter predicate - provides lists of fields and relationships - Field presets - provides a list of fields involved - Argument presets - provides a list of arguments involved - The `GqlFieldArgument` is dropped in favor of `GqlInputField`. - Opendd object usage is not specified for `GqlFieldArgument`. An input argument with object type can have field presets permission. It is replaced with `GqlInputField` to allow specifying the permission usage. This PR also includes JSON schema for the data shape with a golden test to verify. V3_GIT_ORIGIN_REV_ID: f0bf9ba201471af367ef5027bc2c8b9f915994ac
2024-06-25 10:56:31 +03:00
"schemars",
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
"serde",
"serde_json",
]
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
[[package]]
name = "quote"
Bump quote from 1.0.36 to 1.0.37 (#1014) Bumps [quote](https://github.com/dtolnay/quote) from 1.0.36 to 1.0.37. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/quote/releases">quote's releases</a>.</em></p> <blockquote> <h2>1.0.37</h2> <ul> <li>Implement ToTokens for CStr and CString (<a href="https://redirect.github.com/dtolnay/quote/issues/283">#283</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/quote/commit/b1ebffa035363a430862e033aa3268e8cb17affa"><code>b1ebffa</code></a> Release 1.0.37</li> <li><a href="https://github.com/dtolnay/quote/commit/43acd77961424b3cb5035688f74d14d556eefe90"><code>43acd77</code></a> Delete unneeded use of <code>ref</code></li> <li><a href="https://github.com/dtolnay/quote/commit/9382c2182ea10f8e0f90d1e5f15ca3f20a777dff"><code>9382c21</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/quote/issues/283">#283</a> from dtolnay/cstr</li> <li><a href="https://github.com/dtolnay/quote/commit/6ac432877bbfe43892677e32af7e3f0e28b6333e"><code>6ac4328</code></a> Add C string tests</li> <li><a href="https://github.com/dtolnay/quote/commit/9fb0591a17893eea81260351c6eb431e1fd83524"><code>9fb0591</code></a> Implement ToTokens for CStr and CString</li> <li><a href="https://github.com/dtolnay/quote/commit/ba7a9d08c9acba8ae97926dcc18822b20441c0fa"><code>ba7a9d0</code></a> Organize test imports</li> <li><a href="https://github.com/dtolnay/quote/commit/aa9970f9838a5b6dd5438c662921470f873e2b3a"><code>aa9970f</code></a> Inline the macro that generates primitive impls</li> <li><a href="https://github.com/dtolnay/quote/commit/ba411091c98c311526774adde73e724448836337"><code>ba41109</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/quote/issues/282">#282</a> from dtolnay/tokens</li> <li><a href="https://github.com/dtolnay/quote/commit/c77340a4c6869690ad7b40069e8ca1cb90e4abb8"><code>c77340a</code></a> Consistently use 'tokens' as the name of the &amp;mut TokenStream arg</li> <li><a href="https://github.com/dtolnay/quote/commit/a4a0abf12fa0137eca5aaa74fe88ca6694e78746"><code>a4a0abf</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/quote/issues/281">#281</a> from dtolnay/char</li> <li>Additional commits viewable in <a href="https://github.com/dtolnay/quote/compare/1.0.36...1.0.37">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=quote&package-manager=cargo&previous-version=1.0.36&new-version=1.0.37)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Samir Talwar <samir.talwar@hasura.io> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: cf50dd0980c4bf947d9aa5e767c94d3487d05e85
2024-08-26 12:59:58 +03:00
version = "1.0.37"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump quote from 1.0.36 to 1.0.37 (#1014) Bumps [quote](https://github.com/dtolnay/quote) from 1.0.36 to 1.0.37. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/quote/releases">quote's releases</a>.</em></p> <blockquote> <h2>1.0.37</h2> <ul> <li>Implement ToTokens for CStr and CString (<a href="https://redirect.github.com/dtolnay/quote/issues/283">#283</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/quote/commit/b1ebffa035363a430862e033aa3268e8cb17affa"><code>b1ebffa</code></a> Release 1.0.37</li> <li><a href="https://github.com/dtolnay/quote/commit/43acd77961424b3cb5035688f74d14d556eefe90"><code>43acd77</code></a> Delete unneeded use of <code>ref</code></li> <li><a href="https://github.com/dtolnay/quote/commit/9382c2182ea10f8e0f90d1e5f15ca3f20a777dff"><code>9382c21</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/quote/issues/283">#283</a> from dtolnay/cstr</li> <li><a href="https://github.com/dtolnay/quote/commit/6ac432877bbfe43892677e32af7e3f0e28b6333e"><code>6ac4328</code></a> Add C string tests</li> <li><a href="https://github.com/dtolnay/quote/commit/9fb0591a17893eea81260351c6eb431e1fd83524"><code>9fb0591</code></a> Implement ToTokens for CStr and CString</li> <li><a href="https://github.com/dtolnay/quote/commit/ba7a9d08c9acba8ae97926dcc18822b20441c0fa"><code>ba7a9d0</code></a> Organize test imports</li> <li><a href="https://github.com/dtolnay/quote/commit/aa9970f9838a5b6dd5438c662921470f873e2b3a"><code>aa9970f</code></a> Inline the macro that generates primitive impls</li> <li><a href="https://github.com/dtolnay/quote/commit/ba411091c98c311526774adde73e724448836337"><code>ba41109</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/quote/issues/282">#282</a> from dtolnay/tokens</li> <li><a href="https://github.com/dtolnay/quote/commit/c77340a4c6869690ad7b40069e8ca1cb90e4abb8"><code>c77340a</code></a> Consistently use 'tokens' as the name of the &amp;mut TokenStream arg</li> <li><a href="https://github.com/dtolnay/quote/commit/a4a0abf12fa0137eca5aaa74fe88ca6694e78746"><code>a4a0abf</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/quote/issues/281">#281</a> from dtolnay/char</li> <li>Additional commits viewable in <a href="https://github.com/dtolnay/quote/compare/1.0.36...1.0.37">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=quote&package-manager=cargo&previous-version=1.0.36&new-version=1.0.37)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Samir Talwar <samir.talwar@hasura.io> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: cf50dd0980c4bf947d9aa5e767c94d3487d05e85
2024-08-26 12:59:58 +03:00
checksum = "b5b9d34b8991d19d98081b46eacdd8eb58c6f2b201139f7c5f643cc155a633af"
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
dependencies = [
"proc-macro2",
]
[[package]]
name = "radium"
version = "0.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "dc33ff2d4973d518d823d61aa239014831e521c75da58e3df4840d3f47749d09"
[[package]]
name = "rand"
version = "0.8.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "34af8d1a0e25924bc5b7c43c079c942339d8f0a8b57c39049bef581b46327404"
dependencies = [
"libc",
"rand_chacha",
"rand_core",
]
[[package]]
name = "rand_chacha"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e6c10a63a0fa32252be49d21e7709d4d4baf8d231c2dbce1eaa8141b9b127d88"
dependencies = [
"ppv-lite86",
"rand_core",
]
[[package]]
name = "rand_core"
version = "0.6.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ec0be4795e2f6a28069bec0b5ff3e2ac9bafc99e6a9a7dc3547996c5c816922c"
dependencies = [
"getrandom",
]
[[package]]
name = "rayon"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "1.10.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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "b418a60154510ca1a002a752ca9714984e21e4241e804d32555251faf8b78ffa"
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
dependencies = [
"either",
"rayon-core",
]
[[package]]
name = "rayon-core"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "1.12.1"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "1465873a3dfdaa8ae7cb14b4383657caab0b3e8a0aa9ae8e04b044854c8dfce2"
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
dependencies = [
"crossbeam-deque",
"crossbeam-utils",
]
lang-graphql: limit recursion to avoid stack overflows This was a simple solution to prevent crashes from the cases that I was able to discover, refactored into a macro that can be used elsewhere; but I suspect there's a more idiomatic rust solution (entailing a big refactor?). There's also the stacker crate, and see also discussion here: https://hasurahq.slack.com/archives/C04PUMV4X16/p1707337409839869?thread_ts=1701302324.058369&cid=C04PUMV4X16 Note that the compiled binary was built and fuzzed with `--release`. Many discovered cases caused crashes when run into non-optimized binary (probably stack overflows but I did not look into it) V3_GIT_ORIGIN_REV_ID: 31acfc9e358c807be80ba6a5efa78ace78306291
2024-02-13 23:27:48 +03:00
[[package]]
name = "recursion_limit_macro"
Use v3.0.0 as the version number. (#999) ### What Updates the version number to `3.0.0`, now we're officially at GA. ### How I updated the version number, and also updated some dependencies. The `Cargo.lock` file was not up to date. V3_GIT_ORIGIN_REV_ID: 3e9b784c8ad856556193e56aee9fa607fa8ce19e
2024-08-21 17:02:43 +03:00
version = "3.0.0"
lang-graphql: limit recursion to avoid stack overflows This was a simple solution to prevent crashes from the cases that I was able to discover, refactored into a macro that can be used elsewhere; but I suspect there's a more idiomatic rust solution (entailing a big refactor?). There's also the stacker crate, and see also discussion here: https://hasurahq.slack.com/archives/C04PUMV4X16/p1707337409839869?thread_ts=1701302324.058369&cid=C04PUMV4X16 Note that the compiled binary was built and fuzzed with `--release`. Many discovered cases caused crashes when run into non-optimized binary (probably stack overflows but I did not look into it) V3_GIT_ORIGIN_REV_ID: 31acfc9e358c807be80ba6a5efa78ace78306291
2024-02-13 23:27:48 +03:00
dependencies = [
"quote",
Bump syn from 2.0.75 to 2.0.76 (#1017) Bumps [syn](https://github.com/dtolnay/syn) from 2.0.75 to 2.0.76. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/syn/releases">syn's releases</a>.</em></p> <blockquote> <h2>2.0.76</h2> <ul> <li>Enforce that tail call <code>become</code> keyword is followed by an expression (<a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/syn/commit/ef3e9c6dde79be7590fc90278772663ca31c1a73"><code>ef3e9c6</code></a> Release 2.0.76</li> <li><a href="https://github.com/dtolnay/syn/commit/8f7365ff9685c8ca9527c2de409204179a3efcdf"><code>8f7365f</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a> from dtolnay/tailcall</li> <li><a href="https://github.com/dtolnay/syn/commit/6cddd9ea714fe034466b4f02d3f7abb484c65ea0"><code>6cddd9e</code></a> Make tail call expr mandatory</li> <li>See full diff in <a href="https://github.com/dtolnay/syn/compare/2.0.75...2.0.76">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=syn&package-manager=cargo&previous-version=2.0.75&new-version=2.0.76)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d261ad30ffeb10034a80f9044504cb9d6c7c1ff7
2024-08-26 14:39:45 +03:00
"syn 2.0.76",
lang-graphql: limit recursion to avoid stack overflows This was a simple solution to prevent crashes from the cases that I was able to discover, refactored into a macro that can be used elsewhere; but I suspect there's a more idiomatic rust solution (entailing a big refactor?). There's also the stacker crate, and see also discussion here: https://hasurahq.slack.com/archives/C04PUMV4X16/p1707337409839869?thread_ts=1701302324.058369&cid=C04PUMV4X16 Note that the compiled binary was built and fuzzed with `--release`. Many discovered cases caused crashes when run into non-optimized binary (probably stack overflows but I did not look into it) V3_GIT_ORIGIN_REV_ID: 31acfc9e358c807be80ba6a5efa78ace78306291
2024-02-13 23:27:48 +03:00
]
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
[[package]]
name = "redox_syscall"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.5.3"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "2a908a6e00f1fdd0dfd9c0eb08ce85126f6d8bbda50017e74bc4a4b7d4a926a4"
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
dependencies = [
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
"bitflags 2.6.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
]
use a newtype for data connector object type (#542) ## Description Introduce a newtype for data connector object type for the added context. V3_GIT_ORIGIN_REV_ID: b499d3a9cd2610fec05a4bc2e1b3cf522f198b9c
2024-05-03 12:32:28 +03:00
[[package]]
name = "ref-cast"
Bump ref-cast from 1.0.22 to 1.0.23 (#720) Bumps [ref-cast](https://github.com/dtolnay/ref-cast) from 1.0.22 to 1.0.23. Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: cf11179ca52be7fc1430246c319b6c68f4b034a0
2024-06-17 09:06:37 +03:00
version = "1.0.23"
use a newtype for data connector object type (#542) ## Description Introduce a newtype for data connector object type for the added context. V3_GIT_ORIGIN_REV_ID: b499d3a9cd2610fec05a4bc2e1b3cf522f198b9c
2024-05-03 12:32:28 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump ref-cast from 1.0.22 to 1.0.23 (#720) Bumps [ref-cast](https://github.com/dtolnay/ref-cast) from 1.0.22 to 1.0.23. Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: cf11179ca52be7fc1430246c319b6c68f4b034a0
2024-06-17 09:06:37 +03:00
checksum = "ccf0a6f84d5f1d581da8b41b47ec8600871962f2a528115b542b362d4b744931"
use a newtype for data connector object type (#542) ## Description Introduce a newtype for data connector object type for the added context. V3_GIT_ORIGIN_REV_ID: b499d3a9cd2610fec05a4bc2e1b3cf522f198b9c
2024-05-03 12:32:28 +03:00
dependencies = [
"ref-cast-impl",
]
[[package]]
name = "ref-cast-impl"
Bump ref-cast from 1.0.22 to 1.0.23 (#720) Bumps [ref-cast](https://github.com/dtolnay/ref-cast) from 1.0.22 to 1.0.23. Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: cf11179ca52be7fc1430246c319b6c68f4b034a0
2024-06-17 09:06:37 +03:00
version = "1.0.23"
use a newtype for data connector object type (#542) ## Description Introduce a newtype for data connector object type for the added context. V3_GIT_ORIGIN_REV_ID: b499d3a9cd2610fec05a4bc2e1b3cf522f198b9c
2024-05-03 12:32:28 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump ref-cast from 1.0.22 to 1.0.23 (#720) Bumps [ref-cast](https://github.com/dtolnay/ref-cast) from 1.0.22 to 1.0.23. Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: cf11179ca52be7fc1430246c319b6c68f4b034a0
2024-06-17 09:06:37 +03:00
checksum = "bcc303e793d3734489387d205e9b186fac9c6cfacedd98cbb2e8a5943595f3e6"
use a newtype for data connector object type (#542) ## Description Introduce a newtype for data connector object type for the added context. V3_GIT_ORIGIN_REV_ID: b499d3a9cd2610fec05a4bc2e1b3cf522f198b9c
2024-05-03 12:32:28 +03:00
dependencies = [
"proc-macro2",
"quote",
Bump syn from 2.0.75 to 2.0.76 (#1017) Bumps [syn](https://github.com/dtolnay/syn) from 2.0.75 to 2.0.76. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/syn/releases">syn's releases</a>.</em></p> <blockquote> <h2>2.0.76</h2> <ul> <li>Enforce that tail call <code>become</code> keyword is followed by an expression (<a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/syn/commit/ef3e9c6dde79be7590fc90278772663ca31c1a73"><code>ef3e9c6</code></a> Release 2.0.76</li> <li><a href="https://github.com/dtolnay/syn/commit/8f7365ff9685c8ca9527c2de409204179a3efcdf"><code>8f7365f</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a> from dtolnay/tailcall</li> <li><a href="https://github.com/dtolnay/syn/commit/6cddd9ea714fe034466b4f02d3f7abb484c65ea0"><code>6cddd9e</code></a> Make tail call expr mandatory</li> <li>See full diff in <a href="https://github.com/dtolnay/syn/compare/2.0.75...2.0.76">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=syn&package-manager=cargo&previous-version=2.0.75&new-version=2.0.76)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d261ad30ffeb10034a80f9044504cb9d6c7c1ff7
2024-08-26 14:39:45 +03:00
"syn 2.0.76",
use a newtype for data connector object type (#542) ## Description Introduce a newtype for data connector object type for the added context. V3_GIT_ORIGIN_REV_ID: b499d3a9cd2610fec05a4bc2e1b3cf522f198b9c
2024-05-03 12:32:28 +03:00
]
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
[[package]]
name = "regex"
Bump regex from 1.10.5 to 1.10.6 (#930) Bumps [regex](https://github.com/rust-lang/regex) from 1.10.5 to 1.10.6. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/rust-lang/regex/blob/master/CHANGELOG.md">regex's changelog</a>.</em></p> <blockquote> <h1>1.10.6 (2024-08-02)</h1> <p>This is a new patch release with a fix for the <code>unstable</code> crate feature that enables <code>std::str::Pattern</code> trait integration.</p> <p>Bug fixes:</p> <ul> <li>[BUG <a href="https://redirect.github.com/rust-lang/regex/issues/1219">#1219</a>](<a href="https://redirect.github.com/rust-lang/regex/pull/1219">rust-lang/regex#1219</a>): Fix the <code>Pattern</code> trait implementation as a result of nightly API breakage.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/rust-lang/regex/commit/ab88aa5c6824ebe7c4b4c72fe5191681783b3a68"><code>ab88aa5</code></a> 1.10.6</li> <li><a href="https://github.com/rust-lang/regex/commit/76f2d30d85eb70336b76d20bb6eb462de6391321"><code>76f2d30</code></a> changelog: 1.10.6</li> <li><a href="https://github.com/rust-lang/regex/commit/2970d2940dfab8cb4bd8f7122ba8ee50d2e37f67"><code>2970d29</code></a> unstable: fit <code>Pattern</code> trait implementation</li> <li><a href="https://github.com/rust-lang/regex/commit/8856fe36ac7dc37989e6ffb26b5fc57189bae626"><code>8856fe3</code></a> regex-cli-0.2.1</li> <li><a href="https://github.com/rust-lang/regex/commit/c4c76a19b80b981b249f2af1c7b66bcfb0ba1fa0"><code>c4c76a1</code></a> regex-test-0.1.1</li> <li><a href="https://github.com/rust-lang/regex/commit/c2f9ca49a66c51d88b71e5b2248d86789765d2ce"><code>c2f9ca4</code></a> regex-test: bump toml dependency</li> <li><a href="https://github.com/rust-lang/regex/commit/1288b83af3d8b441efb264ed6651b0dfb9c2df78"><code>1288b83</code></a> regex-lite-0.1.6</li> <li>See full diff in <a href="https://github.com/rust-lang/regex/compare/1.10.5...1.10.6">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=regex&package-manager=cargo&previous-version=1.10.5&new-version=1.10.6)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: 527f0e7680e48f2c97e6e36acc28fab7fcc82e2a
2024-08-05 08:28:55 +03:00
version = "1.10.6"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump regex from 1.10.5 to 1.10.6 (#930) Bumps [regex](https://github.com/rust-lang/regex) from 1.10.5 to 1.10.6. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/rust-lang/regex/blob/master/CHANGELOG.md">regex's changelog</a>.</em></p> <blockquote> <h1>1.10.6 (2024-08-02)</h1> <p>This is a new patch release with a fix for the <code>unstable</code> crate feature that enables <code>std::str::Pattern</code> trait integration.</p> <p>Bug fixes:</p> <ul> <li>[BUG <a href="https://redirect.github.com/rust-lang/regex/issues/1219">#1219</a>](<a href="https://redirect.github.com/rust-lang/regex/pull/1219">rust-lang/regex#1219</a>): Fix the <code>Pattern</code> trait implementation as a result of nightly API breakage.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/rust-lang/regex/commit/ab88aa5c6824ebe7c4b4c72fe5191681783b3a68"><code>ab88aa5</code></a> 1.10.6</li> <li><a href="https://github.com/rust-lang/regex/commit/76f2d30d85eb70336b76d20bb6eb462de6391321"><code>76f2d30</code></a> changelog: 1.10.6</li> <li><a href="https://github.com/rust-lang/regex/commit/2970d2940dfab8cb4bd8f7122ba8ee50d2e37f67"><code>2970d29</code></a> unstable: fit <code>Pattern</code> trait implementation</li> <li><a href="https://github.com/rust-lang/regex/commit/8856fe36ac7dc37989e6ffb26b5fc57189bae626"><code>8856fe3</code></a> regex-cli-0.2.1</li> <li><a href="https://github.com/rust-lang/regex/commit/c4c76a19b80b981b249f2af1c7b66bcfb0ba1fa0"><code>c4c76a1</code></a> regex-test-0.1.1</li> <li><a href="https://github.com/rust-lang/regex/commit/c2f9ca49a66c51d88b71e5b2248d86789765d2ce"><code>c2f9ca4</code></a> regex-test: bump toml dependency</li> <li><a href="https://github.com/rust-lang/regex/commit/1288b83af3d8b441efb264ed6651b0dfb9c2df78"><code>1288b83</code></a> regex-lite-0.1.6</li> <li>See full diff in <a href="https://github.com/rust-lang/regex/compare/1.10.5...1.10.6">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=regex&package-manager=cargo&previous-version=1.10.5&new-version=1.10.6)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: 527f0e7680e48f2c97e6e36acc28fab7fcc82e2a
2024-08-05 08:28:55 +03:00
checksum = "4219d74c6b67a3654a9fbebc4b419e22126d13d2f3c4a07ee0cb61ff79a79619"
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
dependencies = [
"aho-corasick",
"memchr",
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"regex-automata",
Remove unused dependencies using `cargo machete`. (#413) `cargo machete` is a very useful tool that figures out when you aren't using a dependency. I have run this locally to remove unused dependencies. I've also added a CI job to make sure we catch these in the future. Sometimes it reports false positives, e.g. when a dependency isn't used directly but in macro-generated code (e.g. with `strum`). I have added `"ignored"` clauses to the `Cargo.toml` files where appropriate. V3_GIT_ORIGIN_REV_ID: ed015089b695cec8eeb03ce455d6dd3cd312a016
2024-03-28 12:16:54 +03:00
"regex-syntax",
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
]
[[package]]
name = "regex-automata"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.4.7"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "38caf58cc5ef2fed281f89292ef23f6365465ed9a41b7a7754eb4e26496c92df"
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
dependencies = [
"aho-corasick",
"memchr",
Remove unused dependencies using `cargo machete`. (#413) `cargo machete` is a very useful tool that figures out when you aren't using a dependency. I have run this locally to remove unused dependencies. I've also added a CI job to make sure we catch these in the future. Sometimes it reports false positives, e.g. when a dependency isn't used directly but in macro-generated code (e.g. with `strum`). I have added `"ignored"` clauses to the `Cargo.toml` files where appropriate. V3_GIT_ORIGIN_REV_ID: ed015089b695cec8eeb03ce455d6dd3cd312a016
2024-03-28 12:16:54 +03:00
"regex-syntax",
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
]
[[package]]
name = "regex-syntax"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.8.4"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "7a66a03ae7c801facd77a29370b4faec201768915ac14a721ba36f20bc9c209b"
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
[[package]]
name = "reqwest"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.11.27"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "dd67538700a17451e7cba03ac727fb961abb7607553461627b97de0b89cf4a62"
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
dependencies = [
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
"base64 0.21.7",
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
"bytes",
"encoding_rs",
"futures-core",
"futures-util",
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
"h2",
"http",
"http-body",
"hyper",
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
"hyper-tls",
"ipnet",
"js-sys",
"log",
"mime",
"mime_guess",
"native-tls",
"once_cell",
Remove unused dependencies using `cargo machete`. (#413) `cargo machete` is a very useful tool that figures out when you aren't using a dependency. I have run this locally to remove unused dependencies. I've also added a CI job to make sure we catch these in the future. Sometimes it reports false positives, e.g. when a dependency isn't used directly but in macro-generated code (e.g. with `strum`). I have added `"ignored"` clauses to the `Cargo.toml` files where appropriate. V3_GIT_ORIGIN_REV_ID: ed015089b695cec8eeb03ce455d6dd3cd312a016
2024-03-28 12:16:54 +03:00
"percent-encoding",
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
"pin-project-lite",
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
"rustls-pemfile",
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
"serde",
"serde_json",
"serde_urlencoded",
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
"sync_wrapper",
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
"system-configuration",
"tokio",
"tokio-native-tls",
"tower-service",
Remove unused dependencies using `cargo machete`. (#413) `cargo machete` is a very useful tool that figures out when you aren't using a dependency. I have run this locally to remove unused dependencies. I've also added a CI job to make sure we catch these in the future. Sometimes it reports false positives, e.g. when a dependency isn't used directly but in macro-generated code (e.g. with `strum`). I have added `"ignored"` clauses to the `Cargo.toml` files where appropriate. V3_GIT_ORIGIN_REV_ID: ed015089b695cec8eeb03ce455d6dd3cd312a016
2024-03-28 12:16:54 +03:00
"url",
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
"wasm-bindgen",
"wasm-bindgen-futures",
"web-sys",
"winreg",
]
[[package]]
name = "ring"
version = "0.16.20"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3053cf52e236a3ed746dfc745aa9cacf1b791d846bdaf412f60a8d7d6e17c8fc"
dependencies = [
"cc",
"libc",
"once_cell",
"spin 0.5.2",
"untrusted",
"web-sys",
"winapi",
]
[[package]]
name = "rmp"
Bump rmp-serde from 1.1.2 to 1.3.0 (#596) Bumps [rmp-serde](https://github.com/3Hren/msgpack-rust) from 1.1.2 to 1.3.0. <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/3Hren/msgpack-rust/commits/rmp-serde/v1.3.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=rmp-serde&package-manager=cargo&previous-version=1.1.2&new-version=1.3.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: c03bfaa8c506b69a06b9a0563ce2e70df21df11e
2024-05-20 11:30:14 +03:00
version = "0.8.14"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump rmp-serde from 1.1.2 to 1.3.0 (#596) Bumps [rmp-serde](https://github.com/3Hren/msgpack-rust) from 1.1.2 to 1.3.0. <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/3Hren/msgpack-rust/commits/rmp-serde/v1.3.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=rmp-serde&package-manager=cargo&previous-version=1.1.2&new-version=1.3.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: c03bfaa8c506b69a06b9a0563ce2e70df21df11e
2024-05-20 11:30:14 +03:00
checksum = "228ed7c16fa39782c3b3468e974aec2795e9089153cd08ee2e9aefb3613334c4"
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
dependencies = [
"byteorder",
"num-traits",
"paste",
]
[[package]]
name = "rmp-serde"
Bump rmp-serde from 1.1.2 to 1.3.0 (#596) Bumps [rmp-serde](https://github.com/3Hren/msgpack-rust) from 1.1.2 to 1.3.0. <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/3Hren/msgpack-rust/commits/rmp-serde/v1.3.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=rmp-serde&package-manager=cargo&previous-version=1.1.2&new-version=1.3.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: c03bfaa8c506b69a06b9a0563ce2e70df21df11e
2024-05-20 11:30:14 +03:00
version = "1.3.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
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump rmp-serde from 1.1.2 to 1.3.0 (#596) Bumps [rmp-serde](https://github.com/3Hren/msgpack-rust) from 1.1.2 to 1.3.0. <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/3Hren/msgpack-rust/commits/rmp-serde/v1.3.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=rmp-serde&package-manager=cargo&previous-version=1.1.2&new-version=1.3.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: c03bfaa8c506b69a06b9a0563ce2e70df21df11e
2024-05-20 11:30:14 +03:00
checksum = "52e599a477cf9840e92f2cde9a7189e67b42c57532749bf90aea6ec10facd4db"
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
dependencies = [
"byteorder",
"rmp",
"serde",
]
[[package]]
name = "rowan"
Update to Rust v1.80.1. (#1002) ### What Upgrade to the latest version of Rust. ### How I modified `rust-toolchain.toml` and ran `cargo update`. V3_GIT_ORIGIN_REV_ID: 5fe675ee5dc568cd24de542c826ffd2d355f90ff
2024-08-22 11:08:47 +03:00
version = "0.15.16"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update to Rust v1.80.1. (#1002) ### What Upgrade to the latest version of Rust. ### How I modified `rust-toolchain.toml` and ran `cargo update`. V3_GIT_ORIGIN_REV_ID: 5fe675ee5dc568cd24de542c826ffd2d355f90ff
2024-08-22 11:08:47 +03:00
checksum = "0a542b0253fa46e632d27a1dc5cf7b930de4df8659dc6e720b647fc72147ae3d"
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
dependencies = [
"countme",
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
"hashbrown 0.14.5",
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
"rustc-hash",
"text-size",
]
[[package]]
name = "rustc-demangle"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.1.24"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "719b953e2095829ee67db738b3bfa9fa368c94900df327b3f07fe6e794d2fe1f"
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
[[package]]
name = "rustc-hash"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "08d43f7aa6b08d49f382cde6a7982047c3426db949b1424bc4b7ec9ae12c6ce2"
[[package]]
name = "rustc_version"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bfa0f585226d2e68097d4f95d113b15b83a82e819ab25717ec0590d9584ef366"
dependencies = [
"semver",
]
[[package]]
name = "rustix"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.38.34"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "70dc5ec042f7a43c4a73241207cecc9873a06d45debb38b329f8541d85c2730f"
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
dependencies = [
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
"bitflags 2.6.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
"errno",
"libc",
"linux-raw-sys",
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
"windows-sys 0.52.0",
]
[[package]]
name = "rustls-pemfile"
version = "1.0.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1c74cae0a4cf6ccbbf5f359f08efdf8ee7e1dc532573bf0db71968cb56b1448c"
dependencies = [
"base64 0.21.7",
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
]
[[package]]
name = "rustversion"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "1.0.17"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "955d28af4278de8121b7ebeb796b6a45735dc01436d898801014aced2773a3d6"
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
[[package]]
name = "ryu"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "1.0.18"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "f3cb5ba0dc43242ce17de99c180e96db90b235b8a9fdc9543c96d2209116bd9f"
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
use short commit SHA as version and mark non-release builds as dev (#295) V3_GIT_ORIGIN_REV_ID: 78475725003cd57790361caa8659c7a7146eacf2
2024-01-25 11:53:24 +03:00
[[package]]
name = "safe-proc-macro2"
version = "1.0.67"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7fd85be67db87168aa3c13fd0da99f48f2ab005dccad5af5626138dc1df20eb6"
dependencies = [
"unicode-ident",
]
[[package]]
name = "safe-quote"
version = "1.0.15"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "77e530f7831f3feafcd5f1aae406ac205dd998436b4007c8e80f03eca78a88f7"
dependencies = [
"safe-proc-macro2",
]
[[package]]
name = "safe-regex"
Bump build-data from 0.1.5 to 0.2.1 (#688) Bumps [build-data](https://gitlab.com/leonhard-llc/ops) from 0.1.5 to 0.2.1. V3_GIT_ORIGIN_REV_ID: 5e2b922820ecb44706f6a628d5dcb60c8ad5df76
2024-06-10 09:01:09 +03:00
version = "0.3.0"
use short commit SHA as version and mark non-release builds as dev (#295) V3_GIT_ORIGIN_REV_ID: 78475725003cd57790361caa8659c7a7146eacf2
2024-01-25 11:53:24 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump build-data from 0.1.5 to 0.2.1 (#688) Bumps [build-data](https://gitlab.com/leonhard-llc/ops) from 0.1.5 to 0.2.1. V3_GIT_ORIGIN_REV_ID: 5e2b922820ecb44706f6a628d5dcb60c8ad5df76
2024-06-10 09:01:09 +03:00
checksum = "5194fafa3cb9da89e0cab6dffa1f3fdded586bd6396d12be11b4cae0c7ee45c2"
use short commit SHA as version and mark non-release builds as dev (#295) V3_GIT_ORIGIN_REV_ID: 78475725003cd57790361caa8659c7a7146eacf2
2024-01-25 11:53:24 +03:00
dependencies = [
"safe-regex-macro",
]
[[package]]
name = "safe-regex-compiler"
Bump build-data from 0.1.5 to 0.2.1 (#688) Bumps [build-data](https://gitlab.com/leonhard-llc/ops) from 0.1.5 to 0.2.1. V3_GIT_ORIGIN_REV_ID: 5e2b922820ecb44706f6a628d5dcb60c8ad5df76
2024-06-10 09:01:09 +03:00
version = "0.3.0"
use short commit SHA as version and mark non-release builds as dev (#295) V3_GIT_ORIGIN_REV_ID: 78475725003cd57790361caa8659c7a7146eacf2
2024-01-25 11:53:24 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump build-data from 0.1.5 to 0.2.1 (#688) Bumps [build-data](https://gitlab.com/leonhard-llc/ops) from 0.1.5 to 0.2.1. V3_GIT_ORIGIN_REV_ID: 5e2b922820ecb44706f6a628d5dcb60c8ad5df76
2024-06-10 09:01:09 +03:00
checksum = "e822ae1e61251bcfd698317c237cf83f7c57161a5dc24ee609a85697f1ed15b3"
use short commit SHA as version and mark non-release builds as dev (#295) V3_GIT_ORIGIN_REV_ID: 78475725003cd57790361caa8659c7a7146eacf2
2024-01-25 11:53:24 +03:00
dependencies = [
"safe-proc-macro2",
"safe-quote",
]
[[package]]
name = "safe-regex-macro"
Bump build-data from 0.1.5 to 0.2.1 (#688) Bumps [build-data](https://gitlab.com/leonhard-llc/ops) from 0.1.5 to 0.2.1. V3_GIT_ORIGIN_REV_ID: 5e2b922820ecb44706f6a628d5dcb60c8ad5df76
2024-06-10 09:01:09 +03:00
version = "0.3.0"
use short commit SHA as version and mark non-release builds as dev (#295) V3_GIT_ORIGIN_REV_ID: 78475725003cd57790361caa8659c7a7146eacf2
2024-01-25 11:53:24 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump build-data from 0.1.5 to 0.2.1 (#688) Bumps [build-data](https://gitlab.com/leonhard-llc/ops) from 0.1.5 to 0.2.1. V3_GIT_ORIGIN_REV_ID: 5e2b922820ecb44706f6a628d5dcb60c8ad5df76
2024-06-10 09:01:09 +03:00
checksum = "2768de7e6ef19f59c5fd3c3ac207ef12b68a49f95e3172d67e4a04cfd992ca06"
use short commit SHA as version and mark non-release builds as dev (#295) V3_GIT_ORIGIN_REV_ID: 78475725003cd57790361caa8659c7a7146eacf2
2024-01-25 11:53:24 +03:00
dependencies = [
"safe-proc-macro2",
"safe-regex-compiler",
]
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
[[package]]
name = "same-file"
version = "1.0.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "93fc1dc3aaa9bfed95e02e6eadabb4baf7e3078b0bd1b4d7b6b0b68378900502"
dependencies = [
"winapi-util",
]
[[package]]
name = "schannel"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.1.23"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "fbc91545643bcf3a0bbb6569265615222618bdf33ce4ffbbd13c4bbd4c093534"
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
dependencies = [
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
"windows-sys 0.52.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
]
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
[[package]]
name = "schema"
Use v3.0.0 as the version number. (#999) ### What Updates the version number to `3.0.0`, now we're officially at GA. ### How I updated the version number, and also updated some dependencies. The `Cargo.lock` file was not up to date. V3_GIT_ORIGIN_REV_ID: 3e9b784c8ad856556193e56aee9fa607fa8ce19e
2024-08-21 17:02:43 +03:00
version = "3.0.0"
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
dependencies = [
"hasura-authn-core",
Add ability to override interpretations of roles (#660) This PR refactors the schema crate to enable overriding the interpretation of roles at runtime. By providing a `NamespacedGetter` that ignores roles entirely (i.e. `GDSNamespacedGetterAgnostic`) to schema generation functions it is possible to derive a GraphQL schema that ignores permissions and presets. This PR leaves back a few opportunities to improve code clarity, which I hope to address in follow-up PRs. For instance, it seems superfluous to make sense for generic code parametrised `<S: SchemaContext>` to carry around both a `S::Namespace` and a `S::NamespaceGetter`, when all that code could ever do with that `S::Namespace` value anyway is apply it to the `S::NamespaceGetter`. Taking this line of reasoning to its conclusion suggests that we can reduce the complexity of `trait SchemaContext` and its associated types and kit. --------- Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: c84555fd88279582670919faa5a62bbd00b714bd
2024-06-04 16:03:44 +03:00
"insta",
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
"json-ext",
"lang-graphql",
"metadata-resolve",
"open-dds",
"serde",
"serde_json",
"strum_macros",
"thiserror",
]
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
[[package]]
name = "schemars"
Remove duplicate JSON Schema entries (#692) <!-- Thank you for submitting this PR! :) --> ## Description When we generate a JSON schema via `schemars`, we end up with duplicate types in the schema, which get names like `ValueExpression2`, `Role2`, and so on. This isn't ideal, and seems to arise for two reasons: 1. The type is polymorphic, and is monomorphised in two ways, and thus the types can't be unified. 2. The type is monomorphic, but is used inside and outside of its home module. The first problem was fixed previously by splitting polymorphic types, but the second has proven to be a bit more work. This PR finally solves the problem by introducing a new library, `jsonschema-tidying`: * First, we search the definitions within the JSON schema for any whose names end in a number, such as `ValueExpression2` or `MetadataV2`. * Then, we look for types whose names match everything up to the final numeric digits, and discard any types for whom we can't find a match (so we keep `ValueExpression2` because `ValueExpression` exists, but discard `MetadataV2` because `MetadataV` does not). * Next, we remove the duplicate definition from the definitions map, potentially breaking links in both the schema _and_ the rest of the definitions map. * Finally, we traverse the entirety of the tree looking for any references to the duplicate entry, and replace them with references to the original entry. This PR has no direct user-facing change, however it _will_ have an effect on the docs generation code, which will hopefully result in tidier documentation. <!-- Questions to consider answering: 1. What user-facing changes are being made? 4. What are issues related to this PR? (Consider adding `(close #<issue-no>)` to the PR title) 5. What is the conceptual design behind this PR? 6. How can this PR be tested/verified? 7. Does the PR have limitations? 8. Does the PR introduce breaking changes? --> ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [ ] community-edition - [ ] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [x] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> _Replace with changelog entry_ <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: fe73acf7d9df0b9867852e673e53cb086e3725d3
2024-06-11 11:27:42 +03:00
version = "0.8.21"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Remove duplicate JSON Schema entries (#692) <!-- Thank you for submitting this PR! :) --> ## Description When we generate a JSON schema via `schemars`, we end up with duplicate types in the schema, which get names like `ValueExpression2`, `Role2`, and so on. This isn't ideal, and seems to arise for two reasons: 1. The type is polymorphic, and is monomorphised in two ways, and thus the types can't be unified. 2. The type is monomorphic, but is used inside and outside of its home module. The first problem was fixed previously by splitting polymorphic types, but the second has proven to be a bit more work. This PR finally solves the problem by introducing a new library, `jsonschema-tidying`: * First, we search the definitions within the JSON schema for any whose names end in a number, such as `ValueExpression2` or `MetadataV2`. * Then, we look for types whose names match everything up to the final numeric digits, and discard any types for whom we can't find a match (so we keep `ValueExpression2` because `ValueExpression` exists, but discard `MetadataV2` because `MetadataV` does not). * Next, we remove the duplicate definition from the definitions map, potentially breaking links in both the schema _and_ the rest of the definitions map. * Finally, we traverse the entirety of the tree looking for any references to the duplicate entry, and replace them with references to the original entry. This PR has no direct user-facing change, however it _will_ have an effect on the docs generation code, which will hopefully result in tidier documentation. <!-- Questions to consider answering: 1. What user-facing changes are being made? 4. What are issues related to this PR? (Consider adding `(close #<issue-no>)` to the PR title) 5. What is the conceptual design behind this PR? 6. How can this PR be tested/verified? 7. Does the PR have limitations? 8. Does the PR introduce breaking changes? --> ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [ ] community-edition - [ ] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [x] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> _Replace with changelog entry_ <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: fe73acf7d9df0b9867852e673e53cb086e3725d3
2024-06-11 11:27:42 +03:00
checksum = "09c024468a378b7e36765cd36702b7a90cc3cba11654f6685c8f233408e89e92"
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
dependencies = [
"dyn-clone",
"indexmap 1.9.3",
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"indexmap 2.4.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
"schemars_derive",
"serde",
"serde_json",
"smol_str",
Remove unused dependencies using `cargo machete`. (#413) `cargo machete` is a very useful tool that figures out when you aren't using a dependency. I have run this locally to remove unused dependencies. I've also added a CI job to make sure we catch these in the future. Sometimes it reports false positives, e.g. when a dependency isn't used directly but in macro-generated code (e.g. with `strum`). I have added `"ignored"` clauses to the `Cargo.toml` files where appropriate. V3_GIT_ORIGIN_REV_ID: ed015089b695cec8eeb03ce455d6dd3cd312a016
2024-03-28 12:16:54 +03:00
"url",
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
]
[[package]]
name = "schemars_derive"
Remove duplicate JSON Schema entries (#692) <!-- Thank you for submitting this PR! :) --> ## Description When we generate a JSON schema via `schemars`, we end up with duplicate types in the schema, which get names like `ValueExpression2`, `Role2`, and so on. This isn't ideal, and seems to arise for two reasons: 1. The type is polymorphic, and is monomorphised in two ways, and thus the types can't be unified. 2. The type is monomorphic, but is used inside and outside of its home module. The first problem was fixed previously by splitting polymorphic types, but the second has proven to be a bit more work. This PR finally solves the problem by introducing a new library, `jsonschema-tidying`: * First, we search the definitions within the JSON schema for any whose names end in a number, such as `ValueExpression2` or `MetadataV2`. * Then, we look for types whose names match everything up to the final numeric digits, and discard any types for whom we can't find a match (so we keep `ValueExpression2` because `ValueExpression` exists, but discard `MetadataV2` because `MetadataV` does not). * Next, we remove the duplicate definition from the definitions map, potentially breaking links in both the schema _and_ the rest of the definitions map. * Finally, we traverse the entirety of the tree looking for any references to the duplicate entry, and replace them with references to the original entry. This PR has no direct user-facing change, however it _will_ have an effect on the docs generation code, which will hopefully result in tidier documentation. <!-- Questions to consider answering: 1. What user-facing changes are being made? 4. What are issues related to this PR? (Consider adding `(close #<issue-no>)` to the PR title) 5. What is the conceptual design behind this PR? 6. How can this PR be tested/verified? 7. Does the PR have limitations? 8. Does the PR introduce breaking changes? --> ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [ ] community-edition - [ ] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [x] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> _Replace with changelog entry_ <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: fe73acf7d9df0b9867852e673e53cb086e3725d3
2024-06-11 11:27:42 +03:00
version = "0.8.21"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Remove duplicate JSON Schema entries (#692) <!-- Thank you for submitting this PR! :) --> ## Description When we generate a JSON schema via `schemars`, we end up with duplicate types in the schema, which get names like `ValueExpression2`, `Role2`, and so on. This isn't ideal, and seems to arise for two reasons: 1. The type is polymorphic, and is monomorphised in two ways, and thus the types can't be unified. 2. The type is monomorphic, but is used inside and outside of its home module. The first problem was fixed previously by splitting polymorphic types, but the second has proven to be a bit more work. This PR finally solves the problem by introducing a new library, `jsonschema-tidying`: * First, we search the definitions within the JSON schema for any whose names end in a number, such as `ValueExpression2` or `MetadataV2`. * Then, we look for types whose names match everything up to the final numeric digits, and discard any types for whom we can't find a match (so we keep `ValueExpression2` because `ValueExpression` exists, but discard `MetadataV2` because `MetadataV` does not). * Next, we remove the duplicate definition from the definitions map, potentially breaking links in both the schema _and_ the rest of the definitions map. * Finally, we traverse the entirety of the tree looking for any references to the duplicate entry, and replace them with references to the original entry. This PR has no direct user-facing change, however it _will_ have an effect on the docs generation code, which will hopefully result in tidier documentation. <!-- Questions to consider answering: 1. What user-facing changes are being made? 4. What are issues related to this PR? (Consider adding `(close #<issue-no>)` to the PR title) 5. What is the conceptual design behind this PR? 6. How can this PR be tested/verified? 7. Does the PR have limitations? 8. Does the PR introduce breaking changes? --> ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [ ] community-edition - [ ] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [x] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> _Replace with changelog entry_ <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: fe73acf7d9df0b9867852e673e53cb086e3725d3
2024-06-11 11:27:42 +03:00
checksum = "b1eee588578aff73f856ab961cd2f79e36bc45d7ded33a7562adba4667aecc0e"
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
dependencies = [
"proc-macro2",
"quote",
"serde_derive_internals",
Bump syn from 2.0.75 to 2.0.76 (#1017) Bumps [syn](https://github.com/dtolnay/syn) from 2.0.75 to 2.0.76. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/syn/releases">syn's releases</a>.</em></p> <blockquote> <h2>2.0.76</h2> <ul> <li>Enforce that tail call <code>become</code> keyword is followed by an expression (<a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/syn/commit/ef3e9c6dde79be7590fc90278772663ca31c1a73"><code>ef3e9c6</code></a> Release 2.0.76</li> <li><a href="https://github.com/dtolnay/syn/commit/8f7365ff9685c8ca9527c2de409204179a3efcdf"><code>8f7365f</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a> from dtolnay/tailcall</li> <li><a href="https://github.com/dtolnay/syn/commit/6cddd9ea714fe034466b4f02d3f7abb484c65ea0"><code>6cddd9e</code></a> Make tail call expr mandatory</li> <li>See full diff in <a href="https://github.com/dtolnay/syn/compare/2.0.75...2.0.76">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=syn&package-manager=cargo&previous-version=2.0.75&new-version=2.0.76)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d261ad30ffeb10034a80f9044504cb9d6c7c1ff7
2024-08-26 14:39:45 +03:00
"syn 2.0.76",
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
]
[[package]]
name = "scopeguard"
version = "1.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "94143f37725109f92c262ed2cf5e59bce7498c01bcc1502d7b9afe439a4e9f49"
[[package]]
name = "security-framework"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "2.11.1"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "897b2245f0b511c87893af39b033e5ca9cce68824c4d7e7630b5a1d339658d02"
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
dependencies = [
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
"bitflags 2.6.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
"core-foundation",
"core-foundation-sys",
"libc",
"security-framework-sys",
]
[[package]]
name = "security-framework-sys"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "2.11.1"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "75da29fe9b9b08fe9d6b22b5b4bcbc75d8db3aa31e639aa56bb62e9d46bfceaf"
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
dependencies = [
"core-foundation-sys",
"libc",
]
[[package]]
name = "semver"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "1.0.23"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "61697e0a1c7e512e84a621326239844a24d8207b4669b41bc18b32ea5cbf988b"
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
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
[[package]]
name = "seq-macro"
version = "0.3.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a3f0bf26fd526d2a95683cd0f87bf103b8539e2ca1ef48ce002d67aad59aa0b4"
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
[[package]]
name = "serde"
Bump serde from 1.0.208 to 1.0.209 (#1016) Bumps [serde](https://github.com/serde-rs/serde) from 1.0.208 to 1.0.209. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/serde-rs/serde/releases">serde's releases</a>.</em></p> <blockquote> <h2>v1.0.209</h2> <ul> <li>Fix deserialization of empty structs and empty tuples inside of untagged enums (<a href="https://redirect.github.com/serde-rs/serde/issues/2805">#2805</a>, thanks <a href="https://github.com/Mingun"><code>@​Mingun</code></a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/serde-rs/serde/commit/30752ac4ffdaa284606eda34055ad185e28c5499"><code>30752ac</code></a> Release 1.0.209</li> <li><a href="https://github.com/serde-rs/serde/commit/b84e6ca4f5fef69b3de985c586a07b1246f3eb9a"><code>b84e6ca</code></a> Improve wording of PR 2805 comments</li> <li><a href="https://github.com/serde-rs/serde/commit/87a2fb0f1a2774ea5bb20c0ed988b9ba57fc8166"><code>87a2fb0</code></a> Wrap comments from PR 2805 to 80 columns</li> <li><a href="https://github.com/serde-rs/serde/commit/9eaf7b9824f2082c50d17ad22b786322dc283a61"><code>9eaf7b9</code></a> Merge pull request <a href="https://redirect.github.com/serde-rs/serde/issues/2805">#2805</a> from Mingun/untagged-tests</li> <li><a href="https://github.com/serde-rs/serde/commit/7bde100237875d4f435de5ad90074b0479c37486"><code>7bde100</code></a> Replace MapRefDeserializer with value::MapDeserializer</li> <li><a href="https://github.com/serde-rs/serde/commit/da7fc795ee654252effa232a62a5a1e6d4f551ee"><code>da7fc79</code></a> Fix deserialization of empty struct variant in untagged enums</li> <li><a href="https://github.com/serde-rs/serde/commit/4c5fec1363d363f995375426f72db11c28f357c1"><code>4c5fec1</code></a> Test special cases that reaches SeqRefDeserializer::deserialize_any len==0 co...</li> <li><a href="https://github.com/serde-rs/serde/commit/6588b0ad3777f7ad930d68ab4b9ec5b9c25398e0"><code>6588b0a</code></a> Cover Content::Seq case in VariantRefDeserializer::struct_variant</li> <li><a href="https://github.com/serde-rs/serde/commit/0093f74cfee5ee3239514a7aad5fb44843eddcdd"><code>0093f74</code></a> Split test newtype_enum into four tests for each variant</li> <li><a href="https://github.com/serde-rs/serde/commit/171c6da57af712cfcf01c6c124b14cabfca364ba"><code>171c6da</code></a> Complete coverage of ContentRefDeserializer::deserialize_newtype_struct</li> <li>Additional commits viewable in <a href="https://github.com/serde-rs/serde/compare/v1.0.208...v1.0.209">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=serde&package-manager=cargo&previous-version=1.0.208&new-version=1.0.209)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: e8d93201cfdad039a62f4f55af5cdcd80dddbff9
2024-08-26 14:36:51 +03:00
version = "1.0.209"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump serde from 1.0.208 to 1.0.209 (#1016) Bumps [serde](https://github.com/serde-rs/serde) from 1.0.208 to 1.0.209. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/serde-rs/serde/releases">serde's releases</a>.</em></p> <blockquote> <h2>v1.0.209</h2> <ul> <li>Fix deserialization of empty structs and empty tuples inside of untagged enums (<a href="https://redirect.github.com/serde-rs/serde/issues/2805">#2805</a>, thanks <a href="https://github.com/Mingun"><code>@​Mingun</code></a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/serde-rs/serde/commit/30752ac4ffdaa284606eda34055ad185e28c5499"><code>30752ac</code></a> Release 1.0.209</li> <li><a href="https://github.com/serde-rs/serde/commit/b84e6ca4f5fef69b3de985c586a07b1246f3eb9a"><code>b84e6ca</code></a> Improve wording of PR 2805 comments</li> <li><a href="https://github.com/serde-rs/serde/commit/87a2fb0f1a2774ea5bb20c0ed988b9ba57fc8166"><code>87a2fb0</code></a> Wrap comments from PR 2805 to 80 columns</li> <li><a href="https://github.com/serde-rs/serde/commit/9eaf7b9824f2082c50d17ad22b786322dc283a61"><code>9eaf7b9</code></a> Merge pull request <a href="https://redirect.github.com/serde-rs/serde/issues/2805">#2805</a> from Mingun/untagged-tests</li> <li><a href="https://github.com/serde-rs/serde/commit/7bde100237875d4f435de5ad90074b0479c37486"><code>7bde100</code></a> Replace MapRefDeserializer with value::MapDeserializer</li> <li><a href="https://github.com/serde-rs/serde/commit/da7fc795ee654252effa232a62a5a1e6d4f551ee"><code>da7fc79</code></a> Fix deserialization of empty struct variant in untagged enums</li> <li><a href="https://github.com/serde-rs/serde/commit/4c5fec1363d363f995375426f72db11c28f357c1"><code>4c5fec1</code></a> Test special cases that reaches SeqRefDeserializer::deserialize_any len==0 co...</li> <li><a href="https://github.com/serde-rs/serde/commit/6588b0ad3777f7ad930d68ab4b9ec5b9c25398e0"><code>6588b0a</code></a> Cover Content::Seq case in VariantRefDeserializer::struct_variant</li> <li><a href="https://github.com/serde-rs/serde/commit/0093f74cfee5ee3239514a7aad5fb44843eddcdd"><code>0093f74</code></a> Split test newtype_enum into four tests for each variant</li> <li><a href="https://github.com/serde-rs/serde/commit/171c6da57af712cfcf01c6c124b14cabfca364ba"><code>171c6da</code></a> Complete coverage of ContentRefDeserializer::deserialize_newtype_struct</li> <li>Additional commits viewable in <a href="https://github.com/serde-rs/serde/compare/v1.0.208...v1.0.209">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=serde&package-manager=cargo&previous-version=1.0.208&new-version=1.0.209)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: e8d93201cfdad039a62f4f55af5cdcd80dddbff9
2024-08-26 14:36:51 +03:00
checksum = "99fce0ffe7310761ca6bf9faf5115afbc19688edd00171d81b1bb1b116c63e09"
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
dependencies = [
"serde_derive",
]
[[package]]
name = "serde_bytes"
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
version = "0.11.15"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
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
checksum = "387cc504cb06bb40a96c8e04e951fe01854cf6bc921053c954e4a606d9675c6a"
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
dependencies = [
"serde",
]
[[package]]
name = "serde_derive"
Bump serde from 1.0.208 to 1.0.209 (#1016) Bumps [serde](https://github.com/serde-rs/serde) from 1.0.208 to 1.0.209. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/serde-rs/serde/releases">serde's releases</a>.</em></p> <blockquote> <h2>v1.0.209</h2> <ul> <li>Fix deserialization of empty structs and empty tuples inside of untagged enums (<a href="https://redirect.github.com/serde-rs/serde/issues/2805">#2805</a>, thanks <a href="https://github.com/Mingun"><code>@​Mingun</code></a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/serde-rs/serde/commit/30752ac4ffdaa284606eda34055ad185e28c5499"><code>30752ac</code></a> Release 1.0.209</li> <li><a href="https://github.com/serde-rs/serde/commit/b84e6ca4f5fef69b3de985c586a07b1246f3eb9a"><code>b84e6ca</code></a> Improve wording of PR 2805 comments</li> <li><a href="https://github.com/serde-rs/serde/commit/87a2fb0f1a2774ea5bb20c0ed988b9ba57fc8166"><code>87a2fb0</code></a> Wrap comments from PR 2805 to 80 columns</li> <li><a href="https://github.com/serde-rs/serde/commit/9eaf7b9824f2082c50d17ad22b786322dc283a61"><code>9eaf7b9</code></a> Merge pull request <a href="https://redirect.github.com/serde-rs/serde/issues/2805">#2805</a> from Mingun/untagged-tests</li> <li><a href="https://github.com/serde-rs/serde/commit/7bde100237875d4f435de5ad90074b0479c37486"><code>7bde100</code></a> Replace MapRefDeserializer with value::MapDeserializer</li> <li><a href="https://github.com/serde-rs/serde/commit/da7fc795ee654252effa232a62a5a1e6d4f551ee"><code>da7fc79</code></a> Fix deserialization of empty struct variant in untagged enums</li> <li><a href="https://github.com/serde-rs/serde/commit/4c5fec1363d363f995375426f72db11c28f357c1"><code>4c5fec1</code></a> Test special cases that reaches SeqRefDeserializer::deserialize_any len==0 co...</li> <li><a href="https://github.com/serde-rs/serde/commit/6588b0ad3777f7ad930d68ab4b9ec5b9c25398e0"><code>6588b0a</code></a> Cover Content::Seq case in VariantRefDeserializer::struct_variant</li> <li><a href="https://github.com/serde-rs/serde/commit/0093f74cfee5ee3239514a7aad5fb44843eddcdd"><code>0093f74</code></a> Split test newtype_enum into four tests for each variant</li> <li><a href="https://github.com/serde-rs/serde/commit/171c6da57af712cfcf01c6c124b14cabfca364ba"><code>171c6da</code></a> Complete coverage of ContentRefDeserializer::deserialize_newtype_struct</li> <li>Additional commits viewable in <a href="https://github.com/serde-rs/serde/compare/v1.0.208...v1.0.209">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=serde&package-manager=cargo&previous-version=1.0.208&new-version=1.0.209)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: e8d93201cfdad039a62f4f55af5cdcd80dddbff9
2024-08-26 14:36:51 +03:00
version = "1.0.209"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump serde from 1.0.208 to 1.0.209 (#1016) Bumps [serde](https://github.com/serde-rs/serde) from 1.0.208 to 1.0.209. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/serde-rs/serde/releases">serde's releases</a>.</em></p> <blockquote> <h2>v1.0.209</h2> <ul> <li>Fix deserialization of empty structs and empty tuples inside of untagged enums (<a href="https://redirect.github.com/serde-rs/serde/issues/2805">#2805</a>, thanks <a href="https://github.com/Mingun"><code>@​Mingun</code></a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/serde-rs/serde/commit/30752ac4ffdaa284606eda34055ad185e28c5499"><code>30752ac</code></a> Release 1.0.209</li> <li><a href="https://github.com/serde-rs/serde/commit/b84e6ca4f5fef69b3de985c586a07b1246f3eb9a"><code>b84e6ca</code></a> Improve wording of PR 2805 comments</li> <li><a href="https://github.com/serde-rs/serde/commit/87a2fb0f1a2774ea5bb20c0ed988b9ba57fc8166"><code>87a2fb0</code></a> Wrap comments from PR 2805 to 80 columns</li> <li><a href="https://github.com/serde-rs/serde/commit/9eaf7b9824f2082c50d17ad22b786322dc283a61"><code>9eaf7b9</code></a> Merge pull request <a href="https://redirect.github.com/serde-rs/serde/issues/2805">#2805</a> from Mingun/untagged-tests</li> <li><a href="https://github.com/serde-rs/serde/commit/7bde100237875d4f435de5ad90074b0479c37486"><code>7bde100</code></a> Replace MapRefDeserializer with value::MapDeserializer</li> <li><a href="https://github.com/serde-rs/serde/commit/da7fc795ee654252effa232a62a5a1e6d4f551ee"><code>da7fc79</code></a> Fix deserialization of empty struct variant in untagged enums</li> <li><a href="https://github.com/serde-rs/serde/commit/4c5fec1363d363f995375426f72db11c28f357c1"><code>4c5fec1</code></a> Test special cases that reaches SeqRefDeserializer::deserialize_any len==0 co...</li> <li><a href="https://github.com/serde-rs/serde/commit/6588b0ad3777f7ad930d68ab4b9ec5b9c25398e0"><code>6588b0a</code></a> Cover Content::Seq case in VariantRefDeserializer::struct_variant</li> <li><a href="https://github.com/serde-rs/serde/commit/0093f74cfee5ee3239514a7aad5fb44843eddcdd"><code>0093f74</code></a> Split test newtype_enum into four tests for each variant</li> <li><a href="https://github.com/serde-rs/serde/commit/171c6da57af712cfcf01c6c124b14cabfca364ba"><code>171c6da</code></a> Complete coverage of ContentRefDeserializer::deserialize_newtype_struct</li> <li>Additional commits viewable in <a href="https://github.com/serde-rs/serde/compare/v1.0.208...v1.0.209">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=serde&package-manager=cargo&previous-version=1.0.208&new-version=1.0.209)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: e8d93201cfdad039a62f4f55af5cdcd80dddbff9
2024-08-26 14:36:51 +03:00
checksum = "a5831b979fd7b5439637af1752d535ff49f4860c0f341d1baeb6faf0f4242170"
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
dependencies = [
"proc-macro2",
"quote",
Bump syn from 2.0.75 to 2.0.76 (#1017) Bumps [syn](https://github.com/dtolnay/syn) from 2.0.75 to 2.0.76. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/syn/releases">syn's releases</a>.</em></p> <blockquote> <h2>2.0.76</h2> <ul> <li>Enforce that tail call <code>become</code> keyword is followed by an expression (<a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/syn/commit/ef3e9c6dde79be7590fc90278772663ca31c1a73"><code>ef3e9c6</code></a> Release 2.0.76</li> <li><a href="https://github.com/dtolnay/syn/commit/8f7365ff9685c8ca9527c2de409204179a3efcdf"><code>8f7365f</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a> from dtolnay/tailcall</li> <li><a href="https://github.com/dtolnay/syn/commit/6cddd9ea714fe034466b4f02d3f7abb484c65ea0"><code>6cddd9e</code></a> Make tail call expr mandatory</li> <li>See full diff in <a href="https://github.com/dtolnay/syn/compare/2.0.75...2.0.76">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=syn&package-manager=cargo&previous-version=2.0.75&new-version=2.0.76)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d261ad30ffeb10034a80f9044504cb9d6c7c1ff7
2024-08-26 14:39:45 +03:00
"syn 2.0.76",
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
]
[[package]]
name = "serde_derive_internals"
OpenDD types for new boolean expressions (#599) <!-- Thank you for submitting this PR! :) --> ## Description We have a new `BooleanExpressionType` metadata kind. This adds it, tests it can be parsed, but hides it from generated metadata and throws an error if one is actually used in the engine. V3_GIT_ORIGIN_REV_ID: 036b5fd9c32475d1c5a5e5e6321fb736fe6caefa
2024-05-21 12:28:02 +03:00
version = "0.29.1"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
OpenDD types for new boolean expressions (#599) <!-- Thank you for submitting this PR! :) --> ## Description We have a new `BooleanExpressionType` metadata kind. This adds it, tests it can be parsed, but hides it from generated metadata and throws an error if one is actually used in the engine. V3_GIT_ORIGIN_REV_ID: 036b5fd9c32475d1c5a5e5e6321fb736fe6caefa
2024-05-21 12:28:02 +03:00
checksum = "18d26a20a969b9e3fdf2fc2d9f21eda6c40e2de84c9408bb5d3b05d499aae711"
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
dependencies = [
"proc-macro2",
"quote",
Bump syn from 2.0.75 to 2.0.76 (#1017) Bumps [syn](https://github.com/dtolnay/syn) from 2.0.75 to 2.0.76. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/syn/releases">syn's releases</a>.</em></p> <blockquote> <h2>2.0.76</h2> <ul> <li>Enforce that tail call <code>become</code> keyword is followed by an expression (<a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/syn/commit/ef3e9c6dde79be7590fc90278772663ca31c1a73"><code>ef3e9c6</code></a> Release 2.0.76</li> <li><a href="https://github.com/dtolnay/syn/commit/8f7365ff9685c8ca9527c2de409204179a3efcdf"><code>8f7365f</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a> from dtolnay/tailcall</li> <li><a href="https://github.com/dtolnay/syn/commit/6cddd9ea714fe034466b4f02d3f7abb484c65ea0"><code>6cddd9e</code></a> Make tail call expr mandatory</li> <li>See full diff in <a href="https://github.com/dtolnay/syn/compare/2.0.75...2.0.76">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=syn&package-manager=cargo&previous-version=2.0.75&new-version=2.0.76)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d261ad30ffeb10034a80f9044504cb9d6c7c1ff7
2024-08-26 14:39:45 +03:00
"syn 2.0.76",
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
]
[[package]]
name = "serde_json"
Bump serde_json from 1.0.125 to 1.0.127 (#1015) Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.125 to 1.0.127. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/serde-rs/json/releases">serde_json's releases</a>.</em></p> <blockquote> <h2>1.0.127</h2> <ul> <li>Add more removal methods to OccupiedEntry (<a href="https://redirect.github.com/serde-rs/json/issues/1179">#1179</a>, thanks <a href="https://github.com/GREsau"><code>@​GREsau</code></a>)</li> </ul> <h2>1.0.126</h2> <ul> <li>Improve string parsing on targets that use 32-bit pointers but also have fast 64-bit integer arithmetic, such as aarch64-unknown-linux-gnu_ilp32 and x86_64-unknown-linux-gnux32 (<a href="https://redirect.github.com/serde-rs/json/issues/1182">#1182</a>, thanks <a href="https://github.com/CryZe"><code>@​CryZe</code></a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/serde-rs/json/commit/5ebf65cc480f90714c94f82099ca9161d80cbb10"><code>5ebf65c</code></a> Release 1.0.127</li> <li><a href="https://github.com/serde-rs/json/commit/f287a3b1a93ecb1a11cee31cb638bd9523a58add"><code>f287a3b</code></a> Merge pull request 1179 from GREsau/patch-1</li> <li><a href="https://github.com/serde-rs/json/commit/ec980b02774abbff12fd3e26b0a1582eb14dcef7"><code>ec980b0</code></a> Release 1.0.126</li> <li><a href="https://github.com/serde-rs/json/commit/e6282b0c479947805a33c7f167b1d19dd4c7ad4f"><code>e6282b0</code></a> Merge pull request <a href="https://redirect.github.com/serde-rs/json/issues/1184">#1184</a> from serde-rs/fastarithmetic</li> <li><a href="https://github.com/serde-rs/json/commit/ffc4a43453029cdc5603cfe3ef08414488fd45de"><code>ffc4a43</code></a> Improve cfg names for fast arithmetic</li> <li><a href="https://github.com/serde-rs/json/commit/4b1048d0ecc4d326d6657531689513f182a4f850"><code>4b1048d</code></a> Merge pull request <a href="https://redirect.github.com/serde-rs/json/issues/1183">#1183</a> from serde-rs/arithmetic</li> <li><a href="https://github.com/serde-rs/json/commit/f268173a9fb1f5f8a80f47af62b564525cf33764"><code>f268173</code></a> Unify chunk size choice between float and string parsing</li> <li><a href="https://github.com/serde-rs/json/commit/fec03769743c3f0ceb6b5b56d91321fdc856dff2"><code>fec0376</code></a> Merge pull request <a href="https://redirect.github.com/serde-rs/json/issues/1182">#1182</a> from CryZe/chunk-64bit</li> <li><a href="https://github.com/serde-rs/json/commit/3d837e1cc4a0f1df56ba6645c3b6d144768b5d9d"><code>3d837e1</code></a> Ensure the SWAR chunks are 64-bit in more cases</li> <li><a href="https://github.com/serde-rs/json/commit/11fc61c7af7b59ea80fb2ef7d78db94465dfbd54"><code>11fc61c</code></a> Add <code>OccupiedEntry::shift_remove()</code> and <code>swap_remove()</code></li> <li>Additional commits viewable in <a href="https://github.com/serde-rs/json/compare/1.0.125...1.0.127">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=serde_json&package-manager=cargo&previous-version=1.0.125&new-version=1.0.127)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: 81a7f8e72d54dcc1e37a6822d7e2f9181d61a9cf
2024-08-26 14:37:15 +03:00
version = "1.0.127"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump serde_json from 1.0.125 to 1.0.127 (#1015) Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.125 to 1.0.127. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/serde-rs/json/releases">serde_json's releases</a>.</em></p> <blockquote> <h2>1.0.127</h2> <ul> <li>Add more removal methods to OccupiedEntry (<a href="https://redirect.github.com/serde-rs/json/issues/1179">#1179</a>, thanks <a href="https://github.com/GREsau"><code>@​GREsau</code></a>)</li> </ul> <h2>1.0.126</h2> <ul> <li>Improve string parsing on targets that use 32-bit pointers but also have fast 64-bit integer arithmetic, such as aarch64-unknown-linux-gnu_ilp32 and x86_64-unknown-linux-gnux32 (<a href="https://redirect.github.com/serde-rs/json/issues/1182">#1182</a>, thanks <a href="https://github.com/CryZe"><code>@​CryZe</code></a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/serde-rs/json/commit/5ebf65cc480f90714c94f82099ca9161d80cbb10"><code>5ebf65c</code></a> Release 1.0.127</li> <li><a href="https://github.com/serde-rs/json/commit/f287a3b1a93ecb1a11cee31cb638bd9523a58add"><code>f287a3b</code></a> Merge pull request 1179 from GREsau/patch-1</li> <li><a href="https://github.com/serde-rs/json/commit/ec980b02774abbff12fd3e26b0a1582eb14dcef7"><code>ec980b0</code></a> Release 1.0.126</li> <li><a href="https://github.com/serde-rs/json/commit/e6282b0c479947805a33c7f167b1d19dd4c7ad4f"><code>e6282b0</code></a> Merge pull request <a href="https://redirect.github.com/serde-rs/json/issues/1184">#1184</a> from serde-rs/fastarithmetic</li> <li><a href="https://github.com/serde-rs/json/commit/ffc4a43453029cdc5603cfe3ef08414488fd45de"><code>ffc4a43</code></a> Improve cfg names for fast arithmetic</li> <li><a href="https://github.com/serde-rs/json/commit/4b1048d0ecc4d326d6657531689513f182a4f850"><code>4b1048d</code></a> Merge pull request <a href="https://redirect.github.com/serde-rs/json/issues/1183">#1183</a> from serde-rs/arithmetic</li> <li><a href="https://github.com/serde-rs/json/commit/f268173a9fb1f5f8a80f47af62b564525cf33764"><code>f268173</code></a> Unify chunk size choice between float and string parsing</li> <li><a href="https://github.com/serde-rs/json/commit/fec03769743c3f0ceb6b5b56d91321fdc856dff2"><code>fec0376</code></a> Merge pull request <a href="https://redirect.github.com/serde-rs/json/issues/1182">#1182</a> from CryZe/chunk-64bit</li> <li><a href="https://github.com/serde-rs/json/commit/3d837e1cc4a0f1df56ba6645c3b6d144768b5d9d"><code>3d837e1</code></a> Ensure the SWAR chunks are 64-bit in more cases</li> <li><a href="https://github.com/serde-rs/json/commit/11fc61c7af7b59ea80fb2ef7d78db94465dfbd54"><code>11fc61c</code></a> Add <code>OccupiedEntry::shift_remove()</code> and <code>swap_remove()</code></li> <li>Additional commits viewable in <a href="https://github.com/serde-rs/json/compare/1.0.125...1.0.127">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=serde_json&package-manager=cargo&previous-version=1.0.125&new-version=1.0.127)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: 81a7f8e72d54dcc1e37a6822d7e2f9181d61a9cf
2024-08-26 14:37:15 +03:00
checksum = "8043c06d9f82bd7271361ed64f415fe5e12a77fdb52e573e7f06a516dea329ad"
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
dependencies = [
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"indexmap 2.4.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
"itoa",
Bump serde_json from 1.0.120 to 1.0.122 (#922) Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.120 to 1.0.122. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/serde-rs/json/releases">serde_json's releases</a>.</em></p> <blockquote> <h2>v1.0.121</h2> <ul> <li>Optimize position search in error path (<a href="https://redirect.github.com/serde-rs/json/issues/1160">#1160</a>, thanks <a href="https://github.com/purplesyringa"><code>@​purplesyringa</code></a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/serde-rs/json/commit/54381d6fee21cb05439937a0f5f286177c21d3f6"><code>54381d6</code></a> Release 1.0.122</li> <li><a href="https://github.com/serde-rs/json/commit/16fb6e0b853590ed065f2a1ce4450a71a433717b"><code>16fb6e0</code></a> Work around buggy rust-analyzer behavior</li> <li><a href="https://github.com/serde-rs/json/commit/49d7d6626f34d38f3bac5ccedffeaec169e02db1"><code>49d7d66</code></a> Merge pull request <a href="https://redirect.github.com/serde-rs/json/issues/1166">#1166</a> from dtolnay/allocvec</li> <li><a href="https://github.com/serde-rs/json/commit/6827c7b3c582a8fe30beb8ddb9e2446bfc391ea7"><code>6827c7b</code></a> Fix json! invocations when std prelude is not in scope</li> <li><a href="https://github.com/serde-rs/json/commit/611b2a4fb671b19c3ef45fc5b6455f906888c89f"><code>611b2a4</code></a> Merge pull request <a href="https://redirect.github.com/serde-rs/json/issues/1165">#1165</a> from serde-rs/jsonmac</li> <li><a href="https://github.com/serde-rs/json/commit/7633cb7f0511d7e4962f5a378171cc1ea0a0820d"><code>7633cb7</code></a> Eliminate local_inner_macros in favor of non-ident macro paths</li> <li><a href="https://github.com/serde-rs/json/commit/eca2658a22cb39952783cb6914eb18242659f66a"><code>eca2658</code></a> Release 1.0.121</li> <li><a href="https://github.com/serde-rs/json/commit/b0d678cfb473386830d559b6ab255d9e21ba39c5"><code>b0d678c</code></a> Merge pull request <a href="https://redirect.github.com/serde-rs/json/issues/1160">#1160</a> from iex-rs/efficient-position</li> <li><a href="https://github.com/serde-rs/json/commit/b1edc7d13f72880fd0ac569403a409e5f7961d5f"><code>b1edc7d</code></a> Optimize position search in error path</li> <li><a href="https://github.com/serde-rs/json/commit/40dd7f5e862436f02471fe076f3486c55e472bc2"><code>40dd7f5</code></a> Merge pull request <a href="https://redirect.github.com/serde-rs/json/issues/1159">#1159</a> from iex-rs/fix-recursion</li> <li>Additional commits viewable in <a href="https://github.com/serde-rs/json/compare/v1.0.120...v1.0.122">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=serde_json&package-manager=cargo&previous-version=1.0.120&new-version=1.0.122)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: 92ae4524a7ffab84c6b55097453b2f1484a0c747
2024-08-02 12:20:52 +03:00
"memchr",
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
"ryu",
"serde",
]
[[package]]
name = "serde_path_to_error"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.1.16"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "af99884400da37c88f5e9146b7f1fd0fbcae8f6eec4e9da38b67d05486f814a6"
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
dependencies = [
"itoa",
"serde",
]
[[package]]
name = "serde_urlencoded"
version = "0.7.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d3491c14715ca2294c4d6a88f15e84739788c1d030eed8c110436aafdaa2f3fd"
dependencies = [
"form_urlencoded",
"itoa",
"ryu",
"serde",
]
Bump serde_with from 2.3.3 to 3.8.1 (#549) V3_GIT_ORIGIN_REV_ID: 73f08cd518591be471b8825dbb84d368c45f5f2c
2024-05-07 11:42:16 +03:00
[[package]]
name = "serde_with"
Bump serde_with from 3.8.3 to 3.9.0 (#926) Bumps [serde_with](https://github.com/jonasbb/serde_with) from 3.8.3 to 3.9.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/jonasbb/serde_with/releases">serde_with's releases</a>.</em></p> <blockquote> <h2>serde_with v3.9.0</h2> <h3>Added</h3> <ul> <li> <p>Deserialize a map` and skip all elements failing to deserialize by <a href="https://github.com/johnmave126"><code>@​johnmave126</code></a> (<a href="https://redirect.github.com/jonasbb/serde_with/issues/763">#763</a>)</p> <p><code>MapSkipError</code> acts like a map (<code>HashMap</code>/<code>BTreeMap</code>), but keys or values that fail to deserialize, like are ignored.</p> <p>For formats with heterogeneously typed maps, we can collect only the elements where both key and value are deserializable. This is also useful in conjunction to <code>#[serde(flatten)]</code> to ignore some entries when capturing additional fields.</p> <pre lang="text"><code>// JSON &quot;value&quot;: {&quot;0&quot;: &quot;v0&quot;, &quot;5&quot;: &quot;v5&quot;, &quot;str&quot;: &quot;str&quot;, &quot;10&quot;: 2}, <p>// Rust #[serde_as(as = &quot;MapSkipError&lt;DisplayFromStr, _&gt;&quot;)] value: BTreeMap&lt;u32, String&gt;,</p> <p>// Only deserializes entries with a numerical key and a string value, i.e., {0 =&gt; &quot;v0&quot;, 5 =&gt; &quot;v5&quot;} </code></pre></p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/jonasbb/serde_with/commit/c3e489f4e571fadad9e656c28332b3708bd8cf0e"><code>c3e489f</code></a> Bump version to 3.9.0 (<a href="https://redirect.github.com/jonasbb/serde_with/issues/770">#770</a>)</li> <li><a href="https://github.com/jonasbb/serde_with/commit/57ad8778c46c0dd689002930430e3f994af1ebb1"><code>57ad877</code></a> Bump version to 3.9.0</li> <li><a href="https://github.com/jonasbb/serde_with/commit/d038657903639832437abcceca546395a0283034"><code>d038657</code></a> Implement <code>MapSkipError</code>, analogous to <code>VecSkipError</code>, but for map-like data ...</li> <li><a href="https://github.com/jonasbb/serde_with/commit/aaa0a2958917da51867ec90398d95826f8ebd717"><code>aaa0a29</code></a> Update serde_with/src/guide/serde_as_transformations.md</li> <li><a href="https://github.com/jonasbb/serde_with/commit/17dec1112b55bce9f7742ecf9d3414dcc089d26d"><code>17dec11</code></a> Add tests to make sure syntax errors are not suppressed.</li> <li><a href="https://github.com/jonasbb/serde_with/commit/97543d0c2d7588d9c2855c329bcc8c2b1107a404"><code>97543d0</code></a> Implement MapSkipError, skipping un-deserializable entries.</li> <li><a href="https://github.com/jonasbb/serde_with/commit/bf6724d2c09f35fb0ff917856829acf5362fed78"><code>bf6724d</code></a> Move VecSkipError to a separate file, preparing for MapSkipError</li> <li><a href="https://github.com/jonasbb/serde_with/commit/31e9172cabefd31b3cca12d24139e416e75ab6d8"><code>31e9172</code></a> Fix dead code warning by correcting a typo (<a href="https://redirect.github.com/jonasbb/serde_with/issues/769">#769</a>)</li> <li><a href="https://github.com/jonasbb/serde_with/commit/f5b2626307f7fb49275232a7f1925bfb5a200a37"><code>f5b2626</code></a> Fix dead code warnings in tests</li> <li><a href="https://github.com/jonasbb/serde_with/commit/4ad4a1b4e9088219b7877d64aa225e6d352298e2"><code>4ad4a1b</code></a> Fix dead code warning by correcting a typo</li> <li>See full diff in <a href="https://github.com/jonasbb/serde_with/compare/v3.8.3...v3.9.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=serde_with&package-manager=cargo&previous-version=3.8.3&new-version=3.9.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: ec2c5b357a416492e2b8033138aa83075023089d
2024-08-05 08:24:52 +03:00
version = "3.9.0"
Bump serde_with from 2.3.3 to 3.8.1 (#549) V3_GIT_ORIGIN_REV_ID: 73f08cd518591be471b8825dbb84d368c45f5f2c
2024-05-07 11:42:16 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump serde_with from 3.8.3 to 3.9.0 (#926) Bumps [serde_with](https://github.com/jonasbb/serde_with) from 3.8.3 to 3.9.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/jonasbb/serde_with/releases">serde_with's releases</a>.</em></p> <blockquote> <h2>serde_with v3.9.0</h2> <h3>Added</h3> <ul> <li> <p>Deserialize a map` and skip all elements failing to deserialize by <a href="https://github.com/johnmave126"><code>@​johnmave126</code></a> (<a href="https://redirect.github.com/jonasbb/serde_with/issues/763">#763</a>)</p> <p><code>MapSkipError</code> acts like a map (<code>HashMap</code>/<code>BTreeMap</code>), but keys or values that fail to deserialize, like are ignored.</p> <p>For formats with heterogeneously typed maps, we can collect only the elements where both key and value are deserializable. This is also useful in conjunction to <code>#[serde(flatten)]</code> to ignore some entries when capturing additional fields.</p> <pre lang="text"><code>// JSON &quot;value&quot;: {&quot;0&quot;: &quot;v0&quot;, &quot;5&quot;: &quot;v5&quot;, &quot;str&quot;: &quot;str&quot;, &quot;10&quot;: 2}, <p>// Rust #[serde_as(as = &quot;MapSkipError&lt;DisplayFromStr, _&gt;&quot;)] value: BTreeMap&lt;u32, String&gt;,</p> <p>// Only deserializes entries with a numerical key and a string value, i.e., {0 =&gt; &quot;v0&quot;, 5 =&gt; &quot;v5&quot;} </code></pre></p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/jonasbb/serde_with/commit/c3e489f4e571fadad9e656c28332b3708bd8cf0e"><code>c3e489f</code></a> Bump version to 3.9.0 (<a href="https://redirect.github.com/jonasbb/serde_with/issues/770">#770</a>)</li> <li><a href="https://github.com/jonasbb/serde_with/commit/57ad8778c46c0dd689002930430e3f994af1ebb1"><code>57ad877</code></a> Bump version to 3.9.0</li> <li><a href="https://github.com/jonasbb/serde_with/commit/d038657903639832437abcceca546395a0283034"><code>d038657</code></a> Implement <code>MapSkipError</code>, analogous to <code>VecSkipError</code>, but for map-like data ...</li> <li><a href="https://github.com/jonasbb/serde_with/commit/aaa0a2958917da51867ec90398d95826f8ebd717"><code>aaa0a29</code></a> Update serde_with/src/guide/serde_as_transformations.md</li> <li><a href="https://github.com/jonasbb/serde_with/commit/17dec1112b55bce9f7742ecf9d3414dcc089d26d"><code>17dec11</code></a> Add tests to make sure syntax errors are not suppressed.</li> <li><a href="https://github.com/jonasbb/serde_with/commit/97543d0c2d7588d9c2855c329bcc8c2b1107a404"><code>97543d0</code></a> Implement MapSkipError, skipping un-deserializable entries.</li> <li><a href="https://github.com/jonasbb/serde_with/commit/bf6724d2c09f35fb0ff917856829acf5362fed78"><code>bf6724d</code></a> Move VecSkipError to a separate file, preparing for MapSkipError</li> <li><a href="https://github.com/jonasbb/serde_with/commit/31e9172cabefd31b3cca12d24139e416e75ab6d8"><code>31e9172</code></a> Fix dead code warning by correcting a typo (<a href="https://redirect.github.com/jonasbb/serde_with/issues/769">#769</a>)</li> <li><a href="https://github.com/jonasbb/serde_with/commit/f5b2626307f7fb49275232a7f1925bfb5a200a37"><code>f5b2626</code></a> Fix dead code warnings in tests</li> <li><a href="https://github.com/jonasbb/serde_with/commit/4ad4a1b4e9088219b7877d64aa225e6d352298e2"><code>4ad4a1b</code></a> Fix dead code warning by correcting a typo</li> <li>See full diff in <a href="https://github.com/jonasbb/serde_with/compare/v3.8.3...v3.9.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=serde_with&package-manager=cargo&previous-version=3.8.3&new-version=3.9.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: ec2c5b357a416492e2b8033138aa83075023089d
2024-08-05 08:24:52 +03:00
checksum = "69cecfa94848272156ea67b2b1a53f20fc7bc638c4a46d2f8abde08f05f4b857"
Bump serde_with from 2.3.3 to 3.8.1 (#549) V3_GIT_ORIGIN_REV_ID: 73f08cd518591be471b8825dbb84d368c45f5f2c
2024-05-07 11:42:16 +03:00
dependencies = [
"base64 0.22.1",
"chrono",
"hex",
"indexmap 1.9.3",
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"indexmap 2.4.0",
Bump serde_with from 2.3.3 to 3.8.1 (#549) V3_GIT_ORIGIN_REV_ID: 73f08cd518591be471b8825dbb84d368c45f5f2c
2024-05-07 11:42:16 +03:00
"serde",
"serde_derive",
"serde_json",
upgrade to ndc v0.1.3 (#629) Upgrade engine to ndc v0.1.3. Also updates custom connector. --------- Co-authored-by: Samir Talwar <samir.talwar@hasura.io> Co-authored-by: Gil Mizrahi <gil@hasura.io> V3_GIT_ORIGIN_REV_ID: 80959d4702ef785b7809d6432e092b6477ef88c1
2024-06-05 13:15:25 +03:00
"serde_with_macros",
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
"time",
]
Bump serde_with from 2.3.3 to 3.8.1 (#549) V3_GIT_ORIGIN_REV_ID: 73f08cd518591be471b8825dbb84d368c45f5f2c
2024-05-07 11:42:16 +03:00
[[package]]
name = "serde_with_macros"
Bump serde_with from 3.8.3 to 3.9.0 (#926) Bumps [serde_with](https://github.com/jonasbb/serde_with) from 3.8.3 to 3.9.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/jonasbb/serde_with/releases">serde_with's releases</a>.</em></p> <blockquote> <h2>serde_with v3.9.0</h2> <h3>Added</h3> <ul> <li> <p>Deserialize a map` and skip all elements failing to deserialize by <a href="https://github.com/johnmave126"><code>@​johnmave126</code></a> (<a href="https://redirect.github.com/jonasbb/serde_with/issues/763">#763</a>)</p> <p><code>MapSkipError</code> acts like a map (<code>HashMap</code>/<code>BTreeMap</code>), but keys or values that fail to deserialize, like are ignored.</p> <p>For formats with heterogeneously typed maps, we can collect only the elements where both key and value are deserializable. This is also useful in conjunction to <code>#[serde(flatten)]</code> to ignore some entries when capturing additional fields.</p> <pre lang="text"><code>// JSON &quot;value&quot;: {&quot;0&quot;: &quot;v0&quot;, &quot;5&quot;: &quot;v5&quot;, &quot;str&quot;: &quot;str&quot;, &quot;10&quot;: 2}, <p>// Rust #[serde_as(as = &quot;MapSkipError&lt;DisplayFromStr, _&gt;&quot;)] value: BTreeMap&lt;u32, String&gt;,</p> <p>// Only deserializes entries with a numerical key and a string value, i.e., {0 =&gt; &quot;v0&quot;, 5 =&gt; &quot;v5&quot;} </code></pre></p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/jonasbb/serde_with/commit/c3e489f4e571fadad9e656c28332b3708bd8cf0e"><code>c3e489f</code></a> Bump version to 3.9.0 (<a href="https://redirect.github.com/jonasbb/serde_with/issues/770">#770</a>)</li> <li><a href="https://github.com/jonasbb/serde_with/commit/57ad8778c46c0dd689002930430e3f994af1ebb1"><code>57ad877</code></a> Bump version to 3.9.0</li> <li><a href="https://github.com/jonasbb/serde_with/commit/d038657903639832437abcceca546395a0283034"><code>d038657</code></a> Implement <code>MapSkipError</code>, analogous to <code>VecSkipError</code>, but for map-like data ...</li> <li><a href="https://github.com/jonasbb/serde_with/commit/aaa0a2958917da51867ec90398d95826f8ebd717"><code>aaa0a29</code></a> Update serde_with/src/guide/serde_as_transformations.md</li> <li><a href="https://github.com/jonasbb/serde_with/commit/17dec1112b55bce9f7742ecf9d3414dcc089d26d"><code>17dec11</code></a> Add tests to make sure syntax errors are not suppressed.</li> <li><a href="https://github.com/jonasbb/serde_with/commit/97543d0c2d7588d9c2855c329bcc8c2b1107a404"><code>97543d0</code></a> Implement MapSkipError, skipping un-deserializable entries.</li> <li><a href="https://github.com/jonasbb/serde_with/commit/bf6724d2c09f35fb0ff917856829acf5362fed78"><code>bf6724d</code></a> Move VecSkipError to a separate file, preparing for MapSkipError</li> <li><a href="https://github.com/jonasbb/serde_with/commit/31e9172cabefd31b3cca12d24139e416e75ab6d8"><code>31e9172</code></a> Fix dead code warning by correcting a typo (<a href="https://redirect.github.com/jonasbb/serde_with/issues/769">#769</a>)</li> <li><a href="https://github.com/jonasbb/serde_with/commit/f5b2626307f7fb49275232a7f1925bfb5a200a37"><code>f5b2626</code></a> Fix dead code warnings in tests</li> <li><a href="https://github.com/jonasbb/serde_with/commit/4ad4a1b4e9088219b7877d64aa225e6d352298e2"><code>4ad4a1b</code></a> Fix dead code warning by correcting a typo</li> <li>See full diff in <a href="https://github.com/jonasbb/serde_with/compare/v3.8.3...v3.9.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=serde_with&package-manager=cargo&previous-version=3.8.3&new-version=3.9.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: ec2c5b357a416492e2b8033138aa83075023089d
2024-08-05 08:24:52 +03:00
version = "3.9.0"
Bump serde_with from 2.3.3 to 3.8.1 (#549) V3_GIT_ORIGIN_REV_ID: 73f08cd518591be471b8825dbb84d368c45f5f2c
2024-05-07 11:42:16 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump serde_with from 3.8.3 to 3.9.0 (#926) Bumps [serde_with](https://github.com/jonasbb/serde_with) from 3.8.3 to 3.9.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/jonasbb/serde_with/releases">serde_with's releases</a>.</em></p> <blockquote> <h2>serde_with v3.9.0</h2> <h3>Added</h3> <ul> <li> <p>Deserialize a map` and skip all elements failing to deserialize by <a href="https://github.com/johnmave126"><code>@​johnmave126</code></a> (<a href="https://redirect.github.com/jonasbb/serde_with/issues/763">#763</a>)</p> <p><code>MapSkipError</code> acts like a map (<code>HashMap</code>/<code>BTreeMap</code>), but keys or values that fail to deserialize, like are ignored.</p> <p>For formats with heterogeneously typed maps, we can collect only the elements where both key and value are deserializable. This is also useful in conjunction to <code>#[serde(flatten)]</code> to ignore some entries when capturing additional fields.</p> <pre lang="text"><code>// JSON &quot;value&quot;: {&quot;0&quot;: &quot;v0&quot;, &quot;5&quot;: &quot;v5&quot;, &quot;str&quot;: &quot;str&quot;, &quot;10&quot;: 2}, <p>// Rust #[serde_as(as = &quot;MapSkipError&lt;DisplayFromStr, _&gt;&quot;)] value: BTreeMap&lt;u32, String&gt;,</p> <p>// Only deserializes entries with a numerical key and a string value, i.e., {0 =&gt; &quot;v0&quot;, 5 =&gt; &quot;v5&quot;} </code></pre></p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/jonasbb/serde_with/commit/c3e489f4e571fadad9e656c28332b3708bd8cf0e"><code>c3e489f</code></a> Bump version to 3.9.0 (<a href="https://redirect.github.com/jonasbb/serde_with/issues/770">#770</a>)</li> <li><a href="https://github.com/jonasbb/serde_with/commit/57ad8778c46c0dd689002930430e3f994af1ebb1"><code>57ad877</code></a> Bump version to 3.9.0</li> <li><a href="https://github.com/jonasbb/serde_with/commit/d038657903639832437abcceca546395a0283034"><code>d038657</code></a> Implement <code>MapSkipError</code>, analogous to <code>VecSkipError</code>, but for map-like data ...</li> <li><a href="https://github.com/jonasbb/serde_with/commit/aaa0a2958917da51867ec90398d95826f8ebd717"><code>aaa0a29</code></a> Update serde_with/src/guide/serde_as_transformations.md</li> <li><a href="https://github.com/jonasbb/serde_with/commit/17dec1112b55bce9f7742ecf9d3414dcc089d26d"><code>17dec11</code></a> Add tests to make sure syntax errors are not suppressed.</li> <li><a href="https://github.com/jonasbb/serde_with/commit/97543d0c2d7588d9c2855c329bcc8c2b1107a404"><code>97543d0</code></a> Implement MapSkipError, skipping un-deserializable entries.</li> <li><a href="https://github.com/jonasbb/serde_with/commit/bf6724d2c09f35fb0ff917856829acf5362fed78"><code>bf6724d</code></a> Move VecSkipError to a separate file, preparing for MapSkipError</li> <li><a href="https://github.com/jonasbb/serde_with/commit/31e9172cabefd31b3cca12d24139e416e75ab6d8"><code>31e9172</code></a> Fix dead code warning by correcting a typo (<a href="https://redirect.github.com/jonasbb/serde_with/issues/769">#769</a>)</li> <li><a href="https://github.com/jonasbb/serde_with/commit/f5b2626307f7fb49275232a7f1925bfb5a200a37"><code>f5b2626</code></a> Fix dead code warnings in tests</li> <li><a href="https://github.com/jonasbb/serde_with/commit/4ad4a1b4e9088219b7877d64aa225e6d352298e2"><code>4ad4a1b</code></a> Fix dead code warning by correcting a typo</li> <li>See full diff in <a href="https://github.com/jonasbb/serde_with/compare/v3.8.3...v3.9.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=serde_with&package-manager=cargo&previous-version=3.8.3&new-version=3.9.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: ec2c5b357a416492e2b8033138aa83075023089d
2024-08-05 08:24:52 +03:00
checksum = "a8fee4991ef4f274617a51ad4af30519438dacb2f56ac773b08a1922ff743350"
Bump serde_with from 2.3.3 to 3.8.1 (#549) V3_GIT_ORIGIN_REV_ID: 73f08cd518591be471b8825dbb84d368c45f5f2c
2024-05-07 11:42:16 +03:00
dependencies = [
Use `syn` v2 in our own macros. (#574) This upgrades `darling` and `schemars` too, so they also use `syn` v2. V3_GIT_ORIGIN_REV_ID: 731160389115dfa079fb1e13e831204d278f5a40
2024-05-14 10:49:52 +03:00
"darling",
Bump serde_with from 2.3.3 to 3.8.1 (#549) V3_GIT_ORIGIN_REV_ID: 73f08cd518591be471b8825dbb84d368c45f5f2c
2024-05-07 11:42:16 +03:00
"proc-macro2",
"quote",
Bump syn from 2.0.75 to 2.0.76 (#1017) Bumps [syn](https://github.com/dtolnay/syn) from 2.0.75 to 2.0.76. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/syn/releases">syn's releases</a>.</em></p> <blockquote> <h2>2.0.76</h2> <ul> <li>Enforce that tail call <code>become</code> keyword is followed by an expression (<a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/syn/commit/ef3e9c6dde79be7590fc90278772663ca31c1a73"><code>ef3e9c6</code></a> Release 2.0.76</li> <li><a href="https://github.com/dtolnay/syn/commit/8f7365ff9685c8ca9527c2de409204179a3efcdf"><code>8f7365f</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a> from dtolnay/tailcall</li> <li><a href="https://github.com/dtolnay/syn/commit/6cddd9ea714fe034466b4f02d3f7abb484c65ea0"><code>6cddd9e</code></a> Make tail call expr mandatory</li> <li>See full diff in <a href="https://github.com/dtolnay/syn/compare/2.0.75...2.0.76">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=syn&package-manager=cargo&previous-version=2.0.75&new-version=2.0.76)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d261ad30ffeb10034a80f9044504cb9d6c7c1ff7
2024-08-26 14:39:45 +03:00
"syn 2.0.76",
Bump serde_with from 2.3.3 to 3.8.1 (#549) V3_GIT_ORIGIN_REV_ID: 73f08cd518591be471b8825dbb84d368c45f5f2c
2024-05-07 11:42:16 +03:00
]
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
[[package]]
name = "sha2"
version = "0.9.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4d58a1e1bf39749807d89cf2d98ac2dfa0ff1cb3faa38fbb64dd88ac8013d800"
dependencies = [
add field arguments in schema and execution (#695) ### TODO - [x] Validate the presence of arguments in the data connector schema - [x] Add test for IR - [x] Add test using custom connector ## Description JIRA: https://hasurahq.atlassian.net/browse/V3ENGINE-148 This is part 2 of the field arguments. This will add the field arguments to the graphql schema and also handles the execution part. ![image](https://github.com/hasura/v3-engine/assets/85472423/c8f55d70-6539-42ef-ab5a-91b74e5699e2) ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> Add support for field arguments <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> --------- Co-authored-by: Anon Ray <ecthiender@users.noreply.github.com> Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: ea06b896feaca30419f81cd070fd4cfd608ef35b
2024-06-19 11:14:24 +03:00
"block-buffer 0.9.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
"cfg-if",
"cpufeatures",
add field arguments in schema and execution (#695) ### TODO - [x] Validate the presence of arguments in the data connector schema - [x] Add test for IR - [x] Add test using custom connector ## Description JIRA: https://hasurahq.atlassian.net/browse/V3ENGINE-148 This is part 2 of the field arguments. This will add the field arguments to the graphql schema and also handles the execution part. ![image](https://github.com/hasura/v3-engine/assets/85472423/c8f55d70-6539-42ef-ab5a-91b74e5699e2) ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> Add support for field arguments <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> --------- Co-authored-by: Anon Ray <ecthiender@users.noreply.github.com> Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: ea06b896feaca30419f81cd070fd4cfd608ef35b
2024-06-19 11:14:24 +03:00
"digest 0.9.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
"opaque-debug",
]
add field arguments in schema and execution (#695) ### TODO - [x] Validate the presence of arguments in the data connector schema - [x] Add test for IR - [x] Add test using custom connector ## Description JIRA: https://hasurahq.atlassian.net/browse/V3ENGINE-148 This is part 2 of the field arguments. This will add the field arguments to the graphql schema and also handles the execution part. ![image](https://github.com/hasura/v3-engine/assets/85472423/c8f55d70-6539-42ef-ab5a-91b74e5699e2) ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> Add support for field arguments <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> --------- Co-authored-by: Anon Ray <ecthiender@users.noreply.github.com> Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: ea06b896feaca30419f81cd070fd4cfd608ef35b
2024-06-19 11:14:24 +03:00
[[package]]
name = "sha2"
version = "0.10.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "793db75ad2bcafc3ffa7c68b215fee268f537982cd901d132f89c6343f3a3dc8"
dependencies = [
"cfg-if",
"cpufeatures",
"digest 0.10.7",
]
support OpenTelemetry zipkin propagator (#466) Support both W3C and Zipkin B3 headers and connectors will prefer B3 headers to extract traces because Cloud Run doesn't respect those headers. V3_GIT_ORIGIN_REV_ID: 1471b848e71d87420bc75b9adee60951f306c856
2024-04-16 17:55:54 +03:00
[[package]]
name = "sharded-slab"
version = "0.1.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f40ca3c46823713e0d4209592e8d6e826aa57e928f09752619fc696c499637f6"
dependencies = [
"lazy_static",
]
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
[[package]]
name = "shlex"
version = "1.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0fda2ff0d084019ba4d7c6f371c95d8fd75ce3524c3cb8fb653a3023f6323e64"
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
[[package]]
name = "signal-hook-registry"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "1.4.2"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "a9e9e0b4211b72e7b8b6e85c807d36c212bdb33ea8587f7569562a84df5465b1"
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
dependencies = [
"libc",
]
[[package]]
name = "signature"
version = "1.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f2807892cfa58e081aa1f1111391c7a0649d4fa127a4ffbe34bcbfb35a1171a4"
dependencies = [
add field arguments in schema and execution (#695) ### TODO - [x] Validate the presence of arguments in the data connector schema - [x] Add test for IR - [x] Add test using custom connector ## Description JIRA: https://hasurahq.atlassian.net/browse/V3ENGINE-148 This is part 2 of the field arguments. This will add the field arguments to the graphql schema and also handles the execution part. ![image](https://github.com/hasura/v3-engine/assets/85472423/c8f55d70-6539-42ef-ab5a-91b74e5699e2) ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> Add support for field arguments <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> --------- Co-authored-by: Anon Ray <ecthiender@users.noreply.github.com> Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: ea06b896feaca30419f81cd070fd4cfd608ef35b
2024-06-19 11:14:24 +03:00
"digest 0.9.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
"rand_core",
]
[[package]]
name = "similar"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "2.6.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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "1de1d4f81173b03af4c0cbed3c898f6bff5b870e4a7f5d6f4057d62a7a4b686e"
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
dependencies = [
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"bstr",
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
"unicode-segmentation",
]
[[package]]
name = "similar-asserts"
version = "1.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e041bb827d1bfca18f213411d51b665309f1afb37a04a5d1464530e13779fc0f"
dependencies = [
"console",
"similar",
]
[[package]]
name = "simple_asn1"
version = "0.6.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "adc4e5204eb1910f40f9cfa375f6f05b68c3abac4b6fd879c8ff5e7ae8a0a085"
dependencies = [
"num-bigint",
"num-traits",
"thiserror",
"time",
]
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
[[package]]
name = "siphasher"
version = "0.3.11"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "38b58827f4464d87d377d175e90bf58eb00fd8716ff0a62f80356b5e61555d0d"
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
[[package]]
name = "slab"
version = "0.4.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8f92a496fb766b417c996b9c5e57daf2f7ad3b0bebe1ccfca4856390e3d3bb67"
dependencies = [
"autocfg",
]
[[package]]
name = "smallvec"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "1.13.2"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "3c5e1a9a646d36c3599cd173a41282daf47c44583ad367b8e6837255952e5c67"
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
[[package]]
name = "smol_str"
version = "0.1.24"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fad6c857cbab2627dcf01ec85a623ca4e7dcb5691cbaa3d7fb7653671f0d09c9"
dependencies = [
"serde",
]
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
[[package]]
name = "snafu"
version = "0.7.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e4de37ad025c587a29e8f3f5605c00f70b98715ef90b9061a815b9e59e9042d6"
dependencies = [
"doc-comment",
"snafu-derive",
]
[[package]]
name = "snafu-derive"
version = "0.7.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "990079665f075b699031e9c08fd3ab99be5029b96f3b78dc0709e8f77e4efebf"
dependencies = [
"heck 0.4.1",
"proc-macro2",
"quote",
"syn 1.0.109",
]
[[package]]
name = "snap"
version = "1.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1b6b67fb9a61334225b5b790716f609cd58395f895b3fe8b328786812a40bc3b"
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
[[package]]
name = "socket2"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.5.7"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "ce305eb0b4296696835b71df73eb912e0f1ffd2556a501fcede6e0c50349191c"
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
dependencies = [
"libc",
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
"windows-sys 0.52.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
]
[[package]]
name = "spin"
version = "0.5.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6e63cff320ae2c57904679ba7cb63280a3dc4613885beafb148ee7bf9aa9042d"
[[package]]
name = "spin"
version = "0.9.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6980e8d7511241f8acf4aebddbb1ff938df5eebe98691418c4468d0b72a96a67"
dependencies = [
"lock_api",
]
[[package]]
name = "spki"
version = "0.4.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5c01a0c15da1b0b0e1494112e7af814a678fec9bd157881b49beac661e9b6f32"
dependencies = [
"der",
]
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
[[package]]
name = "sql"
Use v3.0.0 as the version number. (#999) ### What Updates the version number to `3.0.0`, now we're officially at GA. ### How I updated the version number, and also updated some dependencies. The `Cargo.lock` file was not up to date. V3_GIT_ORIGIN_REV_ID: 3e9b784c8ad856556193e56aee9fa607fa8ce19e
2024-08-21 17:02:43 +03:00
version = "3.0.0"
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
dependencies = [
"async-trait",
Use v3.0.0 as the version number. (#999) ### What Updates the version number to `3.0.0`, now we're officially at GA. ### How I updated the version number, and also updated some dependencies. The `Cargo.lock` file was not up to date. V3_GIT_ORIGIN_REV_ID: 3e9b784c8ad856556193e56aee9fa607fa8ce19e
2024-08-21 17:02:43 +03:00
"chrono",
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
"datafusion",
"execute",
"futures",
"hasura-authn-core",
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"indexmap 2.4.0",
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
"ir",
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
"metadata-resolve",
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 0.2.0",
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
"open-dds",
"schema",
"serde",
simplify the sql context that powers datafusion (#921) Prior to this, on every request, a datafusion catalog provider was created from the stored sql context. This PR reworks it so that this is cheap and also more maintainable will fewer intermediate steps. There is also some work done towards supporting table valued functions. --------- Co-authored-by: Abhinav Gupta <127770473+abhinav-hasura@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: 8c30485366969d81d2a35760962e0383ed5e488c
2024-08-02 00:04:08 +03:00
"serde_json",
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
"thiserror",
[PACHA-12] sql: fix failing introspection queries (#958) ### What Introspection queries (on 'hasura' schema) would fail when there is no data in the underlying tables. ### How A more robust 'MemTable' with a comprehensive set of tests is introduced which shouldn't run into these issues. V3_GIT_ORIGIN_REV_ID: e09de03e8d093fb4348514cfed6b6dc1d9b0b0c8
2024-08-13 00:47:46 +03:00
"tokio",
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
"tracing-util",
]
[[package]]
name = "sqlparser"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
version = "0.49.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
update datafusion to 41.0.0 (#959) <!-- The PR description should answer 2 important questions: --> ### What Updates datafusion dependency to `41`. ### How Fixes for breaking changes. V3_GIT_ORIGIN_REV_ID: cc957f6c7ff9b3c004cc5e0cbb48387c1f963b7a
2024-08-13 02:05:50 +03:00
checksum = "a4a404d0e14905361b918cb8afdb73605e25c1d5029312bd9785142dcb3aa49e"
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
dependencies = [
"log",
"sqlparser_derive",
]
[[package]]
name = "sqlparser_derive"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "01b2e185515564f15375f593fb966b5718bc624ba77fe49fa4616ad619690554"
dependencies = [
"proc-macro2",
"quote",
Bump syn from 2.0.75 to 2.0.76 (#1017) Bumps [syn](https://github.com/dtolnay/syn) from 2.0.75 to 2.0.76. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/syn/releases">syn's releases</a>.</em></p> <blockquote> <h2>2.0.76</h2> <ul> <li>Enforce that tail call <code>become</code> keyword is followed by an expression (<a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/syn/commit/ef3e9c6dde79be7590fc90278772663ca31c1a73"><code>ef3e9c6</code></a> Release 2.0.76</li> <li><a href="https://github.com/dtolnay/syn/commit/8f7365ff9685c8ca9527c2de409204179a3efcdf"><code>8f7365f</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a> from dtolnay/tailcall</li> <li><a href="https://github.com/dtolnay/syn/commit/6cddd9ea714fe034466b4f02d3f7abb484c65ea0"><code>6cddd9e</code></a> Make tail call expr mandatory</li> <li>See full diff in <a href="https://github.com/dtolnay/syn/compare/2.0.75...2.0.76">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=syn&package-manager=cargo&previous-version=2.0.75&new-version=2.0.76)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d261ad30ffeb10034a80f9044504cb9d6c7c1ff7
2024-08-26 14:39:45 +03:00
"syn 2.0.76",
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
]
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
[[package]]
name = "stable_deref_trait"
version = "1.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a8f112729512f8e442d81f95a8a7ddf2b7c6b8a1a6f509a95864142b30cab2d3"
[[package]]
name = "static_assertions"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a2eb9349b6444b326872e140eb1cf5e7c522154d69e7a0ffb0fb81c06b37543f"
[[package]]
name = "strsim"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.11.1"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "7da8b5736845d9f2fcb837ea5d9e2628564b3b043a70948a3f0b778838c5fb4f"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
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
[[package]]
name = "strum"
Bump strum from 0.26.2 to 0.26.3 (#746) V3_GIT_ORIGIN_REV_ID: 082fc99d56a9d3b37ff81780554882c53273687a
2024-06-24 11:12:36 +03:00
version = "0.26.3"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump strum from 0.26.2 to 0.26.3 (#746) V3_GIT_ORIGIN_REV_ID: 082fc99d56a9d3b37ff81780554882c53273687a
2024-06-24 11:12:36 +03:00
checksum = "8fec0f0aef304996cf250b31b5a10dee7980c85da9d759361292b8bca5a18f06"
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
dependencies = [
"strum_macros",
]
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
[[package]]
name = "strum_macros"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.26.4"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "4c6bee85a5a24955dc440386795aa378cd9cf82acd5f764469152d2270e581be"
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
dependencies = [
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
"heck 0.5.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
"proc-macro2",
"quote",
"rustversion",
Bump syn from 2.0.75 to 2.0.76 (#1017) Bumps [syn](https://github.com/dtolnay/syn) from 2.0.75 to 2.0.76. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/syn/releases">syn's releases</a>.</em></p> <blockquote> <h2>2.0.76</h2> <ul> <li>Enforce that tail call <code>become</code> keyword is followed by an expression (<a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/syn/commit/ef3e9c6dde79be7590fc90278772663ca31c1a73"><code>ef3e9c6</code></a> Release 2.0.76</li> <li><a href="https://github.com/dtolnay/syn/commit/8f7365ff9685c8ca9527c2de409204179a3efcdf"><code>8f7365f</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a> from dtolnay/tailcall</li> <li><a href="https://github.com/dtolnay/syn/commit/6cddd9ea714fe034466b4f02d3f7abb484c65ea0"><code>6cddd9e</code></a> Make tail call expr mandatory</li> <li>See full diff in <a href="https://github.com/dtolnay/syn/compare/2.0.75...2.0.76">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=syn&package-manager=cargo&previous-version=2.0.75&new-version=2.0.76)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d261ad30ffeb10034a80f9044504cb9d6c7c1ff7
2024-08-26 14:39:45 +03:00
"syn 2.0.76",
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
]
[[package]]
name = "subtle"
Update to Rust v1.80.1. (#1002) ### What Upgrade to the latest version of Rust. ### How I modified `rust-toolchain.toml` and ran `cargo update`. V3_GIT_ORIGIN_REV_ID: 5fe675ee5dc568cd24de542c826ffd2d355f90ff
2024-08-22 11:08:47 +03:00
version = "2.4.1"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update to Rust v1.80.1. (#1002) ### What Upgrade to the latest version of Rust. ### How I modified `rust-toolchain.toml` and ran `cargo update`. V3_GIT_ORIGIN_REV_ID: 5fe675ee5dc568cd24de542c826ffd2d355f90ff
2024-08-22 11:08:47 +03:00
checksum = "6bdef32e8150c2a081110b42772ffe7d7c9032b606bc226c8260fd97e0976601"
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
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
[[package]]
name = "syn"
version = "1.0.109"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "72b64191b275b66ffe2469e8af2c1cfe3bafa67b529ead792a6d0160888b4237"
dependencies = [
"proc-macro2",
"quote",
"unicode-ident",
]
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
[[package]]
name = "syn"
Bump syn from 2.0.75 to 2.0.76 (#1017) Bumps [syn](https://github.com/dtolnay/syn) from 2.0.75 to 2.0.76. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/syn/releases">syn's releases</a>.</em></p> <blockquote> <h2>2.0.76</h2> <ul> <li>Enforce that tail call <code>become</code> keyword is followed by an expression (<a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/syn/commit/ef3e9c6dde79be7590fc90278772663ca31c1a73"><code>ef3e9c6</code></a> Release 2.0.76</li> <li><a href="https://github.com/dtolnay/syn/commit/8f7365ff9685c8ca9527c2de409204179a3efcdf"><code>8f7365f</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a> from dtolnay/tailcall</li> <li><a href="https://github.com/dtolnay/syn/commit/6cddd9ea714fe034466b4f02d3f7abb484c65ea0"><code>6cddd9e</code></a> Make tail call expr mandatory</li> <li>See full diff in <a href="https://github.com/dtolnay/syn/compare/2.0.75...2.0.76">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=syn&package-manager=cargo&previous-version=2.0.75&new-version=2.0.76)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d261ad30ffeb10034a80f9044504cb9d6c7c1ff7
2024-08-26 14:39:45 +03:00
version = "2.0.76"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump syn from 2.0.75 to 2.0.76 (#1017) Bumps [syn](https://github.com/dtolnay/syn) from 2.0.75 to 2.0.76. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/syn/releases">syn's releases</a>.</em></p> <blockquote> <h2>2.0.76</h2> <ul> <li>Enforce that tail call <code>become</code> keyword is followed by an expression (<a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/syn/commit/ef3e9c6dde79be7590fc90278772663ca31c1a73"><code>ef3e9c6</code></a> Release 2.0.76</li> <li><a href="https://github.com/dtolnay/syn/commit/8f7365ff9685c8ca9527c2de409204179a3efcdf"><code>8f7365f</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a> from dtolnay/tailcall</li> <li><a href="https://github.com/dtolnay/syn/commit/6cddd9ea714fe034466b4f02d3f7abb484c65ea0"><code>6cddd9e</code></a> Make tail call expr mandatory</li> <li>See full diff in <a href="https://github.com/dtolnay/syn/compare/2.0.75...2.0.76">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=syn&package-manager=cargo&previous-version=2.0.75&new-version=2.0.76)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d261ad30ffeb10034a80f9044504cb9d6c7c1ff7
2024-08-26 14:39:45 +03:00
checksum = "578e081a14e0cefc3279b0472138c513f37b41a08d5a3cca9b6e4e8ceb6cd525"
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
dependencies = [
"proc-macro2",
"quote",
"unicode-ident",
]
[[package]]
name = "sync_wrapper"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2047c6ded9c721764247e62cd3b03c09ffc529b2ba5b10ec482ae507a4a70160"
[[package]]
name = "system-configuration"
version = "0.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ba3a3adc5c275d719af8cb4272ea1c4a6d668a777f37e115f6d11ddbc1c8e0e7"
dependencies = [
"bitflags 1.3.2",
"core-foundation",
"system-configuration-sys",
]
[[package]]
name = "system-configuration-sys"
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a75fb188eb626b924683e3b95e3a48e63551fcfb51949de2f06a9d91dbee93c9"
dependencies = [
"core-foundation-sys",
"libc",
]
[[package]]
name = "tap"
version = "1.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "55937e1799185b12863d447f42597ed69d9928686b8d88a1df17376a097d8369"
[[package]]
name = "tempfile"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "3.12.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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "04cbcdd0c794ebb0d4cf35e88edd2f7d2c4c3e9a5a6dab322839b321c6a87a64"
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
dependencies = [
"cfg-if",
"fastrand",
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"once_cell",
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
"rustix",
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"windows-sys 0.59.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
]
[[package]]
name = "text-size"
version = "1.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f18aa187839b2bdb1ad2fa35ead8c4c2976b64e4363c386d45ac0f7ee85c9233"
[[package]]
name = "thiserror"
Bump thiserror from 1.0.62 to 1.0.63 (#898) Bumps [thiserror](https://github.com/dtolnay/thiserror) from 1.0.62 to 1.0.63. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/thiserror/releases">thiserror's releases</a>.</em></p> <blockquote> <h2>1.0.63</h2> <ul> <li>Documentation improvements</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/thiserror/commit/915c75e8a3b679588e6eac03dccbba5d38c764a8"><code>915c75e</code></a> Release 1.0.63</li> <li><a href="https://github.com/dtolnay/thiserror/commit/3d5ec25464d2d71f09f480666e240d3446a44a19"><code>3d5ec25</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/thiserror/issues/312">#312</a> from dtolnay/backtracedoc</li> <li><a href="https://github.com/dtolnay/thiserror/commit/de8a1e54d420514250d9d4081d41723192cf0dfa"><code>de8a1e5</code></a> Update documentation of #[from] and #[backtrace] attributes</li> <li>See full diff in <a href="https://github.com/dtolnay/thiserror/compare/1.0.62...1.0.63">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=thiserror&package-manager=cargo&previous-version=1.0.62&new-version=1.0.63)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: 7c28562af5d512f1be5543cd6f90141136eaf80e
2024-07-29 13:08:46 +03:00
version = "1.0.63"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump thiserror from 1.0.62 to 1.0.63 (#898) Bumps [thiserror](https://github.com/dtolnay/thiserror) from 1.0.62 to 1.0.63. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/thiserror/releases">thiserror's releases</a>.</em></p> <blockquote> <h2>1.0.63</h2> <ul> <li>Documentation improvements</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/thiserror/commit/915c75e8a3b679588e6eac03dccbba5d38c764a8"><code>915c75e</code></a> Release 1.0.63</li> <li><a href="https://github.com/dtolnay/thiserror/commit/3d5ec25464d2d71f09f480666e240d3446a44a19"><code>3d5ec25</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/thiserror/issues/312">#312</a> from dtolnay/backtracedoc</li> <li><a href="https://github.com/dtolnay/thiserror/commit/de8a1e54d420514250d9d4081d41723192cf0dfa"><code>de8a1e5</code></a> Update documentation of #[from] and #[backtrace] attributes</li> <li>See full diff in <a href="https://github.com/dtolnay/thiserror/compare/1.0.62...1.0.63">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=thiserror&package-manager=cargo&previous-version=1.0.62&new-version=1.0.63)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: 7c28562af5d512f1be5543cd6f90141136eaf80e
2024-07-29 13:08:46 +03:00
checksum = "c0342370b38b6a11b6cc11d6a805569958d54cfa061a29969c3b5ce2ea405724"
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
dependencies = [
"thiserror-impl",
]
[[package]]
name = "thiserror-impl"
Bump thiserror from 1.0.62 to 1.0.63 (#898) Bumps [thiserror](https://github.com/dtolnay/thiserror) from 1.0.62 to 1.0.63. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/thiserror/releases">thiserror's releases</a>.</em></p> <blockquote> <h2>1.0.63</h2> <ul> <li>Documentation improvements</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/thiserror/commit/915c75e8a3b679588e6eac03dccbba5d38c764a8"><code>915c75e</code></a> Release 1.0.63</li> <li><a href="https://github.com/dtolnay/thiserror/commit/3d5ec25464d2d71f09f480666e240d3446a44a19"><code>3d5ec25</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/thiserror/issues/312">#312</a> from dtolnay/backtracedoc</li> <li><a href="https://github.com/dtolnay/thiserror/commit/de8a1e54d420514250d9d4081d41723192cf0dfa"><code>de8a1e5</code></a> Update documentation of #[from] and #[backtrace] attributes</li> <li>See full diff in <a href="https://github.com/dtolnay/thiserror/compare/1.0.62...1.0.63">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=thiserror&package-manager=cargo&previous-version=1.0.62&new-version=1.0.63)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: 7c28562af5d512f1be5543cd6f90141136eaf80e
2024-07-29 13:08:46 +03:00
version = "1.0.63"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump thiserror from 1.0.62 to 1.0.63 (#898) Bumps [thiserror](https://github.com/dtolnay/thiserror) from 1.0.62 to 1.0.63. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/thiserror/releases">thiserror's releases</a>.</em></p> <blockquote> <h2>1.0.63</h2> <ul> <li>Documentation improvements</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/thiserror/commit/915c75e8a3b679588e6eac03dccbba5d38c764a8"><code>915c75e</code></a> Release 1.0.63</li> <li><a href="https://github.com/dtolnay/thiserror/commit/3d5ec25464d2d71f09f480666e240d3446a44a19"><code>3d5ec25</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/thiserror/issues/312">#312</a> from dtolnay/backtracedoc</li> <li><a href="https://github.com/dtolnay/thiserror/commit/de8a1e54d420514250d9d4081d41723192cf0dfa"><code>de8a1e5</code></a> Update documentation of #[from] and #[backtrace] attributes</li> <li>See full diff in <a href="https://github.com/dtolnay/thiserror/compare/1.0.62...1.0.63">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=thiserror&package-manager=cargo&previous-version=1.0.62&new-version=1.0.63)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: 7c28562af5d512f1be5543cd6f90141136eaf80e
2024-07-29 13:08:46 +03:00
checksum = "a4558b58466b9ad7ca0f102865eccc95938dca1a74a856f2b57b6629050da261"
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
dependencies = [
"proc-macro2",
"quote",
Bump syn from 2.0.75 to 2.0.76 (#1017) Bumps [syn](https://github.com/dtolnay/syn) from 2.0.75 to 2.0.76. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/syn/releases">syn's releases</a>.</em></p> <blockquote> <h2>2.0.76</h2> <ul> <li>Enforce that tail call <code>become</code> keyword is followed by an expression (<a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/syn/commit/ef3e9c6dde79be7590fc90278772663ca31c1a73"><code>ef3e9c6</code></a> Release 2.0.76</li> <li><a href="https://github.com/dtolnay/syn/commit/8f7365ff9685c8ca9527c2de409204179a3efcdf"><code>8f7365f</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a> from dtolnay/tailcall</li> <li><a href="https://github.com/dtolnay/syn/commit/6cddd9ea714fe034466b4f02d3f7abb484c65ea0"><code>6cddd9e</code></a> Make tail call expr mandatory</li> <li>See full diff in <a href="https://github.com/dtolnay/syn/compare/2.0.75...2.0.76">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=syn&package-manager=cargo&previous-version=2.0.75&new-version=2.0.76)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d261ad30ffeb10034a80f9044504cb9d6c7c1ff7
2024-08-26 14:39:45 +03:00
"syn 2.0.76",
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
]
support OpenTelemetry zipkin propagator (#466) Support both W3C and Zipkin B3 headers and connectors will prefer B3 headers to extract traces because Cloud Run doesn't respect those headers. V3_GIT_ORIGIN_REV_ID: 1471b848e71d87420bc75b9adee60951f306c856
2024-04-16 17:55:54 +03:00
[[package]]
name = "thread_local"
version = "1.1.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8b9ef9bad013ada3808854ceac7b46812a6465ba368859a37e2100283d2d719c"
dependencies = [
"cfg-if",
"once_cell",
]
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
[[package]]
name = "thrift"
version = "0.17.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7e54bc85fc7faa8bc175c4bab5b92ba8d9a3ce893d0e9f42cc455c8ab16a9e09"
dependencies = [
"byteorder",
"integer-encoding",
"ordered-float 2.10.1",
]
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
[[package]]
name = "time"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.3.36"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "5dfd88e563464686c916c7e46e623e520ddc6d79fa6641390f2e3fa86e83e885"
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
dependencies = [
"deranged",
"itoa",
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
"num-conv",
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
"powerfmt",
"serde",
"time-core",
"time-macros",
]
[[package]]
name = "time-core"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ef927ca75afb808a4d64dd374f00a2adf8d0fcff8e7b184af886c3c87ec4a3f3"
[[package]]
name = "time-macros"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.2.18"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "3f252a68540fde3a3877aeea552b832b40ab9a69e318efd078774a01ddee1ccf"
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
dependencies = [
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
"num-conv",
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
"time-core",
]
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
[[package]]
name = "tiny-keccak"
version = "2.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2c9d3793400a45f954c52e73d068316d76b6f4e36977e3fcebb13a2721e80237"
dependencies = [
"crunchy",
]
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
[[package]]
name = "tinytemplate"
version = "1.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "be4d6b5f19ff7664e8c98d03e2139cb510db9b0a60b55f8e8709b689d939b6bc"
dependencies = [
"serde",
"serde_json",
]
[[package]]
name = "tinyvec"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "1.8.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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "445e881f4f6d382d5f27c034e25eb92edd7c784ceab92a0937db7f2e9471b938"
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
dependencies = [
"tinyvec_macros",
]
[[package]]
name = "tinyvec_macros"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1f3ccbac311fea05f86f61904b462b55fb3df8837a366dfc601a0161d0532f20"
[[package]]
name = "tokio"
Use v3.0.0 as the version number. (#999) ### What Updates the version number to `3.0.0`, now we're officially at GA. ### How I updated the version number, and also updated some dependencies. The `Cargo.lock` file was not up to date. V3_GIT_ORIGIN_REV_ID: 3e9b784c8ad856556193e56aee9fa607fa8ce19e
2024-08-21 17:02:43 +03:00
version = "1.39.3"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Use v3.0.0 as the version number. (#999) ### What Updates the version number to `3.0.0`, now we're officially at GA. ### How I updated the version number, and also updated some dependencies. The `Cargo.lock` file was not up to date. V3_GIT_ORIGIN_REV_ID: 3e9b784c8ad856556193e56aee9fa607fa8ce19e
2024-08-21 17:02:43 +03:00
checksum = "9babc99b9923bfa4804bd74722ff02c0381021eafa4db9949217e3be8e84fff5"
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
dependencies = [
"backtrace",
"bytes",
"libc",
"mio",
"parking_lot",
"pin-project-lite",
"signal-hook-registry",
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
"socket2",
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
"tokio-macros",
Bump tokio from 1.38.1 to 1.39.2 (#897) Bumps [tokio](https://github.com/tokio-rs/tokio) from 1.38.1 to 1.39.2. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/tokio-rs/tokio/releases">tokio's releases</a>.</em></p> <blockquote> <h2>Tokio v1.39.2</h2> <h1>1.39.2 (July 27th, 2024)</h1> <p>This release fixes a regression where the <code>select!</code> macro stopped accepting expressions that make use of temporary lifetime extension. (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6722">#6722</a>)</p> <p><a href="https://redirect.github.com/tokio-rs/tokio/issues/6722">#6722</a>: <a href="https://redirect.github.com/tokio-rs/tokio/pull/6722">tokio-rs/tokio#6722</a></p> <h2>Tokio v1.39.1</h2> <h1>1.39.1 (July 23rd, 2024)</h1> <p>This release reverts &quot;time: avoid traversing entries in the time wheel twice&quot; because it contains a bug. (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6715">#6715</a>)</p> <p><a href="https://redirect.github.com/tokio-rs/tokio/issues/6715">#6715</a>: <a href="https://redirect.github.com/tokio-rs/tokio/pull/6715">tokio-rs/tokio#6715</a></p> <h2>Tokio v1.39.0</h2> <h1>1.39.0 (July 23rd, 2024)</h1> <ul> <li>This release bumps the MSRV to 1.70. (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6645">#6645</a>)</li> <li>This release upgrades to mio v1. (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6635">#6635</a>)</li> <li>This release upgrades to windows-sys v0.52 (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6154">#6154</a>)</li> </ul> <h3>Added</h3> <ul> <li>io: implement <code>AsyncSeek</code> for <code>Empty</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6663">#6663</a>)</li> <li>metrics: stabilize <code>num_alive_tasks</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6619">#6619</a>, <a href="https://redirect.github.com/tokio-rs/tokio/issues/6667">#6667</a>)</li> <li>process: add <code>Command::as_std_mut</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6608">#6608</a>)</li> <li>sync: add <code>watch::Sender::same_channel</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6637">#6637</a>)</li> <li>sync: add <code>{Receiver,UnboundedReceiver}::{sender_strong_count,sender_weak_count}</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6661">#6661</a>)</li> <li>sync: implement <code>Default</code> for <code>watch::Sender</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6626">#6626</a>)</li> <li>task: implement <code>Clone</code> for <code>AbortHandle</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6621">#6621</a>)</li> <li>task: stabilize <code>consume_budget</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6622">#6622</a>)</li> </ul> <h3>Changed</h3> <ul> <li>io: improve panic message of <code>ReadBuf::put_slice()</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6629">#6629</a>)</li> <li>io: read during write in <code>copy_bidirectional</code> and <code>copy</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6532">#6532</a>)</li> <li>runtime: replace <code>num_cpus</code> with <code>available_parallelism</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6709">#6709</a>)</li> <li>task: avoid stack overflow when passing large future to <code>block_on</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6692">#6692</a>)</li> <li>time: avoid traversing entries in the time wheel twice (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6584">#6584</a>)</li> <li>time: support <code>IntoFuture</code> with <code>timeout</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6666">#6666</a>)</li> <li>macros: support <code>IntoFuture</code> with <code>join!</code> and <code>select!</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6710">#6710</a>)</li> </ul> <h3>Fixed</h3> <ul> <li>docs: fix docsrs builds with the fs feature enabled (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6585">#6585</a>)</li> <li>io: only use short-read optimization on known-to-be-compatible platforms (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6668">#6668</a>)</li> <li>time: fix overflow panic when using large durations with <code>Interval</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6612">#6612</a>)</li> </ul> <h3>Added (unstable)</h3> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/tokio-rs/tokio/commit/f602eae49988dbad2a11fd83e6b3fbd4f094713c"><code>f602eae</code></a> chore: prepare Tokio v1.39.2 (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6730">#6730</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/438def79579a7e285beb5f0d93b1eb6a9f8062b3"><code>438def7</code></a> macros: allow temporary lifetime extension in select (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6722">#6722</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/ee8d4d1b0546c67198af3cd053d6b7b8b4fd26c3"><code>ee8d4d1</code></a> chore: fix ci failures (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6725">#6725</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/32970527633bb72fc4f01d02523484a9376ac26a"><code>3297052</code></a> ci: test Quinn in CI (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6719">#6719</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/f8fe0ffb23c2279708cb5dada7c88defdae60845"><code>f8fe0ff</code></a> chore: prepare Tokio v1.39.1 (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6716">#6716</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/47210a8e6eeb82b51aa778074fdc4d757b953b8c"><code>47210a8</code></a> time: revert &quot;avoid traversing entries in the time wheel twice&quot; (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6715">#6715</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/29545d90370d925a7264ff8636013ee6bf1760e6"><code>29545d9</code></a> runtime: ignore many_oneshot_futures test for alt scheduler (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6712">#6712</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/48e35c11d924ffa3a009b89fbb6d36e57b835da4"><code>48e35c1</code></a> chore: release Tokio v1.39.0 (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6711">#6711</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/dd1d37167d1f4008ca5d3df500e86826112a8cad"><code>dd1d371</code></a> macros: accept <code>IntoFuture</code> args for macros (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6710">#6710</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/6a1a7b15912d1a86ab4c0d09e1a8f0a221dbfeee"><code>6a1a7b1</code></a> chore: prepare tokio-macros v2.4.0 (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6707">#6707</a>)</li> <li>Additional commits viewable in <a href="https://github.com/tokio-rs/tokio/compare/tokio-1.38.1...tokio-1.39.2">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=tokio&package-manager=cargo&previous-version=1.38.1&new-version=1.39.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: 0cb6c24bedcd6553e8936334df936f49023b8308
2024-07-29 13:07:48 +03:00
"windows-sys 0.52.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
]
[[package]]
name = "tokio-io-timeout"
version = "1.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "30b74022ada614a1b4834de765f9bb43877f910cc8ce4be40e89042c9223a8bf"
dependencies = [
"pin-project-lite",
"tokio",
]
[[package]]
name = "tokio-macros"
Bump tokio from 1.38.1 to 1.39.2 (#897) Bumps [tokio](https://github.com/tokio-rs/tokio) from 1.38.1 to 1.39.2. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/tokio-rs/tokio/releases">tokio's releases</a>.</em></p> <blockquote> <h2>Tokio v1.39.2</h2> <h1>1.39.2 (July 27th, 2024)</h1> <p>This release fixes a regression where the <code>select!</code> macro stopped accepting expressions that make use of temporary lifetime extension. (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6722">#6722</a>)</p> <p><a href="https://redirect.github.com/tokio-rs/tokio/issues/6722">#6722</a>: <a href="https://redirect.github.com/tokio-rs/tokio/pull/6722">tokio-rs/tokio#6722</a></p> <h2>Tokio v1.39.1</h2> <h1>1.39.1 (July 23rd, 2024)</h1> <p>This release reverts &quot;time: avoid traversing entries in the time wheel twice&quot; because it contains a bug. (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6715">#6715</a>)</p> <p><a href="https://redirect.github.com/tokio-rs/tokio/issues/6715">#6715</a>: <a href="https://redirect.github.com/tokio-rs/tokio/pull/6715">tokio-rs/tokio#6715</a></p> <h2>Tokio v1.39.0</h2> <h1>1.39.0 (July 23rd, 2024)</h1> <ul> <li>This release bumps the MSRV to 1.70. (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6645">#6645</a>)</li> <li>This release upgrades to mio v1. (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6635">#6635</a>)</li> <li>This release upgrades to windows-sys v0.52 (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6154">#6154</a>)</li> </ul> <h3>Added</h3> <ul> <li>io: implement <code>AsyncSeek</code> for <code>Empty</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6663">#6663</a>)</li> <li>metrics: stabilize <code>num_alive_tasks</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6619">#6619</a>, <a href="https://redirect.github.com/tokio-rs/tokio/issues/6667">#6667</a>)</li> <li>process: add <code>Command::as_std_mut</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6608">#6608</a>)</li> <li>sync: add <code>watch::Sender::same_channel</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6637">#6637</a>)</li> <li>sync: add <code>{Receiver,UnboundedReceiver}::{sender_strong_count,sender_weak_count}</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6661">#6661</a>)</li> <li>sync: implement <code>Default</code> for <code>watch::Sender</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6626">#6626</a>)</li> <li>task: implement <code>Clone</code> for <code>AbortHandle</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6621">#6621</a>)</li> <li>task: stabilize <code>consume_budget</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6622">#6622</a>)</li> </ul> <h3>Changed</h3> <ul> <li>io: improve panic message of <code>ReadBuf::put_slice()</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6629">#6629</a>)</li> <li>io: read during write in <code>copy_bidirectional</code> and <code>copy</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6532">#6532</a>)</li> <li>runtime: replace <code>num_cpus</code> with <code>available_parallelism</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6709">#6709</a>)</li> <li>task: avoid stack overflow when passing large future to <code>block_on</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6692">#6692</a>)</li> <li>time: avoid traversing entries in the time wheel twice (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6584">#6584</a>)</li> <li>time: support <code>IntoFuture</code> with <code>timeout</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6666">#6666</a>)</li> <li>macros: support <code>IntoFuture</code> with <code>join!</code> and <code>select!</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6710">#6710</a>)</li> </ul> <h3>Fixed</h3> <ul> <li>docs: fix docsrs builds with the fs feature enabled (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6585">#6585</a>)</li> <li>io: only use short-read optimization on known-to-be-compatible platforms (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6668">#6668</a>)</li> <li>time: fix overflow panic when using large durations with <code>Interval</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6612">#6612</a>)</li> </ul> <h3>Added (unstable)</h3> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/tokio-rs/tokio/commit/f602eae49988dbad2a11fd83e6b3fbd4f094713c"><code>f602eae</code></a> chore: prepare Tokio v1.39.2 (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6730">#6730</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/438def79579a7e285beb5f0d93b1eb6a9f8062b3"><code>438def7</code></a> macros: allow temporary lifetime extension in select (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6722">#6722</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/ee8d4d1b0546c67198af3cd053d6b7b8b4fd26c3"><code>ee8d4d1</code></a> chore: fix ci failures (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6725">#6725</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/32970527633bb72fc4f01d02523484a9376ac26a"><code>3297052</code></a> ci: test Quinn in CI (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6719">#6719</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/f8fe0ffb23c2279708cb5dada7c88defdae60845"><code>f8fe0ff</code></a> chore: prepare Tokio v1.39.1 (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6716">#6716</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/47210a8e6eeb82b51aa778074fdc4d757b953b8c"><code>47210a8</code></a> time: revert &quot;avoid traversing entries in the time wheel twice&quot; (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6715">#6715</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/29545d90370d925a7264ff8636013ee6bf1760e6"><code>29545d9</code></a> runtime: ignore many_oneshot_futures test for alt scheduler (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6712">#6712</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/48e35c11d924ffa3a009b89fbb6d36e57b835da4"><code>48e35c1</code></a> chore: release Tokio v1.39.0 (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6711">#6711</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/dd1d37167d1f4008ca5d3df500e86826112a8cad"><code>dd1d371</code></a> macros: accept <code>IntoFuture</code> args for macros (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6710">#6710</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/6a1a7b15912d1a86ab4c0d09e1a8f0a221dbfeee"><code>6a1a7b1</code></a> chore: prepare tokio-macros v2.4.0 (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6707">#6707</a>)</li> <li>Additional commits viewable in <a href="https://github.com/tokio-rs/tokio/compare/tokio-1.38.1...tokio-1.39.2">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=tokio&package-manager=cargo&previous-version=1.38.1&new-version=1.39.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: 0cb6c24bedcd6553e8936334df936f49023b8308
2024-07-29 13:07:48 +03:00
version = "2.4.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
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump tokio from 1.38.1 to 1.39.2 (#897) Bumps [tokio](https://github.com/tokio-rs/tokio) from 1.38.1 to 1.39.2. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/tokio-rs/tokio/releases">tokio's releases</a>.</em></p> <blockquote> <h2>Tokio v1.39.2</h2> <h1>1.39.2 (July 27th, 2024)</h1> <p>This release fixes a regression where the <code>select!</code> macro stopped accepting expressions that make use of temporary lifetime extension. (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6722">#6722</a>)</p> <p><a href="https://redirect.github.com/tokio-rs/tokio/issues/6722">#6722</a>: <a href="https://redirect.github.com/tokio-rs/tokio/pull/6722">tokio-rs/tokio#6722</a></p> <h2>Tokio v1.39.1</h2> <h1>1.39.1 (July 23rd, 2024)</h1> <p>This release reverts &quot;time: avoid traversing entries in the time wheel twice&quot; because it contains a bug. (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6715">#6715</a>)</p> <p><a href="https://redirect.github.com/tokio-rs/tokio/issues/6715">#6715</a>: <a href="https://redirect.github.com/tokio-rs/tokio/pull/6715">tokio-rs/tokio#6715</a></p> <h2>Tokio v1.39.0</h2> <h1>1.39.0 (July 23rd, 2024)</h1> <ul> <li>This release bumps the MSRV to 1.70. (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6645">#6645</a>)</li> <li>This release upgrades to mio v1. (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6635">#6635</a>)</li> <li>This release upgrades to windows-sys v0.52 (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6154">#6154</a>)</li> </ul> <h3>Added</h3> <ul> <li>io: implement <code>AsyncSeek</code> for <code>Empty</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6663">#6663</a>)</li> <li>metrics: stabilize <code>num_alive_tasks</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6619">#6619</a>, <a href="https://redirect.github.com/tokio-rs/tokio/issues/6667">#6667</a>)</li> <li>process: add <code>Command::as_std_mut</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6608">#6608</a>)</li> <li>sync: add <code>watch::Sender::same_channel</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6637">#6637</a>)</li> <li>sync: add <code>{Receiver,UnboundedReceiver}::{sender_strong_count,sender_weak_count}</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6661">#6661</a>)</li> <li>sync: implement <code>Default</code> for <code>watch::Sender</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6626">#6626</a>)</li> <li>task: implement <code>Clone</code> for <code>AbortHandle</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6621">#6621</a>)</li> <li>task: stabilize <code>consume_budget</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6622">#6622</a>)</li> </ul> <h3>Changed</h3> <ul> <li>io: improve panic message of <code>ReadBuf::put_slice()</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6629">#6629</a>)</li> <li>io: read during write in <code>copy_bidirectional</code> and <code>copy</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6532">#6532</a>)</li> <li>runtime: replace <code>num_cpus</code> with <code>available_parallelism</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6709">#6709</a>)</li> <li>task: avoid stack overflow when passing large future to <code>block_on</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6692">#6692</a>)</li> <li>time: avoid traversing entries in the time wheel twice (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6584">#6584</a>)</li> <li>time: support <code>IntoFuture</code> with <code>timeout</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6666">#6666</a>)</li> <li>macros: support <code>IntoFuture</code> with <code>join!</code> and <code>select!</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6710">#6710</a>)</li> </ul> <h3>Fixed</h3> <ul> <li>docs: fix docsrs builds with the fs feature enabled (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6585">#6585</a>)</li> <li>io: only use short-read optimization on known-to-be-compatible platforms (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6668">#6668</a>)</li> <li>time: fix overflow panic when using large durations with <code>Interval</code> (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6612">#6612</a>)</li> </ul> <h3>Added (unstable)</h3> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/tokio-rs/tokio/commit/f602eae49988dbad2a11fd83e6b3fbd4f094713c"><code>f602eae</code></a> chore: prepare Tokio v1.39.2 (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6730">#6730</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/438def79579a7e285beb5f0d93b1eb6a9f8062b3"><code>438def7</code></a> macros: allow temporary lifetime extension in select (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6722">#6722</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/ee8d4d1b0546c67198af3cd053d6b7b8b4fd26c3"><code>ee8d4d1</code></a> chore: fix ci failures (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6725">#6725</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/32970527633bb72fc4f01d02523484a9376ac26a"><code>3297052</code></a> ci: test Quinn in CI (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6719">#6719</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/f8fe0ffb23c2279708cb5dada7c88defdae60845"><code>f8fe0ff</code></a> chore: prepare Tokio v1.39.1 (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6716">#6716</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/47210a8e6eeb82b51aa778074fdc4d757b953b8c"><code>47210a8</code></a> time: revert &quot;avoid traversing entries in the time wheel twice&quot; (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6715">#6715</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/29545d90370d925a7264ff8636013ee6bf1760e6"><code>29545d9</code></a> runtime: ignore many_oneshot_futures test for alt scheduler (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6712">#6712</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/48e35c11d924ffa3a009b89fbb6d36e57b835da4"><code>48e35c1</code></a> chore: release Tokio v1.39.0 (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6711">#6711</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/dd1d37167d1f4008ca5d3df500e86826112a8cad"><code>dd1d371</code></a> macros: accept <code>IntoFuture</code> args for macros (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6710">#6710</a>)</li> <li><a href="https://github.com/tokio-rs/tokio/commit/6a1a7b15912d1a86ab4c0d09e1a8f0a221dbfeee"><code>6a1a7b1</code></a> chore: prepare tokio-macros v2.4.0 (<a href="https://redirect.github.com/tokio-rs/tokio/issues/6707">#6707</a>)</li> <li>Additional commits viewable in <a href="https://github.com/tokio-rs/tokio/compare/tokio-1.38.1...tokio-1.39.2">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=tokio&package-manager=cargo&previous-version=1.38.1&new-version=1.39.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: 0cb6c24bedcd6553e8936334df936f49023b8308
2024-07-29 13:07:48 +03:00
checksum = "693d596312e88961bc67d7f1f97af8a70227d9f90c31bba5806eec004978d752"
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
dependencies = [
"proc-macro2",
"quote",
Bump syn from 2.0.75 to 2.0.76 (#1017) Bumps [syn](https://github.com/dtolnay/syn) from 2.0.75 to 2.0.76. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/syn/releases">syn's releases</a>.</em></p> <blockquote> <h2>2.0.76</h2> <ul> <li>Enforce that tail call <code>become</code> keyword is followed by an expression (<a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/syn/commit/ef3e9c6dde79be7590fc90278772663ca31c1a73"><code>ef3e9c6</code></a> Release 2.0.76</li> <li><a href="https://github.com/dtolnay/syn/commit/8f7365ff9685c8ca9527c2de409204179a3efcdf"><code>8f7365f</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a> from dtolnay/tailcall</li> <li><a href="https://github.com/dtolnay/syn/commit/6cddd9ea714fe034466b4f02d3f7abb484c65ea0"><code>6cddd9e</code></a> Make tail call expr mandatory</li> <li>See full diff in <a href="https://github.com/dtolnay/syn/compare/2.0.75...2.0.76">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=syn&package-manager=cargo&previous-version=2.0.75&new-version=2.0.76)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d261ad30ffeb10034a80f9044504cb9d6c7c1ff7
2024-08-26 14:39:45 +03:00
"syn 2.0.76",
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
]
[[package]]
name = "tokio-native-tls"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bbae76ab933c85776efabc971569dd6119c580d8f5d448769dec1764bf796ef2"
dependencies = [
"native-tls",
"tokio",
]
[[package]]
name = "tokio-stream"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.1.15"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "267ac89e0bec6e691e5813911606935d77c476ff49024f98abcea3e7b15e37af"
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
dependencies = [
"futures-core",
"pin-project-lite",
"tokio",
]
[[package]]
name = "tokio-test"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.4.4"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "2468baabc3311435b55dd935f702f42cd1b8abb7e754fb7dfb16bd36aa88f9f7"
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
dependencies = [
"async-stream",
"bytes",
"futures-core",
"tokio",
"tokio-stream",
]
[[package]]
name = "tokio-util"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.7.11"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "9cf6b47b3771c49ac75ad09a6162f53ad4b8088b76ac60e8ec1455b31a189fe1"
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
dependencies = [
"bytes",
"futures-core",
"futures-sink",
"pin-project-lite",
"tokio",
]
[[package]]
name = "tonic"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.11.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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "76c4eb7a4e9ef9d4763600161f12f5070b92a578e1b634db88a6887844c91a13"
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
dependencies = [
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
"async-stream",
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
"async-trait",
"axum",
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
"base64 0.21.7",
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
"bytes",
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
"h2",
"http",
"http-body",
"hyper",
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
"hyper-timeout",
Remove unused dependencies using `cargo machete`. (#413) `cargo machete` is a very useful tool that figures out when you aren't using a dependency. I have run this locally to remove unused dependencies. I've also added a CI job to make sure we catch these in the future. Sometimes it reports false positives, e.g. when a dependency isn't used directly but in macro-generated code (e.g. with `strum`). I have added `"ignored"` clauses to the `Cargo.toml` files where appropriate. V3_GIT_ORIGIN_REV_ID: ed015089b695cec8eeb03ce455d6dd3cd312a016
2024-03-28 12:16:54 +03:00
"percent-encoding",
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
"pin-project",
"prost",
"tokio",
"tokio-stream",
"tower",
"tower-layer",
"tower-service",
"tracing",
]
[[package]]
name = "tower"
version = "0.4.13"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b8fa9be0de6cf49e536ce1851f987bd21a43b771b09473c3549a6c853db37c1c"
dependencies = [
"futures-core",
"futures-util",
"indexmap 1.9.3",
"pin-project",
"pin-project-lite",
"rand",
"slab",
"tokio",
"tokio-util",
"tower-layer",
"tower-service",
"tracing",
]
[[package]]
name = "tower-http"
version = "0.4.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "61c5bb1d698276a2443e5ecfabc1008bf15a36c12e6a7176e7bf089ea9131140"
dependencies = [
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
"bitflags 2.6.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
"bytes",
"futures-core",
"futures-util",
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
"http",
"http-body",
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
"http-range-header",
Add `/metadata` and `/metadata-hash` endpoints (#461) ## Description This PR iterates on #459. Rather than serving the engine metadata it serves an arbitrary file, given by the command line argument `--introspection-metadata`. Specifying this argument gives rise to endpoints `/metadata` and `/metadata-hash`. ![image](https://github.com/hasura/v3-engine/assets/358550/63040f02-876a-4c29-8cf1-52a305ffff67) Update: We only load the file in at engine startup and serve that version. Changing the file on disk will not change what the engine serves. --------- Co-authored-by: Gil Mizrahi <gil@gilmi.net> V3_GIT_ORIGIN_REV_ID: db88adb5c08c4489cc1abd5fb5236b8d5ba51b9a
2024-04-12 00:31:55 +03:00
"httpdate",
"mime",
"mime_guess",
"percent-encoding",
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
"pin-project-lite",
Add `/metadata` and `/metadata-hash` endpoints (#461) ## Description This PR iterates on #459. Rather than serving the engine metadata it serves an arbitrary file, given by the command line argument `--introspection-metadata`. Specifying this argument gives rise to endpoints `/metadata` and `/metadata-hash`. ![image](https://github.com/hasura/v3-engine/assets/358550/63040f02-876a-4c29-8cf1-52a305ffff67) Update: We only load the file in at engine startup and serve that version. Changing the file on disk will not change what the engine serves. --------- Co-authored-by: Gil Mizrahi <gil@gilmi.net> V3_GIT_ORIGIN_REV_ID: db88adb5c08c4489cc1abd5fb5236b8d5ba51b9a
2024-04-12 00:31:55 +03:00
"tokio",
"tokio-util",
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
"tower-layer",
"tower-service",
"tracing",
]
[[package]]
name = "tower-layer"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.3.3"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "121c2a6cda46980bb0fcd1647ffaf6cd3fc79a013de288782836f6df9c48780e"
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
[[package]]
name = "tower-service"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.3.3"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "8df9b6e13f2d32c91b9bd719c00d1958837bc7dec474d94952798cc8e69eeec3"
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
[[package]]
name = "tracing"
version = "0.1.40"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c3523ab5a71916ccf420eebdf5521fcef02141234bbc0b8a49f2fdc4544364ef"
dependencies = [
"log",
"pin-project-lite",
"tracing-attributes",
"tracing-core",
]
[[package]]
name = "tracing-attributes"
version = "0.1.27"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "34704c8d6ebcbc939824180af020566b01a7c01f80641264eba0999f6c2b6be7"
dependencies = [
"proc-macro2",
"quote",
Bump syn from 2.0.75 to 2.0.76 (#1017) Bumps [syn](https://github.com/dtolnay/syn) from 2.0.75 to 2.0.76. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/syn/releases">syn's releases</a>.</em></p> <blockquote> <h2>2.0.76</h2> <ul> <li>Enforce that tail call <code>become</code> keyword is followed by an expression (<a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/syn/commit/ef3e9c6dde79be7590fc90278772663ca31c1a73"><code>ef3e9c6</code></a> Release 2.0.76</li> <li><a href="https://github.com/dtolnay/syn/commit/8f7365ff9685c8ca9527c2de409204179a3efcdf"><code>8f7365f</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a> from dtolnay/tailcall</li> <li><a href="https://github.com/dtolnay/syn/commit/6cddd9ea714fe034466b4f02d3f7abb484c65ea0"><code>6cddd9e</code></a> Make tail call expr mandatory</li> <li>See full diff in <a href="https://github.com/dtolnay/syn/compare/2.0.75...2.0.76">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=syn&package-manager=cargo&previous-version=2.0.75&new-version=2.0.76)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d261ad30ffeb10034a80f9044504cb9d6c7c1ff7
2024-08-26 14:39:45 +03:00
"syn 2.0.76",
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
]
[[package]]
name = "tracing-core"
version = "0.1.32"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c06d3da6113f116aaee68e4d601191614c9053067f9ab7f6edbcb161237daa54"
dependencies = [
"once_cell",
support OpenTelemetry zipkin propagator (#466) Support both W3C and Zipkin B3 headers and connectors will prefer B3 headers to extract traces because Cloud Run doesn't respect those headers. V3_GIT_ORIGIN_REV_ID: 1471b848e71d87420bc75b9adee60951f306c856
2024-04-16 17:55:54 +03:00
"valuable",
]
[[package]]
name = "tracing-log"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ee855f1f400bd0e5c02d150ae5de3840039a3f54b025156404e34c23c03f47c3"
dependencies = [
"log",
"once_cell",
"tracing-core",
]
[[package]]
name = "tracing-subscriber"
version = "0.3.18"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ad0f048c97dbd9faa9b7df56362b8ebcaa52adb06b498c050d2f4e32f90a7a8b"
dependencies = [
Bump diffy from 0.3.0 to 0.4.0 (#718) Bumps [diffy](https://github.com/bmwill/diffy) from 0.3.0 to 0.4.0. Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: a8d610058bfb0f0fd7af547882724457202c25f8
2024-06-17 08:29:16 +03:00
"nu-ansi-term 0.46.0",
support OpenTelemetry zipkin propagator (#466) Support both W3C and Zipkin B3 headers and connectors will prefer B3 headers to extract traces because Cloud Run doesn't respect those headers. V3_GIT_ORIGIN_REV_ID: 1471b848e71d87420bc75b9adee60951f306c856
2024-04-16 17:55:54 +03:00
"sharded-slab",
"smallvec",
"thread_local",
"tracing-core",
"tracing-log",
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
]
[[package]]
name = "tracing-util"
Use v3.0.0 as the version number. (#999) ### What Updates the version number to `3.0.0`, now we're officially at GA. ### How I updated the version number, and also updated some dependencies. The `Cargo.lock` file was not up to date. V3_GIT_ORIGIN_REV_ID: 3e9b784c8ad856556193e56aee9fa607fa8ce19e
2024-08-21 17:02:43 +03:00
version = "3.0.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
dependencies = [
re-add axum and machete-ignore it to fix tests run with cargo test (#418) <!-- Thank you for submitting this PR! :) --> ## Description For some reason, `cargo test` fails because of missing types in doc comment code, but `cargo nextest run` in CI does not. Re-adding `axum` as a dep dependency to `tracing-util` fixes this. --------- Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: 518e6faf702895d9c434056a57c40c2db6f4b0a8
2024-03-28 14:28:05 +03:00
"axum",
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
"derive_more",
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
"http",
Remove unused dependencies using `cargo machete`. (#413) `cargo machete` is a very useful tool that figures out when you aren't using a dependency. I have run this locally to remove unused dependencies. I've also added a CI job to make sure we catch these in the future. Sometimes it reports false positives, e.g. when a dependency isn't used directly but in macro-generated code (e.g. with `strum`). I have added `"ignored"` clauses to the `Cargo.toml` files where appropriate. V3_GIT_ORIGIN_REV_ID: ed015089b695cec8eeb03ce455d6dd3cd312a016
2024-03-28 12:16:54 +03:00
"opentelemetry",
Pass `TraceContextResponsePropagator` to `set_text_map_propagator` (#884) <!-- The PR description should answer 2 (maybe 3) important questions: --> ### What In a recent engine change, we changed some of our trace context mapping to use the shared settings consistently. However, we needed to make sure we included `TraceContextResponsePropagator`, which returns the `traceresponse` header. Request from console after this fix: <img width="810" alt="Screenshot 2024-07-25 at 11 58 30" src="https://github.com/user-attachments/assets/c8e73c56-87fd-49da-a887-f91cdb6d607a"> <!-- What is this PR trying to accomplish (and why, if it's not obvious)? --> <!-- Consider: do we need to add a changelog entry? --> ### How Adds `TraceContextResponsePropagator` to the global set of text map propagators. <!-- How is it trying to accomplish it (what are the implementation steps)? --> V3_GIT_ORIGIN_REV_ID: 48df6a6fe55e78a48f1dc6bf82304199a0a7e248
2024-07-25 14:30:04 +03:00
"opentelemetry-contrib",
add support for async span with parent context (#341) V3_GIT_ORIGIN_REV_ID: f24ff08407a4f00787dfb76a72f9de072b5a02a2
2024-03-15 12:25:41 +03:00
"opentelemetry-http",
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
"opentelemetry-otlp",
"opentelemetry-semantic-conventions",
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",
support OpenTelemetry zipkin propagator (#466) Support both W3C and Zipkin B3 headers and connectors will prefer B3 headers to extract traces because Cloud Run doesn't respect those headers. V3_GIT_ORIGIN_REV_ID: 1471b848e71d87420bc75b9adee60951f306c856
2024-04-16 17:55:54 +03:00
"opentelemetry-zipkin",
Remove unused dependencies using `cargo machete`. (#413) `cargo machete` is a very useful tool that figures out when you aren't using a dependency. I have run this locally to remove unused dependencies. I've also added a CI job to make sure we catch these in the future. Sometimes it reports false positives, e.g. when a dependency isn't used directly but in macro-generated code (e.g. with `strum`). I have added `"ignored"` clauses to the `Cargo.toml` files where appropriate. V3_GIT_ORIGIN_REV_ID: ed015089b695cec8eeb03ce455d6dd3cd312a016
2024-03-28 12:16:54 +03:00
"opentelemetry_sdk",
support OpenTelemetry zipkin propagator (#466) Support both W3C and Zipkin B3 headers and connectors will prefer B3 headers to extract traces because Cloud Run doesn't respect those headers. V3_GIT_ORIGIN_REV_ID: 1471b848e71d87420bc75b9adee60951f306c856
2024-04-16 17:55:54 +03:00
"tracing-subscriber",
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
]
[[package]]
name = "transitive"
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e31e716441126fedb8baecc6717d79467ccdbdfdd7eed33ba47850f53402ec57"
dependencies = [
Use `syn` v2 in our own macros. (#574) This upgrades `darling` and `schemars` too, so they also use `syn` v2. V3_GIT_ORIGIN_REV_ID: 731160389115dfa079fb1e13e831204d278f5a40
2024-05-14 10:49:52 +03:00
"darling",
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
"proc-macro2",
"quote",
Bump syn from 2.0.75 to 2.0.76 (#1017) Bumps [syn](https://github.com/dtolnay/syn) from 2.0.75 to 2.0.76. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/syn/releases">syn's releases</a>.</em></p> <blockquote> <h2>2.0.76</h2> <ul> <li>Enforce that tail call <code>become</code> keyword is followed by an expression (<a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/syn/commit/ef3e9c6dde79be7590fc90278772663ca31c1a73"><code>ef3e9c6</code></a> Release 2.0.76</li> <li><a href="https://github.com/dtolnay/syn/commit/8f7365ff9685c8ca9527c2de409204179a3efcdf"><code>8f7365f</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a> from dtolnay/tailcall</li> <li><a href="https://github.com/dtolnay/syn/commit/6cddd9ea714fe034466b4f02d3f7abb484c65ea0"><code>6cddd9e</code></a> Make tail call expr mandatory</li> <li>See full diff in <a href="https://github.com/dtolnay/syn/compare/2.0.75...2.0.76">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=syn&package-manager=cargo&previous-version=2.0.75&new-version=2.0.76)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d261ad30ffeb10034a80f9044504cb9d6c7c1ff7
2024-08-26 14:39:45 +03:00
"syn 2.0.76",
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
]
[[package]]
name = "try-lock"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.2.5"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "e421abadd41a4225275504ea4d6566923418b7f05506fbc9c0fe86ba7396114b"
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
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
[[package]]
name = "twox-hash"
version = "1.6.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "97fee6b57c6a41524a810daee9286c02d7752c4253064d0b05472833a438f675"
dependencies = [
"cfg-if",
"static_assertions",
]
support OpenTelemetry zipkin propagator (#466) Support both W3C and Zipkin B3 headers and connectors will prefer B3 headers to extract traces because Cloud Run doesn't respect those headers. V3_GIT_ORIGIN_REV_ID: 1471b848e71d87420bc75b9adee60951f306c856
2024-04-16 17:55:54 +03:00
[[package]]
name = "typed-builder"
version = "0.18.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "77739c880e00693faef3d65ea3aad725f196da38b22fdc7ea6ded6e1ce4d3add"
dependencies = [
"typed-builder-macro",
]
[[package]]
name = "typed-builder-macro"
version = "0.18.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1f718dfaf347dcb5b983bfc87608144b0bad87970aebcbea5ce44d2a30c08e63"
dependencies = [
"proc-macro2",
"quote",
Bump syn from 2.0.75 to 2.0.76 (#1017) Bumps [syn](https://github.com/dtolnay/syn) from 2.0.75 to 2.0.76. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/syn/releases">syn's releases</a>.</em></p> <blockquote> <h2>2.0.76</h2> <ul> <li>Enforce that tail call <code>become</code> keyword is followed by an expression (<a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/syn/commit/ef3e9c6dde79be7590fc90278772663ca31c1a73"><code>ef3e9c6</code></a> Release 2.0.76</li> <li><a href="https://github.com/dtolnay/syn/commit/8f7365ff9685c8ca9527c2de409204179a3efcdf"><code>8f7365f</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a> from dtolnay/tailcall</li> <li><a href="https://github.com/dtolnay/syn/commit/6cddd9ea714fe034466b4f02d3f7abb484c65ea0"><code>6cddd9e</code></a> Make tail call expr mandatory</li> <li>See full diff in <a href="https://github.com/dtolnay/syn/compare/2.0.75...2.0.76">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=syn&package-manager=cargo&previous-version=2.0.75&new-version=2.0.76)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d261ad30ffeb10034a80f9044504cb9d6c7c1ff7
2024-08-26 14:39:45 +03:00
"syn 2.0.76",
support OpenTelemetry zipkin propagator (#466) Support both W3C and Zipkin B3 headers and connectors will prefer B3 headers to extract traces because Cloud Run doesn't respect those headers. V3_GIT_ORIGIN_REV_ID: 1471b848e71d87420bc75b9adee60951f306c856
2024-04-16 17:55:54 +03:00
]
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
[[package]]
name = "typenum"
version = "1.17.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "42ff0bf0c66b8238c6f3b578df37d0b7848e55df8577b3f74f92a69acceeb825"
[[package]]
name = "ucd-trie"
version = "0.1.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ed646292ffc8188ef8ea4d1e0e0150fb15a5c2e12ad9b8fc191ae7a8a7f3c4b9"
[[package]]
name = "unicase"
version = "2.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f7d2d4dafb69621809a81864c9c1b864479e1235c0dd4e199924b9742439ed89"
dependencies = [
"version_check",
]
[[package]]
name = "unicode-bidi"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.3.15"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "08f95100a766bf4f8f28f90d77e0a5461bbdb219042e7679bebe79004fed8d75"
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
[[package]]
name = "unicode-ident"
version = "1.0.12"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3354b9ac3fae1ff6755cb6db53683adb661634f67557942dea4facebec0fee4b"
[[package]]
name = "unicode-normalization"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.1.23"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "a56d1686db2308d901306f92a263857ef59ea39678a5458e7cb17f01415101f5"
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
dependencies = [
"tinyvec",
]
[[package]]
name = "unicode-segmentation"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "1.11.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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "d4c87d22b6e3f4a18d4d40ef354e97c90fcb14dd91d7dc0aa9d8a1172ebf7202"
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
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
[[package]]
name = "unicode-width"
version = "0.1.13"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0336d538f7abc86d282a4189614dfaa90810dfc2c6f6427eaf88e16311dd225d"
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
[[package]]
name = "unreachable"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "382810877fe448991dfc7f0dd6e3ae5d58088fd0ea5e35189655f84e6814fa56"
dependencies = [
"void",
]
[[package]]
name = "untrusted"
version = "0.7.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a156c684c91ea7d62626509bce3cb4e1d9ed5c4d978f7b4352658f96a4c26b4a"
[[package]]
name = "url"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "2.5.2"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "22784dbdf76fdde8af1aeda5622b546b422b6fc585325248a2bf9f5e41e94d6c"
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
dependencies = [
"form_urlencoded",
Remove unused dependencies using `cargo machete`. (#413) `cargo machete` is a very useful tool that figures out when you aren't using a dependency. I have run this locally to remove unused dependencies. I've also added a CI job to make sure we catch these in the future. Sometimes it reports false positives, e.g. when a dependency isn't used directly but in macro-generated code (e.g. with `strum`). I have added `"ignored"` clauses to the `Cargo.toml` files where appropriate. V3_GIT_ORIGIN_REV_ID: ed015089b695cec8eeb03ce455d6dd3cd312a016
2024-03-28 12:16:54 +03:00
"idna",
"percent-encoding",
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
]
[[package]]
name = "urlencoding"
version = "2.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "daf8dba3b7eb870caf1ddeed7bc9d2a049f3cfdfae7cb521b087cc33ae4c49da"
[[package]]
name = "utf8parse"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
version = "0.2.2"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
checksum = "06abde3611657adf66d383f00b093d7faecc7fa57071cce2578660c9f1010821"
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
[[package]]
name = "uuid"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "1.10.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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "81dfa00651efa65069b0b6b651f4aaa31ba9e3c3ce0137aaad053604ee7e0314"
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
dependencies = [
"getrandom",
"serde",
]
support OpenTelemetry zipkin propagator (#466) Support both W3C and Zipkin B3 headers and connectors will prefer B3 headers to extract traces because Cloud Run doesn't respect those headers. V3_GIT_ORIGIN_REV_ID: 1471b848e71d87420bc75b9adee60951f306c856
2024-04-16 17:55:54 +03:00
[[package]]
name = "valuable"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "830b7e5d4d90034032940e4ace0d9a9a057e7a45cd94e6c007832e39edb82f6d"
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
[[package]]
name = "vcpkg"
version = "0.2.15"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "accd4ea62f7bb7a82fe23066fb0957d48ef677f6eeb8215f372f52e48bb32426"
[[package]]
name = "version_check"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.9.5"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "0b928f33d975fc6ad9f86c8f283853ad26bdd5b10b7f1542aa2fa15e2289105a"
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
[[package]]
name = "void"
version = "1.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6a02e4885ed3bc0f2de90ea6dd45ebcbb66dacffe03547fadbb0eeae2770887d"
[[package]]
name = "walkdir"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "2.5.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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "29790946404f91d9c5d06f9874efddea1dc06c5efe94541a7d6863108e3a5e4b"
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
dependencies = [
"same-file",
"winapi-util",
]
[[package]]
name = "want"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bfa7760aed19e106de2c7c0b581b509f2f25d3dacaf737cb82ac61bc6d760b0e"
dependencies = [
"try-lock",
]
[[package]]
name = "wasi"
version = "0.11.0+wasi-snapshot-preview1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9c8d87e72b64a3b4db28d11ce29237c246188f4f51057d65a7eab63b7987e423"
[[package]]
name = "wasm-bindgen"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.2.93"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "a82edfc16a6c469f5f44dc7b571814045d60404b55a0ee849f9bcfa2e63dd9b5"
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
dependencies = [
"cfg-if",
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"once_cell",
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
"wasm-bindgen-macro",
]
[[package]]
name = "wasm-bindgen-backend"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.2.93"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "9de396da306523044d3302746f1208fa71d7532227f15e347e2d93e4145dd77b"
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
dependencies = [
"bumpalo",
"log",
"once_cell",
"proc-macro2",
"quote",
Bump syn from 2.0.75 to 2.0.76 (#1017) Bumps [syn](https://github.com/dtolnay/syn) from 2.0.75 to 2.0.76. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/syn/releases">syn's releases</a>.</em></p> <blockquote> <h2>2.0.76</h2> <ul> <li>Enforce that tail call <code>become</code> keyword is followed by an expression (<a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/syn/commit/ef3e9c6dde79be7590fc90278772663ca31c1a73"><code>ef3e9c6</code></a> Release 2.0.76</li> <li><a href="https://github.com/dtolnay/syn/commit/8f7365ff9685c8ca9527c2de409204179a3efcdf"><code>8f7365f</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a> from dtolnay/tailcall</li> <li><a href="https://github.com/dtolnay/syn/commit/6cddd9ea714fe034466b4f02d3f7abb484c65ea0"><code>6cddd9e</code></a> Make tail call expr mandatory</li> <li>See full diff in <a href="https://github.com/dtolnay/syn/compare/2.0.75...2.0.76">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=syn&package-manager=cargo&previous-version=2.0.75&new-version=2.0.76)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d261ad30ffeb10034a80f9044504cb9d6c7c1ff7
2024-08-26 14:39:45 +03:00
"syn 2.0.76",
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
"wasm-bindgen-shared",
]
[[package]]
name = "wasm-bindgen-futures"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.4.43"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "61e9300f63a621e96ed275155c108eb6f843b6a26d053f122ab69724559dc8ed"
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
dependencies = [
"cfg-if",
"js-sys",
"wasm-bindgen",
"web-sys",
]
[[package]]
name = "wasm-bindgen-macro"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.2.93"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "585c4c91a46b072c92e908d99cb1dcdf95c5218eeb6f3bf1efa991ee7a68cccf"
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
dependencies = [
"quote",
"wasm-bindgen-macro-support",
]
[[package]]
name = "wasm-bindgen-macro-support"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.2.93"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "afc340c74d9005395cf9dd098506f7f44e38f2b4a21c6aaacf9a105ea5e1e836"
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
dependencies = [
"proc-macro2",
"quote",
Bump syn from 2.0.75 to 2.0.76 (#1017) Bumps [syn](https://github.com/dtolnay/syn) from 2.0.75 to 2.0.76. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/syn/releases">syn's releases</a>.</em></p> <blockquote> <h2>2.0.76</h2> <ul> <li>Enforce that tail call <code>become</code> keyword is followed by an expression (<a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/syn/commit/ef3e9c6dde79be7590fc90278772663ca31c1a73"><code>ef3e9c6</code></a> Release 2.0.76</li> <li><a href="https://github.com/dtolnay/syn/commit/8f7365ff9685c8ca9527c2de409204179a3efcdf"><code>8f7365f</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a> from dtolnay/tailcall</li> <li><a href="https://github.com/dtolnay/syn/commit/6cddd9ea714fe034466b4f02d3f7abb484c65ea0"><code>6cddd9e</code></a> Make tail call expr mandatory</li> <li>See full diff in <a href="https://github.com/dtolnay/syn/compare/2.0.75...2.0.76">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=syn&package-manager=cargo&previous-version=2.0.75&new-version=2.0.76)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d261ad30ffeb10034a80f9044504cb9d6c7c1ff7
2024-08-26 14:39:45 +03:00
"syn 2.0.76",
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
"wasm-bindgen-backend",
"wasm-bindgen-shared",
]
[[package]]
name = "wasm-bindgen-shared"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.2.93"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "c62a0a307cb4a311d3a07867860911ca130c3494e8c2719593806c08bc5d0484"
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
[[package]]
name = "web-sys"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.3.70"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "26fdeaafd9bd129f65e7c031593c24d62186301e0c72c8978fa1678be7d532c0"
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
dependencies = [
"js-sys",
"wasm-bindgen",
]
[[package]]
name = "winapi"
version = "0.3.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5c839a674fcd7a98952e593242ea400abe93992746761e38641405d28b00f419"
dependencies = [
"winapi-i686-pc-windows-gnu",
"winapi-x86_64-pc-windows-gnu",
]
[[package]]
name = "winapi-i686-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ac3b87c63620426dd9b991e5ce0329eff545bccbbb34f3be09ff6fb6ab51b7b6"
[[package]]
name = "winapi-util"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.1.9"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "cf221c93e13a30d793f7645a0e7762c55d169dbb0a49671918a2319d289b10bb"
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
dependencies = [
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"windows-sys 0.59.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
]
[[package]]
name = "winapi-x86_64-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "712e227841d057c1ee1cd2fb22fa7e5a5461ae8e48fa2ca79ec42cfc1931183f"
[[package]]
name = "windows-core"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "0.52.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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "33ab640c8d7e35bf8ba19b884ba838ceb4fba93a4e8c65a9059d08afcfc683d9"
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
dependencies = [
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"windows-targets 0.52.6",
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
]
[[package]]
name = "windows-sys"
version = "0.48.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "677d2418bec65e3338edb076e806bc1ec15693c5d0104683f2efe857f61056a9"
dependencies = [
"windows-targets 0.48.5",
]
[[package]]
name = "windows-sys"
version = "0.52.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "282be5f36a8ce781fad8c8ae18fa3f9beff57ec1b52cb3de0789201425d9a33d"
dependencies = [
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"windows-targets 0.52.6",
]
[[package]]
name = "windows-sys"
version = "0.59.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1e38bc4d79ed67fd075bcc251a1c39b32a1776bbe92e5bef1f0bf1f8c531853b"
dependencies = [
"windows-targets 0.52.6",
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
]
[[package]]
name = "windows-targets"
version = "0.48.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9a2fa6e2155d7247be68c096456083145c183cbbbc2764150dda45a87197940c"
dependencies = [
"windows_aarch64_gnullvm 0.48.5",
"windows_aarch64_msvc 0.48.5",
"windows_i686_gnu 0.48.5",
"windows_i686_msvc 0.48.5",
"windows_x86_64_gnu 0.48.5",
"windows_x86_64_gnullvm 0.48.5",
"windows_x86_64_msvc 0.48.5",
]
[[package]]
name = "windows-targets"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.52.6"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "9b724f72796e036ab90c1021d4780d4d3d648aca59e491e6b98e725b84e99973"
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
dependencies = [
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"windows_aarch64_gnullvm 0.52.6",
"windows_aarch64_msvc 0.52.6",
"windows_i686_gnu 0.52.6",
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
"windows_i686_gnullvm",
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"windows_i686_msvc 0.52.6",
"windows_x86_64_gnu 0.52.6",
"windows_x86_64_gnullvm 0.52.6",
"windows_x86_64_msvc 0.52.6",
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
]
[[package]]
name = "windows_aarch64_gnullvm"
version = "0.48.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2b38e32f0abccf9987a4e3079dfb67dcd799fb61361e53e2882c3cbaf0d905d8"
[[package]]
name = "windows_aarch64_gnullvm"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.52.6"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "32a4622180e7a0ec044bb555404c800bc9fd9ec262ec147edd5989ccd0c02cd3"
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
[[package]]
name = "windows_aarch64_msvc"
version = "0.48.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "dc35310971f3b2dbbf3f0690a219f40e2d9afcf64f9ab7cc1be722937c26b4bc"
[[package]]
name = "windows_aarch64_msvc"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.52.6"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "09ec2a7bb152e2252b53fa7803150007879548bc709c039df7627cabbd05d469"
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
[[package]]
name = "windows_i686_gnu"
version = "0.48.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a75915e7def60c94dcef72200b9a8e58e5091744960da64ec734a6c6e9b3743e"
[[package]]
name = "windows_i686_gnu"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.52.6"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "8e9b5ad5ab802e97eb8e295ac6720e509ee4c243f69d781394014ebfe8bbfa0b"
Upgrade all Rust dependencies. (#736) I was in the area. V3_GIT_ORIGIN_REV_ID: 46918a8b124a1a5853621e482d46ed51c42c868e
2024-06-20 16:38:57 +03:00
[[package]]
name = "windows_i686_gnullvm"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.52.6"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "0eee52d38c090b3caa76c563b86c3a4bd71ef1a819287c19d586d7334ae8ed66"
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
[[package]]
name = "windows_i686_msvc"
version = "0.48.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8f55c233f70c4b27f66c523580f78f1004e8b5a8b659e05a4eb49d4166cca406"
[[package]]
name = "windows_i686_msvc"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.52.6"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "240948bc05c5e7c6dabba28bf89d89ffce3e303022809e73deaefe4f6ec56c66"
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
[[package]]
name = "windows_x86_64_gnu"
version = "0.48.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "53d40abd2583d23e4718fddf1ebec84dbff8381c07cae67ff7768bbf19c6718e"
[[package]]
name = "windows_x86_64_gnu"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.52.6"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "147a5c80aabfbf0c7d901cb5895d1de30ef2907eb21fbbab29ca94c5b08b1a78"
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
[[package]]
name = "windows_x86_64_gnullvm"
version = "0.48.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0b7b52767868a23d5bab768e390dc5f5c55825b6d30b86c844ff2dc7414044cc"
[[package]]
name = "windows_x86_64_gnullvm"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.52.6"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "24d5b23dc417412679681396f2b49f3de8c1473deb516bd34410872eff51ed0d"
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
[[package]]
name = "windows_x86_64_msvc"
version = "0.48.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ed94fce61571a4006852b7389a063ab983c02eb1bb37b47f8272ce92d06d9538"
[[package]]
name = "windows_x86_64_msvc"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.52.6"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "589f6da84c646204747d1270a2a5661ea66ed1cced2631d546fdfb155959f9ec"
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
[[package]]
name = "winreg"
version = "0.50.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "524e57b2c537c0f9b1e69f1965311ec12182b4122e45035b1508cd24d2adadb1"
dependencies = [
"cfg-if",
"windows-sys 0.48.0",
]
[[package]]
name = "wyz"
version = "0.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "05f360fc0b24296329c78fda852a1e9ae82de9cf7b27dae4b7f62f118f77b9ed"
dependencies = [
"tap",
]
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
[[package]]
name = "xz2"
version = "0.1.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "388c44dc09d76f1536602ead6d325eb532f5c122f17782bd57fb47baeeb767e2"
dependencies = [
"lzma-sys",
]
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
[[package]]
name = "yansi"
version = "0.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "09041cd90cf85f7f8b2df60c646f853b7f535ce68f85244eb6731cf89fa498ec"
[[package]]
name = "yansi"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
version = "1.0.1"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade ndc-spec and opentelemetry, and add a traceresponse header. (#416) <!-- Thank you for submitting this PR! :) --> ## Description I have upgraded ndc-spec to v0.1.1. This pulls in an upgrade to opentelemetry v0.22 so I've done that too. We had issues with the `traceresponse` response header disappearing when using an opentelemetry version > v0.20. This seems to be resolved here, probably because we have pinned a single version of opentelemetry rather than loading multiple at once. I added the `traceresponse` header to verify this, and have left it in because it doesn't seem to hurt anything. I verified that everything works as expected with the OSS components, but not multitenant. ## Changelog - Add a changelog entry (in the "Changelog entry" section below) if the changes in this PR have any user-facing impact. See [changelog guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide). - If no changelog is required ignore/remove this section and add a `no-changelog-required` label to the PR. ### Product _(Select all products this will be available in)_ - [x] community-edition - [x] cloud <!-- product : end : DO NOT REMOVE --> ### Type <!-- See changelog structure: https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog --> _(Select only one. In case of multiple, choose the most appropriate)_ - [ ] highlight - [x] enhancement - [ ] bugfix - [ ] behaviour-change - [ ] performance-enhancement - [ ] security-fix <!-- type : end : DO NOT REMOVE --> ### Changelog entry <!-- - Add a user understandable changelog entry - Include all details needed to understand the change. Try including links to docs or issues if relevant - For Highlights start with a H4 heading (#### <entry title>) - Get the changelog entry reviewed by your team --> v3 engine GraphQL queries now include a "traceresponse" header. <!-- changelog-entry : end : DO NOT REMOVE --> <!-- changelog : end : DO NOT REMOVE --> V3_GIT_ORIGIN_REV_ID: f37b6bdb1331b55c49f0bd953f522f5eca298d1d
2024-03-28 19:20:27 +03:00
checksum = "cfe53a6657fd280eaa890a3bc59152892ffa3e30101319d168b781ed6529b049"
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
[[package]]
name = "yasna"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e262a29d0e61ccf2b6190d7050d4b237535fc76ce4c1210d9caa316f71dffa75"
dependencies = [
"num-bigint",
]
[[package]]
name = "zerocopy"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.7.35"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "1b9b4fd18abc82b8136838da5d50bae7bdea537c574d8dc1a34ed098d6c166f0"
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
dependencies = [
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
"byteorder",
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
"zerocopy-derive",
]
[[package]]
name = "zerocopy-derive"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.7.35"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "fa4f8080344d4671fb4e831a13ad1e68092748387dfc4f55e356242fae12ce3e"
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
dependencies = [
"proc-macro2",
"quote",
Bump syn from 2.0.75 to 2.0.76 (#1017) Bumps [syn](https://github.com/dtolnay/syn) from 2.0.75 to 2.0.76. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/syn/releases">syn's releases</a>.</em></p> <blockquote> <h2>2.0.76</h2> <ul> <li>Enforce that tail call <code>become</code> keyword is followed by an expression (<a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/syn/commit/ef3e9c6dde79be7590fc90278772663ca31c1a73"><code>ef3e9c6</code></a> Release 2.0.76</li> <li><a href="https://github.com/dtolnay/syn/commit/8f7365ff9685c8ca9527c2de409204179a3efcdf"><code>8f7365f</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a> from dtolnay/tailcall</li> <li><a href="https://github.com/dtolnay/syn/commit/6cddd9ea714fe034466b4f02d3f7abb484c65ea0"><code>6cddd9e</code></a> Make tail call expr mandatory</li> <li>See full diff in <a href="https://github.com/dtolnay/syn/compare/2.0.75...2.0.76">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=syn&package-manager=cargo&previous-version=2.0.75&new-version=2.0.76)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d261ad30ffeb10034a80f9044504cb9d6c7c1ff7
2024-08-26 14:39:45 +03:00
"syn 2.0.76",
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
]
[[package]]
name = "zeroize"
Update to Rust v1.80.1. (#1002) ### What Upgrade to the latest version of Rust. ### How I modified `rust-toolchain.toml` and ran `cargo update`. V3_GIT_ORIGIN_REV_ID: 5fe675ee5dc568cd24de542c826ffd2d355f90ff
2024-08-22 11:08:47 +03:00
version = "1.4.3"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update to Rust v1.80.1. (#1002) ### What Upgrade to the latest version of Rust. ### How I modified `rust-toolchain.toml` and ran `cargo update`. V3_GIT_ORIGIN_REV_ID: 5fe675ee5dc568cd24de542c826ffd2d355f90ff
2024-08-22 11:08:47 +03:00
checksum = "d68d9dcec5f9b43a30d38c49f91dfedfaac384cb8f085faca366c26207dd1619"
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
dependencies = [
"zeroize_derive",
]
[[package]]
name = "zeroize_derive"
version = "1.4.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ce36e65b0d2999d2aafac989fb249189a141aee1f53c612c1f37d72631959f69"
dependencies = [
"proc-macro2",
"quote",
Bump syn from 2.0.75 to 2.0.76 (#1017) Bumps [syn](https://github.com/dtolnay/syn) from 2.0.75 to 2.0.76. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dtolnay/syn/releases">syn's releases</a>.</em></p> <blockquote> <h2>2.0.76</h2> <ul> <li>Enforce that tail call <code>become</code> keyword is followed by an expression (<a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dtolnay/syn/commit/ef3e9c6dde79be7590fc90278772663ca31c1a73"><code>ef3e9c6</code></a> Release 2.0.76</li> <li><a href="https://github.com/dtolnay/syn/commit/8f7365ff9685c8ca9527c2de409204179a3efcdf"><code>8f7365f</code></a> Merge pull request <a href="https://redirect.github.com/dtolnay/syn/issues/1725">#1725</a> from dtolnay/tailcall</li> <li><a href="https://github.com/dtolnay/syn/commit/6cddd9ea714fe034466b4f02d3f7abb484c65ea0"><code>6cddd9e</code></a> Make tail call expr mandatory</li> <li>See full diff in <a href="https://github.com/dtolnay/syn/compare/2.0.75...2.0.76">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=syn&package-manager=cargo&previous-version=2.0.75&new-version=2.0.76)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> V3_GIT_ORIGIN_REV_ID: d261ad30ffeb10034a80f9044504cb9d6c7c1ff7
2024-08-26 14:39:45 +03:00
"syn 2.0.76",
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
]
[[package]]
name = "zstd"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "0.13.2"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "fcf2b778a664581e31e389454a7072dab1647606d44f7feea22cd5abb9c9f3f9"
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
dependencies = [
"zstd-safe",
]
[[package]]
name = "zstd-safe"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "7.2.1"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "54a3ab4db68cea366acc5c897c7b4d4d1b8994a9cd6e6f841f8964566a419059"
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
dependencies = [
"zstd-sys",
]
[[package]]
name = "zstd-sys"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
version = "2.0.12+zstd.1.5.6"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
Update dependencies in preparation for some cloud work. (#972) ### What Update dependencies in preparation for some cloud work, and move dependency versions to the workspace. ### How ``` $ cargo update ``` V3_GIT_ORIGIN_REV_ID: a42ba0c8a1cb376280f9771abd7d1f4f7bf19b84
2024-08-15 12:04:57 +03:00
checksum = "0a4e40c320c3cb459d9a9ff6de98cff88f4751ee9275d140e2be94a2b74e4c13"
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
dependencies = [
"cc",
"pkg-config",
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
]
Reference in New Issue Copy Permalink