Note that there are no changes from version 1.2022.2 (other than the version). The 2022c release of the Time Zone Database does not include any time zone data changes from 2022b.
Changed DateTime results to always use the proleptic Gregorian calendar. This affects DateTime results prior to 1582-10-15 and any arithmetic performed on the results that would produce a secondary result prior to 1582-10-15.
Added support for eager loading all the time zone and country data by calling either TZInfo::DataSource#eager_load! or TZInfo.eager_load!. Compatible with Ruby On Rails' eager_load_namespaces. #129.
Ignore the SECURITY file from Arch Linux's tzdata package. #134.
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)
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?
✳️ tzinfo-data (1.2021.1 → 1.2022.3) · Repo
Release Notes
1.2022.3
1.2022.2
1.2022.1
1.2021.5
1.2021.4
1.2021.3
1.2021.2
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 16 commits:
Update to tzdata version 2022c.
Update to tzdata version 2022b.
Update to tzdata version 2022a.
Handle failure indications output by zdump 2022a.
Rebuild modules for 2022 (adding an additional year of future data).
Use File.exist? instead of File.exists?.
Use Ruby 3.1 for tests.
Update copyright years.
Use GitHub Actions for CI.
Update to tzdata version 2021e.
Update to tzdata version 2021d.
Update to tzdata version 2021c.
Ignore the SECURITY file first included in 2021c.
Update to tzdata version 2021b.
Support zdump 2021b output in definition tests.
Update the tzdb gpg key.
✳️ tzinfo (2.0.4 → 2.0.5) · Repo · Changelog
Release Notes
2.0.5
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 30 commits:
Preparing v2.0.5.
Add v0.3.61 and v1.2.10 from the 0.3 and 1.2 branches.
Fix relative path loading tests.
Add a top level eager_load! method for Rails compatibility.
Support preloading all data from a DataSource.
Clarify that both files and directories are excluded.
Tidy up of security file ignoring.
Merge pull request #133.
Workaround for 'Permission denied - NUL' errors with JRuby on Windows.
ignore SECURITY file for Arch tzdata package
Add Ruby 3.1.
Update copyright years.
Update copyright years.
Fix documentation.
Fix a typo.
Continue to use philr/setup-ruby@legacy for Ruby 2.0.0 x86 on Windows.
Add JRuby 9.3 and update to TruffleRuby 21.
Switch to ruby/setup-ruby for 1.9.3 (non-Windows) and 2.0.0.
Always return DateTime results using the proleptic Gregorian calendar.
Tidy up syntax.
Fix a grammatical error.
Add version 0.3.60 from the 0.3 branch.
Remove an unnecessary or.
Add RubyGems logo.
Ignore more warnings from sub-processes.
Mark truffleruby as experimental.
Limit json to < 2.5.0 on Windows Ruby 2.0.
Switch to GitHub Actions for CI.
[ci skip] Add version 0.3.59 from the 0.3 branch.
[ci skip] Improve formatting.
↗️ concurrent-ruby (indirect, 1.1.8 → 1.1.10) · Repo · Changelog
Release Notes
1.1.10
1.1.9 (from changelog)
Does any of this look wrong? Please let us know.
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
.All Depfu comment commands
This change is