fix(deps): update dependency typesense/typesense-php to v5 #61
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^4.9
->^5.0
Release Notes
typesense/typesense-php (typesense/typesense-php)
v5.0.0
Compare Source
What's Changed
fix: URI encode user-inputted string by @phiHero in https://github.com/typesense/typesense-php/pull/76
Resource names are now URL-encoded by the library automatically. If you are using an older version of the library and doing URL encoding of Typesense resource names in your application (eg: collection names, aliases, document IDs, etc), you now want to remove that from your application code and let the library handle the URL encoding for you, to prevent double URL encoding.
Full Changelog: typesense/typesense-php@v4.9.3...v5.0.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.