Update cloudinary 1.29.0 → 2.0.2 (major) #3365
Merged
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.
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?
✳️ cloudinary (1.29.0 → 2.0.2) · Repo · Changelog
Release Notes
2.0.2
2.0.1
2.0.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 15 commits:
Version 2.0.2
Fix CarrierWave `store!` method
Version 2.0.1
Fix rake tasks
Version 2.0.0
Fix rake tasks
Update sample syntax
Update `Version Support` in `README`
Remove deprecated methods
Filter users by last login in `users` Provisioning API
Support chunked uploads with CarrierWave
Add support for URL Analytics
Set config `secure` to `true` by default
Add support for `analyze` API
Replace `rest-client` with `faraday`
🆕 faraday-follow_redirects (added, 0.3.0)
🆕 faraday-multipart (added, 1.0.4)
🆕 multipart-post (added, 2.4.0)
🗑️ aws_cf_signer (removed)
🗑️ domain_name (removed)
🗑️ http-accept (removed)
🗑️ http-cookie (removed)
🗑️ mime-types (removed)
🗑️ mime-types-data (removed)
🗑️ netrc (removed)
🗑️ rest-client (removed)
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