Skip to content

Upgrade dependencies#6546

Open
guilload wants to merge 2 commits into
mainfrom
guilload/upgrade-deps
Open

Upgrade dependencies#6546
guilload wants to merge 2 commits into
mainfrom
guilload/upgrade-deps

Conversation

@guilload

Copy link
Copy Markdown
Member

No description provided.

@guilload guilload requested review from a team as code owners June 24, 2026 21:26
@guilload guilload requested a review from nadav-govari June 24, 2026 21:26
serde_json = { workspace = true }
tantivy = { workspace = true }
time = { workspace = true }
time-fmt = "0.3.8"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why is this not in the workspace-level Cargo.toml?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think some rare deps that are only used in sub packages we haven't moved to workspace level. Let me clean this up.

@guilload guilload force-pushed the guilload/upgrade-deps branch from 09e3bd3 to a1fcb64 Compare July 7, 2026 21:32
@guilload guilload requested a review from trinity-1686a July 7, 2026 21:35
@guilload guilload force-pushed the guilload/upgrade-deps branch from a1fcb64 to b9a4f58 Compare July 7, 2026 21:36

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b9a4f58104

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread quickwit/Cargo.toml
serde_json_borrow = "0.9"
serde_qs = { version = "0.15" }
serde_with = "3.20"
serde_qs = { version = "1.1" }

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Preserve bare refresh query parsing

When an Elasticsearch bulk request uses a bare ?refresh parameter (no =), ElasticBulkOptions is supposed to treat it as ElasticRefresh::True for compatibility, and the existing test covers serde_qs::from_str::<ElasticBulkOptions>("refresh"). With serde_qs 1.1, that bare parameter is deserialized as a no-value/unit for enum fields instead of the empty-string alias, so this request now fails query parsing and returns 400 rather than forcing a refresh; please either adapt the refresh parser or avoid this serde_qs behavior change.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants