chore: Update packages to next 16.3 preview 9#722
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
💡 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" |
There was a problem hiding this comment.
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 👍 / 👎.
Improving Documentation
pnpm lint:fixto fix formatting issues before opening the PR.Description
What?
Why?