Skip to content

chore: Update packages to next 16.3 preview 9#722

Merged
aXenDeveloper merged 1 commit into
canaryfrom
chore--Update-packages-to-next-16.3-preview-9
Jul 23, 2026
Merged

chore: Update packages to next 16.3 preview 9#722
aXenDeveloper merged 1 commit into
canaryfrom
chore--Update-packages-to-next-16.3-preview-9

Conversation

@aXenDeveloper

Copy link
Copy Markdown
Owner

Improving Documentation

Description

What?

Why?

@vercel

vercel Bot commented Jul 23, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
vitnode-docs Ready Ready Preview, Comment Jul 23, 2026 5:10pm

@aXenDeveloper
aXenDeveloper merged commit 0000862 into canary Jul 23, 2026
5 checks passed
@aXenDeveloper
aXenDeveloper deleted the chore--Update-packages-to-next-16.3-preview-9 branch July 23, 2026 17:13

@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: 773c56d478

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

},
"dependencies": {
"@elastic/elasticsearch": "^8.0.0"
"@elastic/elasticsearch": "^9.4.2"

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 Keep the Elasticsearch client compatible with ES 8 installs

When this adapter is used against an existing Elasticsearch 8 cluster, this dependency bump silently replaces the 8.x client with a 9.x client. Elastic’s compatibility policy is forward-oriented (upgrade the server before the client) and does not guarantee that newer clients work against older servers, so published @vitnode/elasticsearch users who have not migrated their self-hosted/Cloud cluster to ES 9 can start seeing runtime request failures after a package update. Keep the range on 8.x until the adapter is documented as ES9-only or supports both client majors.

Useful? React with 👍 / 👎.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant