-
Notifications
You must be signed in to change notification settings - Fork 65
chore(deps): update dependencies #1427
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update dependencies #1427
Conversation
Thank you for the PR! I will re-push to start the workflows, and will make some adjustments for the code. |
Newer versions of graphql crates change the order of properties in introspection responses (or maybe it's in the tooling?), here is a diff of normalized graphql schema: difftests/proxy/graphql_schema.t.err.json --- 1/7 --- JSON 3 3 "data": { 4 4 "__schema": { 5 5 "directives": [ . 6 { . 7 "args": [ . 8 { . 9 "defaultValue": null, . 10 "description": null, . 11 "name": "reason", . 12 "type": { . 13 "kind": "NON_NULL", . 14 "name": null, . 15 "ofType": { . 16 "kind": "SCALAR", . 17 "name": "String", . 18 "ofType": null . 19 } . 20 } . 21 } . 22 ], . 23 "description": null, . 24 "locations": [ . 25 "FIELD_DEFINITION", . 26 "ENUM_VALUE" . 27 ], . 28 "name": "deprecated" . 29 }, 6 30 { 7 31 "args": [ 8 32 { converted with LLM for better highlighting -- not a valid diff--- a/tests/proxy/graphql_schema.t.err.json
+++ b/tests/proxy/graphql_schema.t.err.json
@@ -3,6 +3,29 @@
"data": {
"__schema": {
"directives": [
+ {
+ "args": [
+ {
+ "defaultValue": null,
+ "description": null,
+ "name": "reason",
+ "type": {
+ "kind": "NON_NULL",
+ "name": null,
+ "ofType": {
+ "kind": "SCALAR",
+ "name": "String",
+ "ofType": null
+ }
+ }
+ }
+ ],
+ "description": null,
+ "locations": [
+ "FIELD_DEFINITION",
+ "ENUM_VALUE"
+ ],
+ "name": "deprecated"
+ },
{
"args": [
{
@@ -53,6 +76,28 @@
"INLINE_FRAGMENT"
],
"name": "skip"
+ },
+ {
+ "args": [
+ {
+ "defaultValue": null,
+ "description": null,
+ "name": "url",
+ "type": {
+ "kind": "NON_NULL",
+ "name": null,
+ "ofType": {
+ "kind": "SCALAR",
+ "name": "String",
+ "ofType": null
+ }
+ }
+ }
+ ],
+ "description": null,
+ "locations": [
+ "SCALAR"
+ ],
+ "name": "specifiedBy"
}
],
"mutationType": {
@@ -1558,6 +1603,20 @@
}
}
},
+ {
+ "args": [],
+ "deprecationReason": null,
+ "description": null,
+ "isDeprecated": false,
+ "name": "isRepeatable",
+ "type": {
+ "kind": "NON_NULL",
+ "name": null,
+ "ofType": {
+ "kind": "SCALAR",
+ "name": "Boolean",
+ "ofType": null
+ }
+ }
+ },
{
"args": [],
"deprecationReason": null,
@@ -1664,12 +1723,33 @@
"isDeprecated": false,
"name": "FIELD"
},
+ {
+ "deprecationReason": null,
+ "description": null,
+ "isDeprecated": false,
+ "name": "SCALAR"
+ },
{
"deprecationReason": null,
"description": null,
"isDeprecated": false,
"name": "FRAGMENT_DEFINITION"
},
+ {
+ "deprecationReason": null,
+ "description": null,
+ "isDeprecated": false,
+ "name": "FIELD_DEFINITION"
+ },
+ {
+ "deprecationReason": null,
+ "description": null,
+ "isDeprecated": false,
+ "name": "VARIABLE_DEFINITION"
+ },
{
"deprecationReason": null,
"description": null,
@@ -1681,6 +1761,12 @@
"description": null,
"isDeprecated": false,
"name": "INLINE_FRAGMENT"
+ },
+ {
+ "deprecationReason": null,
+ "description": null,
+ "isDeprecated": false,
+ "name": "ENUM_VALUE"
}
],
"fields": null,
@@ -1935,6 +2021,17 @@
"description": null,
"enumValues": null,
"fields": [
+ {
+ "args": [],
+ "deprecationReason": null,
+ "description": null,
+ "isDeprecated": false,
+ "name": "description",
+ "type": {
+ "kind": "SCALAR",
+ "name": "String",
+ "ofType": null
+ }
+ },
{
"args": [],
"deprecationReason": null,
@@ -2058,6 +2155,17 @@
"ofType": null
}
},
+ {
+ "args": [],
+ "deprecationReason": null,
+ "description": null,
+ "isDeprecated": false,
+ "name": "specifiedByUrl",
+ "type": {
+ "kind": "SCALAR",
+ "name": "String",
+ "ofType": null
+ }
+ },
{
"args": [],
"deprecationReason": null, |
verified the release container. |
merging -- thanks again! |
Just confirmed -- we can remove jaeger crates, since jaeger now supports ingestion of otel. This will allow to upgrade all related crates. |
Great to see that you could fix all remaining problems! Because many crates are unmaintained, are you open to using alternatives? |
Yes, any maintained alternatives are fine, as long as it doesn't blow up Cargo.lock too much -- that's the main concern. |
Updated
Not updated