Update tzinfo-data: 1.2021.1 → 1.2022.5 (minor)

[depfu[bot]]

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.5) · Repo

Release Notes

1.2022.5

Based on version 2022e of the IANA Time Zone Database (https://mm.icann.org/pipermail/tz-announce/2022-October/000074.html).

1.2022.4

Based on version 2022d of the IANA Time Zone Database (https://mm.icann.org/pipermail/tz-announce/2022-September/000073.html).

1.2022.3

Based on version 2022c of the IANA Time Zone Database (https://mm.icann.org/pipermail/tz-announce/2022-August/000072.html).

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.

1.2022.2

Based on version 2022b of the IANA Time Zone Database (https://mm.icann.org/pipermail/tz-announce/2022-August/000071.html).

1.2022.1

Based on version 2022a of the IANA Time Zone Database (https://mm.icann.org/pipermail/tz-announce/2022-March/000070.html).

1.2021.5

Based on version 2021e of the IANA Time Zone Database (https://mm.icann.org/pipermail/tz-announce/2021-October/000069.html).

1.2021.4

Based on version 2021d of the IANA Time Zone Database (https://mm.icann.org/pipermail/tz-announce/2021-October/000068.html).

1.2021.3

Based on version 2021c of the IANA Time Zone Database (https://mm.icann.org/pipermail/tz-announce/2021-October/000067.html).

1.2021.2

Based on version 2021b of the IANA Time Zone Database (https://mm.icann.org/pipermail/tz-announce/2021-September/000066.html).

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 19 commits:

• Update dependencies on actions/checkout and actions/cache.
• Update to tzdata version 2022e.
• Update to tzdata version 2022d.
• 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

• 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.

TZInfo v2.0.5 on RubyGems.org

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

concurrent-ruby:

• (#951) Set the Ruby compatibility version at 2.2
• (#939, #933) The caller_runs fallback policy no longer blocks reads from the job queue by worker threads
• (#938, #761, #652) You can now explicitly prune_pool a thread pool (Sylvain Joyeux)
• (#937, #757, #670) We switched the Yahoo stock API for demos to Alpha Vantage (Gustavo Caso)
• (#932, #931) We changed how SafeTaskExecutor handles local jump errors (Aaron Jensen)
• (#927) You can use keyword arguments in your initialize when using Async (Matt Larraz)
• (#926, #639) We removed timeout from TimerTask because it wasn't sound, and now it's a no-op with a warning (Jacob Atzen)
• (#919) If you double-lock a re-entrant read-write lock, we promote to locked for writing (zp yuan)
• (#915) monotonic_time now accepts an optional unit parameter, as Ruby's clock_gettime (Jean Boussier)

1.1.9 (from changelog)

concurrent-ruby:

• (#866) Child promise state not set to :pending immediately after #execute when parent has completed
• (#905, #872) Fix RubyNonConcurrentPriorityQueue#delete method
• (2df0337d) Make sure locks are not shared on shared when objects are dup/cloned
• (#900, #906, #796, #847, #911) Fix Concurrent::Set tread-safety issues on CRuby
• (#907) Add new ConcurrentMap backend for TruffleRuby

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

@​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)

---

This change is 

[depfu[bot]]

Closed in favor of #61.