Skip to content

feat: upgrade typesense-sync to be v30 compatible [wip]#24631

Closed
onceLearner wants to merge 2 commits intovectordotdev:masterfrom
onceLearner:reda.elissati/web-8160-upgrade-typesense-sync-v30
Closed

feat: upgrade typesense-sync to be v30 compatible [wip]#24631
onceLearner wants to merge 2 commits intovectordotdev:masterfrom
onceLearner:reda.elissati/web-8160-upgrade-typesense-sync-v30

Conversation

@onceLearner
Copy link
Contributor

@onceLearner onceLearner commented Feb 10, 2026

Summary

  • Upgrade typesense-sync to v2.0.0 to be Compatible with Cluster v30
  • typesense.config.json in accordance with package updates, including schema definition for easier updates in the future
  • Use new syntax for the typesense sync

Vector configuration

How did you test this PR?

Change Type

  • Bug fix
  • New feature
  • Non-functional (chore, refactoring, docs)
  • Performance

Is this a breaking change?

  • Yes
  • No

Does this PR include user facing changes?

  • Yes. Please add a changelog fragment based on our guidelines.
  • No. A maintainer will apply the no-changelog label to this PR.

References

Notes

  • Please read our Vector contributor resources.
  • Do not hesitate to use @vectordotdev/vector to reach out to us regarding this PR.
  • Some CI checks run only after we manually approve them.
    • We recommend adding a pre-push hook, please see this template.
    • Alternatively, we recommend running the following locally before pushing to the remote branch:
      • make fmt
      • make check-clippy (if there are failures it's possible some of them can be fixed with make clippy-fix)
      • make test
  • After a review is requested, please avoid force pushes to help us review incrementally.
    • Feel free to push as many commits as you want. They will be squashed into one before merging.
    • For example, you can run git merge origin master and git push.
  • If this PR introduces changes Vector dependencies (modifies Cargo.lock), please
    run make build-licenses to regenerate the license inventory and commit the changes (if any). More details here.

@onceLearner onceLearner requested review from a team as code owners February 10, 2026 10:04
@github-actions
Copy link


Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.


I have read the CLA Document and I hereby sign the CLA


You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.

@onceLearner onceLearner changed the base branch from master to website February 11, 2026 09:09
@onceLearner onceLearner requested review from a team as code owners February 11, 2026 09:09
@onceLearner onceLearner changed the base branch from website to master February 11, 2026 09:19
@github-actions github-actions bot locked and limited conversation to collaborators Feb 11, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant