Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.
All Depfu comment commands
@depfu rebase
Rebases against your default branch and redoes this update
@depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@depfu cancel merge
Cancels automatic merging of this PR
@depfu close
Closes this PR and deletes the branch
@depfu reopen
Restores the branch and reopens this PR (if it's closed)
@depfu pause
Ignores all future updates for this dependency and closes this PR
@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ @algolia/client-search (4.17.2 → 4.19.1) · Repo · Changelog
Release Notes
4.19.1
4.19.0
4.18.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 8 commits:
chore: release v4.19.1 (#1473)
fix(recommend): Add Type RecommendQueriesResponse from old MultipleQueriesResponse for recommend (#1472)
chore: release v4.19.0 (#1471)
feat(recommend): add "Looking Similar" model (#1469)
feat(abtests): add outlier count to variant response payload (#1467)
chore: release v4.18.0 (#1466)
fix(types): union SearchForFacetValuesResponse type for multipleQueries (#1460)
feat(cache-browser-local-storage): Implemented TTL support to cached items (#1457)
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands