Update i18n-tasks: 0.9.21 → 0.9.23 (minor) #1836
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.
We've updated a dependency and here is what you need to know:
Additionally, the update changed a few other dependencies as well:
You should probably take a good look at the info here and the test results before merging this pull request, of course.
What changed?
✳️ i18n-tasks (0.9.21 → 0.9.23) · Repo · Changelog
Release Notes
From the Github release:
Fixes DeepL locale handling. #49d6d2b6
Commits
See the full diff on Github. The new version differs by 14 commits:
Bump to 0.9.23
Refactor: Move translator classes to their own dir
DeepL: Convert locales to a compatible format
Bump to 0.9.22
DeepL fixes
Introduce a base class for translation impls
Make env API keys take priority over config file
Follow-up on #294
add DeepL Pro artificial intelligence translation service (#294)
Remove country from locale before Google translate
Try the new CodeClimate Test Reporter
Travis: Use latest jruby known to travis
Update and lock rubocop
CI: Bump minimum cc-test-reporter instead of locking simplecov
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
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
.