We've tested your project with an updated dependency and the build failed.
This version is either within the version range you specified or you haven't specified a version/range. To be able to test your project with the new version, we've taken the liberty of pinning the version for this branch and pull request.
name
version specification
new version
i18n
~> 1.0
1.13.0
Unfortunately, we encountered failing tests after pinning. This means that this new version is not compatible with your project and the test failure will potentially also happen on fresh installs.
If you have correctly specified a semantic versioning version range, you should probably also file an issue with the upstream project as they might have released an update that's breaking SemVer rules, which is not cool. (But then again, not all projects explicitly follow SemVer)
We've left the pull request open for you to investigate this issue. Please don't merge it as is, because, again, we've pinned the version of i18n for this test run.
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 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)
We've tested your project with an updated dependency and the build failed.
This version is either within the version range you specified or you haven't specified a version/range. To be able to test your project with the new version, we've taken the liberty of pinning the version for this branch and pull request.
Unfortunately, we encountered failing tests after pinning. This means that this new version is not compatible with your project and the test failure will potentially also happen on fresh installs.
If you have correctly specified a semantic versioning version range, you should probably also file an issue with the upstream project as they might have released an update that's breaking SemVer rules, which is not cool. (But then again, not all projects explicitly follow SemVer)
We've left the pull request open for you to investigate this issue. Please don't merge it as is, because, again, we've pinned the version of i18n for this test run.
What changed?
✳️ i18n (~> 1.0 → 1.13.0) · Repo · Changelog
Release Notes
1.13.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 24 commits:
Bump to 1.13.0
Merge pull request #649 from fatkodima/fix-interpolate-same-object
Return same string object when no interpolations were made
Merge pull request #651 from fatkodima/optimizations
Merge pull request #650 from fatkodima/stub_const
Optimize `I18n.t`
Properly stub constants
Merge pull request #637 from movermeyer/movermeyer/nested_pluralization_with_base_backend
Merge pull request #647 from misdoro/exists_scope
Merge pull request #634 from movermeyer/movermeyer/explicit_0_1_and_lateral_inheritance
Allow passing scope argument to exists?
Merge pull request #644 from mensfeld/master
Merge pull request #1 from mensfeld/patch-1
Update simple.rb
Create funding.yml
Merge pull request #640 from movermeyer/movermeyer/date_meridian_indicators
Merge pull request #642 from nickcampbell18/patch-1
Fix load_path example in README.md
Merge pull request #627 from lucapericlp/master
Add support for meridian indicators on `Date` objects
Revert #503 changes for Backend::Base
Merge pull request #636 from movermeyer/movermeyer/pluralization_and_symbol_resolution
Fix symbol resolving with pluralization
Get closer to full CLDR pluralization support
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